-
Notifications
You must be signed in to change notification settings - Fork 118
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
do not create things that need route if ingress is disabled #860
Conversation
This needs to skip creating the clusterrole/bindings for the OAuthClient - probably just need to add it to "Process OpenShift OAuth client" task. I'll work on that next UPDATE: actually, nothing needs to be done. The existing code we have is good enough. Those cluster role/bindings for oauth are not created unless auth.strategy is "openshift" and the only time auth.strategy is allowed to be "openshift" is if the ingress is enabled. If ingress is disabled, the auth.strategy is not allowed to be/will never be openshift, thus if ingress is disabled, then these cluster role/bindings for oauth will never be created. |
46f3968
to
ebd461f
Compare
16c3865
to
ae4e819
Compare
The molecule tests that should show this doesn't break anything:
Molecule tests pass for me:
|
After you run the test instructions in the previous comment, you can do additional manual testing:
|
. abort if ingress is disabled but using openshift auth strategy
84d8a9e
to
ad91fe5
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.
fixes: kiali/kiali#8023