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

Add a note about full CA chain requirement for Che #1922

Merged
merged 4 commits into from
Mar 22, 2021
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
[id="importing-untrusted-tls-certificates_{context}"]
= Importing untrusted TLS certificates to {prod-short}

Internal communications between {prod-short} components are, by default, encrypted with TLS.
External communications between {prod-short} components are, by default, encrypted with TLS.
Communications of {prod-short} components with external services such as proxies, source code repositories, identity providers may require using of TLS.
Those communications require the use of TLS certificates signed by trusted Certificate Authorities.

Expand Down Expand Up @@ -30,6 +30,12 @@ the cluster contains cluster-wide trusted CA certificates added through the link
- Based on this annotation, OpenShift automatically injects the cluster-wide trusted CA certificates inside the `ca-bundle.crt` key of ConfigMap
====

[IMPORTANT]
====
Some {prod-short} components require to have full certificate chain to trust the endpoint.
If the cluster is configured with an intermediate certificate, then the whole chain (including self-signed root) should be added to {prod-short}.
====

== Adding new CA certificates into {prod-short}

This guide can be used before the installations of {prod-short} or when {prod-short} is already installed and running.
Expand Down