Skip to content

Commit

Permalink
chore: Simplify Importing untrusted TLS certificates to Che doc (#2869)
Browse files Browse the repository at this point in the history
* chore: Simplify Importing untrusted TLS certificates to Che doc

Signed-off-by: Anatolii Bazko <[email protected]>

* Add https://gdpr.eu to ingoreULRS

Signed-off-by: Anatolii Bazko <[email protected]>

---------

Signed-off-by: Anatolii Bazko <[email protected]>
  • Loading branch information
tolusha authored Feb 25, 2025
1 parent 3081882 commit d984a87
Show file tree
Hide file tree
Showing 2 changed files with 10 additions and 6 deletions.
1 change: 1 addition & 0 deletions .htmltest.yml
Original file line number Diff line number Diff line change
Expand Up @@ -30,4 +30,5 @@ IgnoreURLs:
- https://git.example.com:8443
- https://stackoverflow.com/questions/tagged/eclipse-che
- https://example.com/
- https://gdpr.eu/

Original file line number Diff line number Diff line change
Expand Up @@ -16,14 +16,17 @@ Therefore, you must import into {prod-short} all untrusted CA chains in use by a
* A source code repositories provider (Git)

{prod-short} uses labeled ConfigMaps in {prod-short} {orch-namespace} as sources for TLS certificates.
The ConfigMaps can have an arbitrary amount of keys with a random amount of certificates each. Operator merges all ConfigMaps into a single one titled `ca-certs-merged`, and mounts it as a volume in the {prod-short} server, dashboard and workspace pods.
By default, the Operator mounts the `ca-certs-merged` ConfigMap in a user's workspace at two locations: `/public-certs` and `/etc/pki/ca-trust/extracted/pem`. The `/etc/pki/ca-trust/extracted/pem` directory is where the system stores extracted CA certificates for trusted certificate authorities on Red Hat (e.g., CentOS, Fedora). CLI tools automatically use certificates from the system-trusted locations, when the user's workspace is up and running.
The ConfigMaps can have an arbitrary amount of keys with a random amount of certificates each.
All certificates are mounted into:

[NOTE]
* `/public-certs` location of {prod-short} server and dashboard pods
* `/public-certs` and `/etc/pki/ca-trust/extracted/pem` locations of workspaces pods

The `/etc/pki/ca-trust/extracted/pem` directory is where the system stores extracted CA certificates for trusted certificate authorities on Red Hat (e.g., CentOS, Fedora). CLI tools automatically use certificates from the system-trusted locations, when the user's workspace is up and running.

[IMPORTANT]
====
When an OpenShift cluster contains cluster-wide trusted CA certificates added through the link:https://docs.openshift.com/container-platform/latest/networking/configuring-a-custom-pki.html#nw-proxy-configure-object_configuring-a-custom-pki[cluster-wide-proxy configuration],
{prod-short} Operator detects them and automatically injects them into a ConfigMap with the `config.openshift.io/inject-trusted-cabundle="true"` label.
Based on this annotation, OpenShift automatically injects the cluster-wide trusted CA certificates inside the `ca-bundle.crt` key of the ConfigMap.
On OpenShift cluster, {prod-short} operator automatically adds Red Hat Enterprise Linux CoreOS (RHCOS) trust bundle into mounted certificates.
====

.Prerequisites
Expand Down

0 comments on commit d984a87

Please sign in to comment.