-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Support namespaced IngressClass #7519
Comments
@rikatz: This issue is currently awaiting triage. If Ingress contributors determines this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@rikatz |
@akshitgrover unfortunatelly I misunderstood the concept of Namespaced Ingress Class, which does not exists (what exists is the namespaced parameters) :/ I'm going to close this issue as this is not "doable" but we can discuss other things for you to work as well :) /close |
@rikatz: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@rikatz So, if the namespaced IngressClass(es) do not exist, what are users doing namespaced nginx ingress controller installation supposed to use ( |
Have a similar question as a @alex-vmw |
If its hurting you badly, then you can install ingress-controller v1.1.1 3 times, with each one in 3 different namespaces.
Worst case scene, you can revert to the annotation. It will stay for a long time I think. Although the docs needs update on that aspect.
Thanks,
; Long
… On 21-Feb-2022, at 11:22 PM, Denys ***@***.***> wrote:
Have a similar question as a @alex-vmw <https://github.com/alex-vmw>
So, we have a cluster with say 3 namespaces for separate environments/projects.
How it can be achieved? kubernetes.io/ingress.class annotation is deprecated and IngressClass is a cluster level resource that users have no permissions for
—
Reply to this email directly, view it on GitHub <#7519 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABGZVWWERCASPZNQ6AJG2ALU4J3URANCNFSM5CR2KDBA>.
Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you are subscribed to this thread.
|
Namespaced Ingress Class is already in Beta.
We should support it and allow users to use it instead of cluster scoped Ingress Class
The text was updated successfully, but these errors were encountered: