As a Logging administrator I want to distribute individual ClusterLogForwarder resources per clusterset, so that I can operate individual log forwarding configurations for sets of clusters.

AcceptanceCriteria

1. When the Logging administrator distributes a ClusterLogForwarder resource annotated with a list of existing clustersets then the addon will include the logging resources only in the ManifestWorks targeting ManagedCluster resources that belong to one of these clustersets.
2. When the Logging administrator distributes a ClusterLogForwarder resource without an annotation listing clustersets then the addon will include the logging resources in all ManifestWorks targeting ManagedCluster resources.
3. When the Logging administrator distributes a non-annotated ClusterLogForwarder resource and an annotated ClusterLogForwarder resource then the addon will consider only the last one and in turn include the logging resources only in the ManifestWorks targeting ManagedCluster resources that belong to one of these clustersets.

Developer Notes:

1. Managing clusters via the ACM placement: https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.10/html/clusters/cluster_mce_overview#placement-intro
2. Introduction to ManagedClusterSets: https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.10/html/clusters/cluster_mce_overview#managedclustersets-intro

Potential implementation discussed during grooming:

1. Registration of a managed cluster will happen when a ManagedClusterAddon resource is created on the namespace of the spoke cluster;
2. When reconciling we will need to check the ManagedCluster resource to see if it has a clusterset label and what value it holds.
3. If the ManagedCluster resource has a clusterset label we will look for a ClusterLogForwarder that matches said label.