Review user-provided ingress certificates in OKD, including transport layer security (TLS) secret storage, IngressController references, and replacing Operator-generated defaults.
Use user-provided certificates for the default IngressController CR to complete the following tasks:
Replace Operator-generated default certificates before production use.
Store TLS secrets in the correct namespace.
Reference the secret in the IngressController CR.
Use user-provided default ingress certificates to allow applications on the default apps domain to present a custom TLS certificate to clients, so clients do not need to have cluster-managed certificate authority (CA) certificates installed.
Applications are usually exposed at <route_name>.apps.<cluster_name>.<base_domain>. The <cluster_name> and <base_domain> come from the installation config file. <route_name> is the host field of the route, if specified, or the route name. For example, hello-openshift-default.apps.username.devcluster.openshift.com. hello-openshift is the name of the route and the route is in the default namespace. You might want clients to access the applications without distributing cluster-managed CA certificates to the clients. Cluster administrators must set a custom default certificate when serving application content.
|
The Ingress Operator generates a default certificate for an |
Store user-provided certificates in a tls type Secret resource in the openshift-ingress namespace. Update the IngressController CR in the openshift-ingress-operator namespace to enable the use of the user-provided certificate. For more information, see "Setting a custom default certificate".