Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Namespace selected via selector #3247

Open
Allure996 opened this issue Jun 21, 2023 · 1 comment
Open

Namespace selected via selector #3247

Allure996 opened this issue Jun 21, 2023 · 1 comment
Labels
t:feature New feature or enhancement request

Comments

@Allure996
Copy link

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 cindymullins-dw added the t:feature New feature or enhancement request label Jul 1, 2023
@cindymullins-dw
Copy link
Collaborator

cindymullins-dw commented Jul 1, 2023

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
t:feature New feature or enhancement request
Projects
None yet
Development

No branches or pull requests

2 participants