-
Feature
-
Resolution: Unresolved
-
Critical
-
None
Feature Overview (aka. Goal Summary)
In a managed Service context, a user may need to be able to provide a cluster wide pull secret to be able to pull content from a registry (IBM registry, their own internal registry,...) however, this pull secret needs to be separated from the pull secret that is managed by the service to ensure the cluster functions (redhat registry, ACR/ECR,....) This feature is to provide a mechanism where the customer can place a pull secret in cluster which would then result in it being appended to the global pull secret
- causes
-
OCPSTRAT-2563 Feature Parity with ROSA Classic for ROSA-HCP
-
- In Progress
-
- clones
-
OCPSTRAT-2150 Customer global pull secret in HCP for ARO
-
- Closed
-
- is depended on by
-
OCPSTRAT-2557 Backport Customer global pull secret in HCP to OpenShift 4.18 for Managed OpenShift
-
- New
-
- is related to
-
CNTRLPLANE-1707 Backport Customer Global Pull Secret to OpenShift 4.18.z, 4.19.z, and 4.20.z for Managed Services
-
- New
-
- links to