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

[Question]Does k8s ingress-nginx support the mergeable ingress type #3031

Closed
hchenxa opened this issue Sep 3, 2018 · 2 comments
Closed

[Question]Does k8s ingress-nginx support the mergeable ingress type #3031

hchenxa opened this issue Sep 3, 2018 · 2 comments

Comments

@hchenxa
Copy link
Contributor

hchenxa commented Sep 3, 2018

refer https://github.com/nginxinc/kubernetes-ingress/tree/master/examples/mergeable-ingress-types, just want to confirm if the ingress-nginx support the mergable ingress type.

@aledbf
Copy link
Member

aledbf commented Sep 3, 2018

@hchenxa no, that concept is not supported by this ingress controller.
By default, we merge all the ingresses. Please check https://kubernetes.github.io/ingress-nginx/how-it-works/

@amq
Copy link

amq commented Oct 25, 2019

If multiple Ingresses define different paths for the same host, the ingress controller will merge the definitions.
Annotations are applied to all the paths in the Ingress.
Multiple Ingresses can define different annotations. These definitions are not shared between Ingresses.

This seems a bit ambiguous. If there are multiple ingresses which define different paths for the same host, are annotations in one of them applied to all? This makes it impossible to selectively use e.g. oauth2_proxy.

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

No branches or pull requests

3 participants