1. Proposed title of this feature request

OpenShift Branded Internal DNS Name for Registry

2. What is the nature and description of the request?

Provide an additional DNS name for the OpenShift internal registry that is accessible within the cluster and is portable across OpenShift instances. As an example - `registry.openshift.local`.

3. Why does the customer need this? (List the business requirements here)

The OpenShift internal registry is currently reachable within the cluster through its internal `Service` address. However, its domain name makes it challenging for use with Kubernetes-native projects, like Tekton and Shipwright:

• The domain name is lengthy and "stutters" a bit (`image-registry.openshift-image-registry.svc`)
• Accessing the registry within the cluster requires use of the non-HTTPS port (:5000).
• Pulling and pushing from the internal registry requires one of the following:
  • Adding the internal network CA to the container in the correct location (/etc/containers/certs.d or /etc/docker/certs.d - see https://docs.docker.com/engine/security/certificates/) OR
  • Ignoring TLS verification.

ImageStreams are not a solution for upstream projects like Tekton, Shipwright, and Argo Workflows, and deprecating ImageStreams is under active discussion.

4. List any affected packages or components.

Image Registry