-
Epic
-
Resolution: Won't Do
-
Critical
-
None
Epic Goal
- As part of the vision described in
ACM-1717, we need to provide a way to control the lifecycle of the Klusterlets across the fleet.
Why is this important?
- In the same way that we need to be able to configure a desire upgrade version for add-on agents and rolling upgrade behavior, we need to be able to do the same for Klusterlet.
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>
ACM Epic Done Checklist
See presentation and details.
Update with "Y" if Epic meets the requirement, "N" if it does not, or "N/A" if not applicable.
- _ FIPS Readiness
- _ Works in Disconnected
- _ Global Proxy Support
- _ Installable to Infrastructure Nodes
- _ No impacts to Performance and Scalability
- _ Backup and Restorable
- blocks
-
ACM-2478 Initial rolling upgrade prototype for Klusterlet and Add-ons
- Closed