-
Epic
-
Resolution: Unresolved
-
Undefined
-
None
-
Support an "OKD" featureset to be enabled by default on OKD clusters
-
False
-
-
False
-
Not Selected
-
To Do
-
QE Needed, Docs Needed, TE Needed, Customer Facing, PX Needed
-
25% To Do, 63% In Progress, 13% Done
ref: https://docs.google.com/document/d/1r32eDYsP3oZ1DpRKr9qrqMM-BrJNJLtysW1J__sg5ys/edit?tab=t.0
Proposal:
- Add a subset of featuregates as part of a new “OKD” featureset (Default + selected features)
- Featureset is enabled by default for OKD clusters, allowing the features to be ON and the cluster to be upgradeable by default.
Reason:
- Offload testing for techpreview features to OKD
- Have customers try out new features by installing OKD on dev clusters which can then be upgraded unlike TechPreviewNoUpgrade
- Differentiate OKD from Openshift, while providing early signal for OCP.
Changes required:
- New API definition
- Add features which have stable/v1beta api to the featureset and exclude features with v1alpha api
- cluster-config-operator needs to set upgradeable to true when OKD featureset is enabled for OKD clusters
- CVO (Cluster-version-operator) needs to recognize the featureset in order to apply the respective manifests
- Manifests for new featureset need to be created for cluster-ingress-operator
- Run test suites and upgrade tests to make sure cluster stability is not affected.
- Document new OKD featureset and which features are enabled on OKD.
- is related to
-
OKD-270 List of feature gates and their respective API version
-
- Closed
-
- links to