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

Support namespaced IngressClass #7519

Closed
rikatz opened this issue Aug 21, 2021 · 7 comments
Closed

Support namespaced IngressClass #7519

rikatz opened this issue Aug 21, 2021 · 7 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Milestone

Comments

@rikatz
Copy link
Contributor

rikatz commented Aug 21, 2021

Namespaced Ingress Class is already in Beta.

We should support it and allow users to use it instead of cluster scoped Ingress Class

@rikatz rikatz added the kind/feature Categorizes issue or PR as related to a new feature. label Aug 21, 2021
@rikatz rikatz added this to the v1.1.0 milestone Aug 21, 2021
@k8s-ci-robot
Copy link
Contributor

@rikatz: This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

@k8s-ci-robot k8s-ci-robot added needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority labels Aug 21, 2021
@akshitgrover
Copy link
Contributor

@rikatz
The issue I was working on initially, There is already a PR raised for it by another contributor
Since This is on the same lines, I'd like to take this one up
I hope it's fine
Thank you

@rikatz
Copy link
Contributor Author

rikatz commented Aug 24, 2021

@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

@k8s-ci-robot
Copy link
Contributor

@rikatz: Closing this issue.

In response to this:

@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

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.

@alex-vmw
Copy link

@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 So, if the namespaced IngressClass(es) do not exist, what are users doing namespaced nginx ingress controller installation supposed to use (kubernetes.io/ingress.class annotation is deprecated and IngressClass is a cluster level resource that users have no permissions for)?

@dmakeienko
Copy link

dmakeienko commented Feb 21, 2022

Have a similar question as a @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
I have also encountered a problem, when I tried to set scope to false and then I managed to deploy nginx-ingress in 1 namespace. But I can't deploy it into the separate namespace with the same config (though names/IP's are changed), it doesn't creates any pods.

@longwuyuan
Copy link
Contributor

longwuyuan commented Feb 23, 2022 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

6 participants