-
Story
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
None
-
Product / Portfolio Work
-
False
-
-
False
-
3
-
None
-
None
-
Node Blue Sprint 279
User Story:
As a (user persona), I want to be able to:
- The Machine Config Operator (MCO) should block cluster upgrades when there existing a customer created ClusterImagePolicy (CIP) named openshift while running with the default feature set.
so that I can achieve
- prevent this misconfiguration, since the openshift CIP is reserved for release payload verification. If a customer creates their own CIP with this name, it may conflict with cluster-managed configurations and break critical upgrade paths.
Acceptance Criteria:
Description of criteria:
- When a CIP named openshift is detected and the cluster is using the default feature set, Upgradeable=False is set and not able to upgrade
(optional) Out of Scope:
Details about what is specifically not being delivered in the story
Engineering Details:
- Backport to 4.20.z stream since we GA the ClusterImagePolicy in 4.20.
This does not require a design proposal.
This does not require a feature gate.