-
Epic
-
Resolution: Done
-
Major
-
ACM 2.14.0
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
Background
"Migrate addon to be managed by addon-manager" is a cross-release Epic we have done for a few releases.
[2.10] Migrate addon to be managed by addon-manager
[2.11] Migrate addon to be managed by addon-manager
This epic is the last step for this migration. And next, we will:
- Will stop supporting addon-framework version v0.8.1 in ACM 0.14.0.
- Plan to stop supporting addon-framework version v0.9.3 in ACM 0.15.0.
Requirement:
All add-ons upgrade to the latest v0.12.0 addon-framework.
Upgrade tips:
First, check how your add-on lifecycle is managed:
- For most of ACM add-ons, the cma annotation "addon.open-cluster-management.io/lifecycle" is already addon-manager, just upgrade the version in your go.mod.
- For obs addon, it's cma annotation "addon.open-cluster-management.io/lifecycle" is self plz check if you are still using the WithInstallStrategy() function of addon-framework.
Then upgrade your addon-framework version in go.mod.
- For most of ACM add-ons using addon-framework v0.9., v0.10., just upgrade the version in your go.mod.
- For addons still using addon-framework v0.8.,* when upgrade to v0.12.0, the dependent k8s.io package will cause errors due to upgrading too many versions, and the effort may be large, plz start as early as you can.
Why is this important?
...
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)