Skip to content
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

Ingress annotations are ignored when single service ingress is used #1761

Closed
angeloxx opened this issue Nov 28, 2017 · 3 comments · Fixed by #1768
Closed

Ingress annotations are ignored when single service ingress is used #1761

angeloxx opened this issue Nov 28, 2017 · 3 comments · Fixed by #1768

Comments

@angeloxx
Copy link

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.

@jackielii
Copy link

Confirmed on my side on quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0-beta.18.

Do you have a workaround?

@aledbf
Copy link
Member

aledbf commented Nov 29, 2017

@angeloxx @jackielii please use quay.io/aledbf/nginx-ingress-controller:0.294

@angeloxx
Copy link
Author

@aledbf thanks, I can't use images outside the official paths so I'll wait the merge in the master distribution

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants