Currently ConfigurationPolicy implements a basic NamespaceSelector that filters the list of namespaces by name via include and exclude arrays that accept leading and/or trailing wildcards. Enhancing this to include LabelSelector will align more closely with typical Kubernetes use-cases that involve labeling namespaces.
In response to [this](https://github.com/open-cluster-management-io/community/issues/155#issuecomment-1176218136):
>/close
Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
Currently
ConfigurationPolicy
implements a basicNamespaceSelector
that filters the list of namespaces by name viainclude
andexclude
arrays that accept leading and/or trailing wildcards. Enhancing this to include LabelSelector will align more closely with typical Kubernetes use-cases that involve labeling namespaces.