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

Automatically propagate certificates from ca-certs configmap into the components #17918

Closed
tolusha opened this issue Sep 21, 2020 · 0 comments
Closed
Labels
area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator kind/enhancement A feature request - must adhere to the feature request template. severity/P1 Has a major impact to usage or development of the system.
Milestone

Comments

@tolusha
Copy link
Contributor

tolusha commented Sep 21, 2020

Is your enhancement related to a problem? Please describe.

When ca-certs configmap is updated with new certificates then keycloak and che-server are not aware of them.
We have to restart those pods to reread the certificates.

Describe the solution you'd like

Automatically restart che-server and keycloak pods when ca-certs config map is changed

@tolusha tolusha added kind/enhancement A feature request - must adhere to the feature request template. area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator labels Sep 21, 2020
@tolusha tolusha added this to the Backlog - Deploy milestone Sep 21, 2020
@tolusha tolusha modified the milestones: Backlog - Deploy, 7.21 Sep 30, 2020
@tolusha tolusha added the severity/P1 Has a major impact to usage or development of the system. label Sep 30, 2020
@tolusha tolusha mentioned this issue Oct 1, 2020
50 tasks
@tolusha tolusha modified the milestones: 7.21, 7.20 Oct 13, 2020
@tolusha tolusha closed this as completed Oct 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator kind/enhancement A feature request - must adhere to the feature request template. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

No branches or pull requests

1 participant