Troubleshooting accessing a hosted cluster by using a custom DNS
If you encounter an issue when you access a hosted cluster by using a custom DNS, you can determine the root cause so that you can resolve the issue.
Procedure
-
Verify that the DNS record is properly configured and resolved.
-
Check that the TLS certificates for the custom domain are valid, verifying that the SAN is correct for your domain, by entering the following command:
$ oc get secret \ -n clusters <serving_certificate_name> \ -o jsonpath='{.data.tls\.crt}' | base64 \ -d |openssl x509 -text -noout - -
Ensure that network connectivity to the custom domain is working.
-
In the
HostedClusterresource, verify that the status shows the correct customkubeconfiginformation, as shown in the following example:ExampleHostedClusterstatusstatus: customKubeconfig: name: sample-hosted-custom-admin-kubeconfig -
Check the
kube-apiserverlogs in theHostedControlPlanenamespace by entering the following command:$ oc logs -n <hosted_control_plane_namespace> \ -l app=kube-apiserver -f -c kube-apiserver