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

Placement and PlacementBinding changes should not cause all policies to be regenerated

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • GRC
    • None
    • GRC Sprint 2023-16, GRC Sprint 2023-17, GRC Sprint 2023-18, GRC Sprint 2023-19
    • No

      Whenever there is a PlacementRule, Placement/PlacementDecision, or PlacementBinding change, it causes the root policy to be regenerated for every managed cluster, even those not affected.

      This should be separated out to a separate controller in the Policy Propagator so that a placement update only affects the impacted clusters. For example, if a cluster is added to a placement, the propagated policy should generated just for that one cluster.

      This is related to ACM-7332.

              yikim@redhat.com Yi Rae Kim
              mprahl Matthew Prahl
              Justin Kulikauskas
              Derek Ho Derek Ho
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: