-
Bug
-
Resolution: Done
-
Blocker
-
7.2.0.CD13
-
None
-
Documentation (Ref Guide, User Guide, etc.)
-
-
-
-
-
-
https://gitlab.cee.redhat.com/red-hat-jboss-enterprise-application-platform-documentation/eap-for-openshift/merge_requests/179, https://gitlab.cee.redhat.com/red-hat-jboss-enterprise-application-platform-documentation/eap-for-openshift/merge_requests/183, https://gitlab.cee.redhat.com/red-hat-jboss-enterprise-application-platform-documentation/eap-for-openshift/merge_requests/186
The current documented workflow for setting up EAP imagestreams and templates on OpenShift is broken because the imagestreams now refer to the new secured registry.redhat.io image registry, rather than the previous (currently documented) open registry registry.access.redhat.com. (change made as part of CLOUD-2812).
The documented workflows for OCP and OSO will need to be respectively updated to allow users to authenticate+authorize to access images in the secured registry.
I have set this as a blocker, because the current documentation does not work with the GitHub-hosted imagestreams and templates. (affects 7.1, current and future CD releases, and upcoming 7.2)
- is cloned by
-
JBEAP-15468 [7.1] OpenShift docs workflow broken; imagestreams pointing to new secured registry
- Closed
-
JBEAP-15496 Quickstart OpenShift docs workflow broken; imagestreams pointing to new secured registry
- Closed
-
JBEAP-15521 [CD13] OpenShift docs workflow broken; imagestreams pointing to new secured registry
- Closed
-
JBEAP-15532 [7.2] OpenShift docs: Update import instructions for 7.2.0.GA
- Closed
-
JBEAP-15536 Quickstarts: OpenShift imagestreams need to be loaded from the tagged location
- Closed