-
Notifications
You must be signed in to change notification settings - Fork 753
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
fix(rbac): do not create clusterrole for namespace deployment on Traefik v3 #1012
Conversation
@ChandonPierre Thanks. You found an interesting way for rbac namespaced. Would you please add test and some documentation in values.yaml ? |
Updated! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR only works with traefik v3.0.0.
Please update your if statements and your tests accordingly by adding something like:
{{- if semverCompare "<3.0.0-0" (include "imageVersion" $) }}
db3ba11
to
4d8bd28
Compare
Yes, you are correct. Updated to use the previous behavior on Traefik V2, and disable ingressclass lookup/ClusterRole when Traefik V3 and namespaced |
@ChandonPierre In its current form, this PR will be breaking for v3 users, using spec.ingressClassname with Wdyt about:
|
4d8bd28
to
668708c
Compare
I would argue the previous behvaior was a bug, or at the very least, a misnomer. But I agree not regressing existing functionality. Updated PR with the suggested behavior. |
668708c
to
0fab94f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks 👍 LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
I tested it, it works well, thanks for your contribution :-)
A namespace scoped deployment should not create cluster scoped rbac.