Hello Team,

Customer want to deploy RHOSO connected environment using their own internal registry setup on RHOCP [1].

This is because they would like to avoid directly pulling images from registry.redhat.io for reasons of performance, better control over images, and most importantly for security compliance purposes.

They want to use the same internal registry for both control and data plane deployment. 

Our existing documentation on Connected environment says the redhat registry (registry.redhat.io) will be used.

Whereas on the disconnected environment documentation [2] we talk about oc-mirror in the section "Preparing the images and the Operator mirror"  but it not clear whether customer can adopt the same steps for connected environment to have internal registry.

Hence customer would like to know,

=> Whether internal registry can be setup for connected environment?

=> If internal registry is supported in connected environment, then the steps need to be included in our existing connected RHOSO deployment documentation.

Please help to clarify the above two points. 

NOTE: Customer is also ready to use the 3rd party registry like harbor if the same is supported by us.

[1]

[kni@p105-provisioner 04_mis]$ oc get clusteroperator image-registry
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE
image-registry 4.18.7 True False False 6d22h

[kni@p105-provisioner 04_mis]$ oc get route default-route -n openshift-image-registry NAME HOST/PORT PATH SERVICES PORT TERMINATION WILDCARD
default-route default-route-openshift-image-registry.apps.bby2-st-rh-04b.corp.fortinet.com image-registry <all> reencrypt None

[2]

https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html/deploying_red_hat_openstack_services_on_openshift_in_a_disconnected_environment/proc_prepare-images-and-operator-mirror_disconnected-rhoso