-
Feature
-
Resolution: Unresolved
-
Major
-
None
-
False
-
None
-
False
-
Not Selected
-
0% To Do, 0% In Progress, 100% Done
-
SF Ready/Refined Backlog
Feature Overview
Migration towards all add-ons being managed by the default add-on manager and remove duplicate controllers
Goals
1. SF team follow the migration plan in community to upgrade the addon-framework and addon-manager.
https://github.com/open-cluster-management-io/ocm/issues/355
OCM v0.14.0
- The addon is default managed by self (addon-framework).
- The minimal request addon-framework version is v0.8.1.
- Addon-manager will add annotation addon.open-cluster-management.io/lifecycle: addon-manager if self is not set.
Addon-framework 0.10.0
- Remove duplicate config controller code in framework.
- Remove WithInstallStrategy() func in framework.
- If use addon-framework, remove annotation addon.open-cluster-management.io/lifecycle: self.
2. Cross quad work, each ACM addon owner needs to upgrade the addon-framework to required version.
Requirements
This Section: A list of specific needs or objectives that a Feature must
deliver to satisfy the Feature.. Some requirements will be flagged as MVP.
If an MVP gets shifted, the feature shifts. If a non MVP requirement slips,
it does not shift the feature.
| Requirement | Notes | isMvp? |
|---|---|---|
| CI - MUST be running successfully with test automation | This is a requirement for ALL features. |
YES |
| Release Technical Enablement | Provide necessary release enablement details and documents. |
YES |
(Optional) Use Cases
This Section:
- Main success scenarios - high-level user stories
- Alternate flow/scenarios - high-level user stories
- ...
Questions to answer
- ...
Out of Scope
- …
Background, and strategic fit
This Section: What does the person writing code, testing, documenting
need to know? What context can be provided to frame this feature?
Assumptions
- ...
Customer Considerations
- ...
Documentation Considerations
Questions to be addressed:
- What educational or reference material (docs) is required to support this
product feature? For users/admins? Other functions (security officers, etc)? - Does this feature have a doc impact?
- New Content, Updates to existing content, Release Note, or No Doc Impact
- If unsure and no Technical Writer is available, please contact Content
Strategy. - What concepts do customers need to understand to be successful in
[action]? - How do we expect customers will use the feature? For what purpose(s)?
- What reference material might a customer want/need to complete [action]?
- Is there source material that can be used as reference for the Technical
Writer in writing the content? If yes, please link if available. - What is the doc impact (New Content, Updates to existing content, or
Release Note)?