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

Fix Dex configuration is broken after update (#1014) #591

Merged
merged 7 commits into from
Nov 15, 2019
Merged

Fix Dex configuration is broken after update (#1014) #591

merged 7 commits into from
Nov 15, 2019

Conversation

cclhsu
Copy link
Contributor

@cclhsu cclhsu commented Nov 12, 2019

Describe your changes

  1. Instead of modify Dex connector using addon after deploy, edit configmap directly.

Copy link
Contributor

@thehejik thehejik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks

@nkoranova nkoranova requested a review from r0ckarong November 12, 2019 17:08
Copy link
Contributor

@r0ckarong r0ckarong left a 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
Copy link

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.

@jenting
Copy link

jenting commented Nov 14, 2019

@cclhsu Sorry I don't know the discussion history, but is it better to ask the customer to download the existing oidc-dex-config ConfigMap before addon upgrade, then re-apply the downloaded oidc-dex-config ConfigMap after addon upgraded. Since as I know, we did not change the oidc-dex-config ConfigMap since skuba 4.0.0.

kubectl get configmap oidc-dex-config -n kube-system -o yaml > oidc-dex-config.yaml
kubectl replace -f oidc-dex-config.yaml

@r0ckarong r0ckarong added AdminGuide Fix will change the Admin Guide v4 CaaSP v4 labels Nov 14, 2019
@r0ckarong r0ckarong added this to the Sprint 17 milestone Nov 14, 2019
@nkoranova
Copy link
Contributor

@jordimassaguerpla is this relevant for 4.0.2?

@davidcassany
Copy link
Contributor

@jordimassaguerpla is this relevant for 4.0.2?

Yes it is, this makes reference to SUSE/avant-garde#1014

@nkoranova nkoranova changed the base branch from master to release-4.0.2 November 15, 2019 12:44
@nkoranova
Copy link
Contributor

nkoranova commented Nov 15, 2019

@cclhsu Sorry I don't know the discussion history, but is it better to ask the customer to download the existing oidc-dex-config ConfigMap before addon upgrade, then re-apply the downloaded oidc-dex-config ConfigMap after addon upgraded. Since as I know, we did not change the oidc-dex-config ConfigMap since skuba 4.0.0.

kubectl get configmap oidc-dex-config -n kube-system -o yaml > oidc-dex-config.yaml
kubectl replace -f oidc-dex-config.yaml

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 nkoranova merged commit ab16354 into SUSE:release-4.0.2 Nov 15, 2019
@r0ckarong
Copy link
Contributor

@nkoranova Can you merge this to master as well please?

nkoranova pushed a commit that referenced this pull request Nov 15, 2019
* Add storage sizing qualifying remarks (Closes #487)

* Fix Dex configuration is broken after update (#1014)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AdminGuide Fix will change the Admin Guide v4 CaaSP v4
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants