Add option to Che deployment.yaml to allow self-signed certificates for OIDC #12874
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: John Collier John.J.Collier@ibm.com
What does this PR do?
If Che is installed via Helm on to a Kubernetes cluster with self-signed certificates and multiuser is enabled, Eclipse Che will fail to start with the following error:
This PR adds a
global.tls.useSelfSignedCerts
value to values.yaml. When enabled, it has theCHE_SELF__SIGNED__CERT
environment variable added to Che's deployment.yaml, allowing the user to pass in the cluster's ca.crt into theself-signed-certificate
secret.What issues does this PR fix or reference?
#12863
Release Notes
N/A
Docs PR
N/A