-
Epic
-
Resolution: Done
-
Critical
-
None
-
Leverage Composable OpenShift feature to make cloud-controller-manager optional
-
Product / Portfolio Work
-
-
0% To Do, 0% In Progress, 100% Done
-
False
-
-
False
-
Green
-
M
-
None
Epic Goal
- Add a capability to make cloud-controller-manager an optional component
Why is this important?
- To reduce overall footprint of OpenShift for Telco environments
Scenarios
- ...
Acceptance Criteria
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- ...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- ...
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>
- is duplicated by
-
OCPCLOUD-2151 [Duplicate of OCPVE-628] Make cloud-controller-manager optional by leveraging Composable OpenShift feature
-
- Release Pending
-
- is related to
-
OCPSTRAT-421 OpenShift Optional Capabilities (Phase 5)
-
- Closed
-
- is triggering
-
OCPBUGS-23022 Installer should not complain about API resolution when the domains resolved
-
- Closed
-
- links to
- mentioned in
-
Page Loading...
(1 links to, 1 mentioned in)