-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Read self-signed certiicate from dedicated secret #17044
Conversation
…ith operator installer) Signed-off-by: Mykola Morhun <[email protected]>
@@ -100,7 +100,7 @@ spec: | |||
valueFrom: | |||
secretKeyRef: | |||
key: ca.crt | |||
name: {{ .Values.global.tls.secretName }} | |||
name: {{ .Values.global.tls.selfSignedCertSecretName }} |
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.
It is not good to change the value name.
Somebody might use it
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.
No, I didn't change the name. This change just says: "Read ca.crt
from selfSignedCertSecretName secret instead of secretName secret". Names are unchanged.
✅ E2E Happy path tests succeed 🎉 See Details
Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1) |
…ith operator installer) (#17044) Signed-off-by: Mykola Morhun <[email protected]>
Signed-off-by: Mykola Morhun [email protected]
What does this PR do?
Makes
self-signed-certificate
secret the source of Che server CA certificate. This is done to be consistent with other installers. Also such approach make autodetection of self-signed certificate usage easier.What issues does this PR fix or reference?
Issue: #16764
Should be merged together with che-incubator/chectl#734