-
Epic
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
Enhance ClusterCurator EUS upgrade to have an extra posthook after the intermediate upgrade
-
Product / Portfolio Work
-
False
-
-
False
-
Not Selected
-
To Do
OCP/Telco Definition of Done
https://docs.google.com/document/d/1TP2Av7zHXz4_fmeX4q9HB0m9cqSZ4F6Jd4AiVoaF_2s/edit#heading=h.gaa58bzbvwde
Epic Template descriptions and documentation.
https://docs.google.com/document/d/14CUCEg6hQ_jpsFzJtWo29GfFVWmun2Uivrxq3_Fkgdg/edit
ACM-wide Product Requirements (Top-level Epics)
https://docs.google.com/document/d/1uIp6nS2QZ766UFuZBaC9USs8dW_I5wVdtYF9sUObYKg/edit
*<--- Cut-n-Paste the entire contents of this description into your new
Epic --->*
Epic Goal
Allow the user to have an extra posthook after the intermediate upgrade finished and before the final upgrade starts.
The container order would be like:
- prehook-ansiblejob
- intermediate-upgrade-cluster
- intermediate-monitor-upgrade
- intermediate-posthook-ansiblejob
- final-upgrade-cluster
- final-monitor-upgrade
- posthook-ansiblejob
This is mainly useful for for example:
- Updating the channel
- Checking deprecated APIs for next version
- Ensure that the cluster is in shape to continue upgrade to final version
Update Azure managed identity permissions (with ccoctl)
Requested by Amadeus https://redhat-internal.slack.com/archives/C04EYRKRXGF/p1753358769936029?thread_ts=1711474370.934189&cid=C04EYRKRXGF
Why is this important?
See above.
Scenarios
...
Acceptance Criteria
...
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 - Doc issue opened with a completed template. Separate doc issue
opened for any deprecation, removal, or any current known
issue/troubleshooting removal from the doc, if applicable. - Considerations were made for Extended Update Support (EUS)
