-
Epic
-
Resolution: Done
-
Major
-
None
-
TechPreviewNoUpgrade manifest annotation for conditional core components
-
False
-
False
-
Done
-
0% To Do, 0% In Progress, 100% Done
Epic Goal
- Make life easier for tech-preview OCP-core components, by adding a release-manifest annotation for manifests that should be feature-gated by TechPreviewNoUpgrade.
Why is this important?
- Avoids the need to develop inert-mode operators for tech-preview components.
- Avoids the clutter of inert-mode namespaces, RBAC, Deployments, etc. for the inert-mode operator, where that inert-mode operator needs the power to conditionally install CRDs and other important resources.
Scenarios
- cluster-api operator is tech-preview for 4.10, and it would be convenient for them to have this tooling in place, so they could avoid working up an inert-mode operator that knows how to reconcile CRDs.
Acceptance Criteria
- CI - cluster-api shows up in existing TechPreviewNoUpgrade CI jobs, but not in base jobs that do not enable that feature gate.
- Release Technical Enablement - No external docs required outside of the enhancements repository.
Dependencies (internal and external)
No dependencies.
Previous Work (Optional):
Open questions:
No open questions.
Done Checklist
- CI - CI is running, tests are automated and merged.
- Release Enablement <link to Feature Enablement Presentation>
- DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
- DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
- DEV - Downstream build attached to advisory: <link to errata>
- QE - Test plans in Polarion: <link or reference to Polarion>
- QE - Automated tests merged: <link or reference to automated tests>
- DOC - Downstream documentation merged: <link to meaningful PR>