-
Notifications
You must be signed in to change notification settings - Fork 55
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 Dex configuration is broken after update (#1014) #591
Fix Dex configuration is broken after update (#1014) #591
Conversation
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, thanks
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.
Looks fine, some small phrases need to be corrected.
+ | ||
---- | ||
kubectl replace --force -f <cluster-name>/addons/dex/dex.yaml | ||
kubectl --namespace=kube-system delete pod -l app=oidc-dex | ||
kubectl --namespace=kube-system delete pod -l app=oidc-gangway |
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.
I don't think we need to restart gangway pods since this is for fix dex configuration.
@cclhsu Sorry I don't know the discussion history, but is it better to ask the customer to download the existing
|
…doc-caasp into update_dex_configuration
@jordimassaguerpla is this relevant for 4.0.2? |
Yes it is, this makes reference to SUSE/avant-garde#1014 |
I asked Clark about this in a private message and apparently both ways are OK, it seems to be a matter of preference. So merging now. Thanks for the contribution! |
@nkoranova Can you merge this to master as well please? |
Describe your changes