Feature Overview

Migration towards all add-ons being managed by the default add-on manager and remove duplicate controllers

Goals

https://docs.google.com/document/d/15Wmv0UJfM8vUnwrcfwlooQM9DyTDwjTZu2XwVlar5nU/edit#heading=h.qesnf6rron85 

https://docs.google.com/document/d/1xP9hNdgIayJZW6gUO7E5HOkmwbR26oUuIh8vkt_r-7M/edit?tab=t.0 

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.

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.

(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)?