Epic Goal

...

I can now (with ACM 2.14 TP) generate a ClusterPermission for a single Cluster
but what about:

• All Clusters
• All Cluster in a ClusterSet
• All Clusters with a certain label

This is not working like with Policies and Applications
where you can assign Placement and configure them directly on the Hub.

Technically a ACM-Policy would be a nice way to achieve this.

But this is complex to embed into the UI

Why is this important?

...

Scenarios

...

Acceptance Criteria

...

What happens with many Clusters?
What happens if a Cluster gets removed?

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions:

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Doc issue opened with a completed template. Separate doc issue
  opened for any deprecation, removal, or any current known
  issue/troubleshooting removal from the doc, if applicable.
• Considerations were made for Extended Update Support (EUS)