Blocker In 2.6 3scale images will have to be published in a new registry (registry.redhat.io). This new registry requires authentication to access as opposed to the current registry ( registry.access.redhat.com) which is unauthenticated.
As of February 13th 2019, all newly requested container image repos (requested through Comet) have been available only on the new terms-based registry.
Implications:
- to access images, use registry.redhat.io (or in stage environment, registry.stage.redhat.io, etc). The new feature (besides a shift in endpoint): you'll have to authenticate.
- all hard references to the old registry (registry.access.redhat.com) must be updated to the new terms based registry - in documentation, in templates, in Ansible playbooks, in operators, in Jenkins pipelines, in QE tests, everywhere. Authentication (potentially with service accounts) will also have to be handled in any automated interaction with the registry.
- it'll be necessary to communicate this registry switch (and authentication implications) to existing customers
