-
Epic
-
Resolution: Done
-
Major
-
None
-
Support developing addon using a template API
-
False
-
None
-
False
-
Green
-
To Do
-
0% To Do, 0% In Progress, 100% Done
Description of problem:
Today developing an addon is still hard, since the developer needs to write code leveraging addon-framework go library, and deploy the hub addon manager on acm hub. To ease the development, we should develop a template API for addon, so developer can just create a yaml manifest to easily deploy their addon agent on managed clusters.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
- ...
Actual results:
Expected results:
Additional info:
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