6.3. Customizing console routes
For console and downloads routes, custom routes functionality uses the ingress config route configuration API. If the console custom route is set up in both the ingress config and console-operator config, then the new ingress config custom route configuration takes precedent. The route configuration with the console-operator config is deprecated.
6.3.1. Customizing the console route 링크 복사링크가 클립보드에 복사되었습니다!
You can customize the console route by setting the custom hostname and TLS certificate in the spec.componentRoutes field of the cluster Ingress configuration.
Prerequisites
- You have logged in to the cluster as a user with administrative privileges.
You have created a secret in the
openshift-confignamespace containing the TLS certificate and key. This is required if the domain for the custom hostname suffix does not match the cluster domain suffix. The secret is optional if the suffix matches.작은 정보You can create a TLS secret by using the
oc create secret tlscommand.
Procedure
Edit the cluster
Ingressconfiguration:$ oc edit ingress.config.openshift.io clusterSet the custom hostname and optionally the serving certificate and key:
apiVersion: config.openshift.io/v1 kind: Ingress metadata: name: cluster spec: componentRoutes: - name: console namespace: openshift-console hostname: <custom_hostname>1 servingCertKeyPairSecret: name: <secret_name>2 - Save the file to apply the changes.
Add a DNS record for the custom console route that points to the application ingress load balancer.