From 1fd325688623f29e4420de1ed80a825223388149 Mon Sep 17 00:00:00 2001 From: Michael Burke Date: Thu, 12 Apr 2018 16:40:01 -0400 Subject: [PATCH] Revert "Lists what hostnames and IPs are needed for custom certificates" --- .../deploy_registry_existing_clusters.adoc | 46 ------------------- 1 file changed, 46 deletions(-) diff --git a/install_config/registry/deploy_registry_existing_clusters.adoc b/install_config/registry/deploy_registry_existing_clusters.adoc index ece16bcd0c2b..2786da7df2b7 100644 --- a/install_config/registry/deploy_registry_existing_clusters.adoc +++ b/install_config/registry/deploy_registry_existing_clusters.adoc @@ -380,52 +380,6 @@ MIIEvgIBADANBgkqhkiG9w0BAQEFAASCBKgwggSkAgEAAoIBAQCyOJ5garOYw0sm ... -----END PRIVATE KEY----- ---- - -- The secured registry should contain the following Subject Alternative Names (SAN) list: -+ -* Two service hostnames: -+ -For example: -+ ----- -docker-registry.default.svc.cluster.local -docker-registry.default.svc ----- -+ -* Service IP address. -+ -For example: -+ ----- -172.30.124.220 ----- -+ -Use the following command to get the Docker registry service IP address: -+ ----- -oc get service docker-registry --template='{{.spec.clusterIP}}' ----- -+ -* Public hostname. -+ -For example: -+ ----- -docker-registry-default.apps.example.com ----- -+ -Use the following command to get the Docker registry public hostname: -+ ----- -oc get route docker-registry --template '{{.spec.host}}' ----- -+ -For example, the server certificate should contain SAN details similar to the following: -+ ----- -X509v3 Subject Alternative Name: - DNS:docker-registry-public.openshift.com, DNS:docker-registry.default.svc, DNS:docker-registry.default.svc.cluster.local, DNS:172.30.2.98, IP Address:172.30.2.98 ----- + The registry console loads a certificate from the *_/etc/cockpit/ws-certs.d_* directory. It uses the last file with a *_.cert_* extension in alphabetical