-
Notifications
You must be signed in to change notification settings - Fork 474
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clash between ingress.class annotation and ingressClassName attribute in latest charts #1000
Comments
Thanks for your interest in OpenFaaS. Can you introduce yourself please? Who is "we"? We don't seem to have any record of your company in https://github.com/openfaas/faas/blob/master/ADOPTERS.md |
Pardon my English. We as a team of people. We are using OpenFaas for a project we decided to use to enhance our skills on Kubernetes/Node etc. Not a company per se. Should we be a company to receive support here? |
I'm asking what company, team or organisation you are representing, who we will be supporting with their usage of OpenFaaS? We provide support to our paying customers, for free users there is no SLA and is only provided on a goodwill basis, by volunteers in their spare time. See also: https://github.com/openfaas/faas/blob/master/CONTRIBUTING.md#setting-expectations-support-and-slas So if we're going to work for free to help you and your use-case, then we ask that you introduce yourself: See also: First impressions - introducing yourself and your use-case |
remove default inress annotation so the ingressClassName is setable Signed-off-by: Richard Lavey <[email protected]>
We are using Terraform and a "helm_release" resource to deploy chart version
10.2.1
in our EKS cluster.During a clean install when
ingressClassName
is provided in values we encounter an error as if aningress.class
annotation has also been provided somehow. The opposite does not apply (having the annotation in place withingressClassName
commented out works fine).While we do override the ingress annotations with a bunch of our own it seems as if the charts default annotation value makes it in there no matter what causing the issue.
Our values' snippet:
Expected Behaviour
The
helm_release
should produce the openfaas release on the cluster.Current Behaviour
The "helm_release" fails with the following message:
Are you a GitHub Sponsor (Yes/No?)
Check at: https://github.com/sponsors/openfaas
List All Possible Solutions and Workarounds
If my hunch is correct removing the default value from
values.yaml
in the sectioningress.annotations: "kubernetes.io/ingress.class: "nginx"
should fix this.Steps to Reproduce (for bugs)
Your Environment
faas-cli version
):0.14.1
docker version
(e.g. Docker 17.0.05 ):20.10.13-2.amzn2
kubectl version
Client Version: version.Info{Major:"1", Minor:"17+", GitVersion:"v1.17.9-eks-4c6976", GitCommit:"4c6976793196d70bc5cd29d56ce5440c9473648e", GitTreeState:"clean", BuildDate:"2020-07-17T19:00:19Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"21+", GitVersion:"v1.21.14-eks-18ef993", GitCommit:"ac73613dfd25370c18cbbbc6bfc65449397b35c7", GitTreeState:"clean", BuildDate:"2022-07-06T18:06:50Z", GoVersion:"go1.16.15", Compiler:"gc", Platform:"linux/amd64"}
EKS-optimized Amazon Linux
The text was updated successfully, but these errors were encountered: