Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-10826

Implement incremental versioning in ManagedClusterAddon to generate Manifestworks

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • Maestro
    • Critical

      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:

      1.  
      2.  
      3. ...

      Actual results:

      Expected results:

      Additional info:

            Unassigned Unassigned
            lcao@redhat.com Longlong Cao
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: