Namespace selected via selector

[Allure996]

Please describe your use case / problem.
I set up a namespace-scoped traffic-manager, by inserting all the names of the namespace in which I wanted it to have permissions (same for clientsRbac)
This works fine, but if I will have more namespace I will update values.yaml everytime.

Describe the solution you'd like
Since the namespaces in my clusters have common labels, it would be nice to allow us to select namespaces using selectors.

Describe alternatives you've considered

Versions (please complete the following information)

Client         : v2.13.1
Root Daemon    : v2.13.1
User Daemon    : v2.13.1
Traffic Manager: v2.14.0

• Kubernetes Environment and Version: 1.24

[cindymullins-dw]

@Allure996 , you might check the docs note here and see if it covers your use case. If not, we'll leave this as a feature request.

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment, or this will be closed in 7 days.

[nurbek-workfindme]

This is a needed feature. Providing list of namespaces is not flexible enough when working with preview environments that are created and removed frequently. There should be either namespace selector or config that accepts regex for namespace names.

For example with this config:

namespaces: 'sbx-.*'

I want following namespaces to be selected as connectable:

sbx-one, sbx-two

[thallgren]

Suggested implementation:

1. The current managerRbac.namespaces setting remains. It must list names verbatim.
2. A new top-level namespaces list is introduced, deprecating the managerRbac.namespaces.
3. An entry in the namespaces list entry can either be name, a regular expression, or a selector in the form of an object.
4. The final list of managed namespaces will consist of all entries in the deprecated managerRbac.namespaces, the names in the list, all existing namespaces matching a regular expression or has a metadata.labels set that matches a selector.
5. Unless the final list is empty, the managerRbac.namespaced is implied.
6. The current clientRbac.namespaced and clientRbac.namespaces will no longer be used.

When new namespaces arrive, it will be necessary to do a helm upgrade, because those namespaces must be added, not only to the traffic-manager's environment, but also the mutating webhook's namespaceSelector.

@Allure996, @nurbek-workfindme, does this proposal cover your needs?