CheckAndUpdateK8sTLSConfiguration validates Che TLS configuration on Kubernetes infra.

CreateTLSSecretFromRoute creates TLS secret with given name which contains certificates obtained from give url.

GetConfigMapData gets env values from CR spec and returns a map with key:value which is used in CheCluster ConfigMap to configure CheCluster master behavior.

GetClusterRoute returns existing route.

GetClusterSecret retrieves given secret from cluster.

GetEndpointTLSCrtBytes creates a test TLS route and gets it to extract certificate chain There's an easier way which is to read tls secret in default (3.11) or openshift-ingress (4.0) namespace which however requires extra privileges for operator service account.

GetEndpointTLSCrtChain retrieves TLS certificates chain from given endpoint.

GetFullCheServerImageLink evaluate full cheImage link(with repo and tag) based on Checluster information and image defaults from env variables.

GetSpecRoute returns default configuration of a route in Che namespace.

GetSpecSecret return default secret config for given data.

IsSelfSignedCertificateUsed detects whether endpoints are/should be secured by self-signed certificate.

K8sHandleCheTLSSecrets handles TLS secrets required for Che deployment on Kubernetes infrastructure.

* * Create devfile registry resources unless an external registry is used.

* * Create plugin registry resources unless an external registry is used.

SyncSecretToCluster applies secret into cluster.

TLS related constants.

TLS related constants.

TLS related constants.

TLS related constants.

TLS related constants.

TLS related constants.

TLS related constants.

This is only to correctly manage defaults during the transition from Upstream 7.0.0 GA to the next version That fixed bug https://github.com/eclipse/che/issues/13714.