-
Bug
-
Resolution: Done
-
Major
-
None
-
None
Description of problem:
Currently, the ManagedClusterAddon lacks an incremental number field to track changes in generated manifestworks. This introduces challenges in monitoring changes that affect manifestworks. While the status field of ManagedClusterAddon currently tracks the latest AddonDeploymentConfig hash via the config hash field, but it's not easy to convert the config hash to an incremental number. (there is a field called lastObservedGeneration, but it is deprecated).
So, there is a need to introduce a universal incremental number field to effectively monitor the versioning of generated manifestworks within ManagedClusterAddon.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
- ...
Actual results:
Expected results:
Additional info:
- impacts account
-
ACM-10423 As an addon developer, I can configure addon to be deployed by maestro
- Closed