We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Running nginx-ingress-controller:0.9.0-beta.17, if the ingress is described as:
kind: Ingress apiVersion: extensions/v1beta1 metadata: name: test annotations: ingress.kubernetes.io/class: nginx ingress.kubernetes.io/secure-backends: "true" spec: backend: serviceName: testsvc servicePort: 443
all the ingress annotations (secure-backends, affinity and so on) are ignored, if the same service is configured with the name based vhosting:
kind: Ingress apiVersion: extensions/v1beta1 metadata: name: test annotations: ingress.kubernetes.io/class: nginx ingress.kubernetes.io/secure-backends: "true" spec: rules: - http: paths: - path: / backend: serviceName: testsvc servicePort: 443
works as espected.
The text was updated successfully, but these errors were encountered:
Confirmed on my side on quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0-beta.18.
Do you have a workaround?
Sorry, something went wrong.
@angeloxx @jackielii please use quay.io/aledbf/nginx-ingress-controller:0.294
quay.io/aledbf/nginx-ingress-controller:0.294
@aledbf thanks, I can't use images outside the official paths so I'll wait the merge in the master distribution
Successfully merging a pull request may close this issue.
Running nginx-ingress-controller:0.9.0-beta.17, if the ingress is described as:
all the ingress annotations (secure-backends, affinity and so on) are ignored, if the same service is configured with the name based vhosting:
works as espected.
The text was updated successfully, but these errors were encountered: