Hide Forgot
Description of problem: The example Ansible byo inventory states: # For enterprise deployment types we ensure that registry.access.redhat.com is # included if you do not include it This is backwards, in enterprise deployments no internet / upstream repositories should be enabled unconditionally, the administrator should have full control over the registries being setup. Especially in the case of enterprise, local registry mirrors are often used and internet access is not available / forbidden. Please do not unconditionally enable registry.access.redhat.com or allow a configuration knob to disable it. Version-Release number of selected component (if applicable): 3.4
What's the impact of this in an environment where access to registry.access.redhat.com is blocked? Setting to low severity as I believe this won't actually break anything.
Correct, low prio, zero impact if you have "127.0.0.2 registry.access.redhat.com" in your /etc/hosts or firewall configured but those are needless extra steps compared to registry.access.redhat.com not being enabled at all. Thanks.
If having registry.access.redhat.com forced into the docker config actually creates problems without putting in a garbage /etc/hosts entry in we should consider this a medium. If it's just cosmetic we'll leave it at low.
Can be achieved by setting openshift_docker_ent_reg='' in 3.9 and later. *** This bug has been marked as a duplicate of bug 1461465 ***