-
Notifications
You must be signed in to change notification settings - Fork 549
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
feat(vault_kubernetes_auth_backend_role): support for bound_service_account_namespace_selector field #2379
base: main
Are you sure you want to change the base?
Conversation
'bound_service_account_namespace_selector'
Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement Learn more about why HashiCorp requires a CLA and what the CLA includes Have you signed the CLA already but the status is still pending? Recheck it. |
Shouldn't However (at least with my vault version, 1.18.1) at least one of the two attributes must be set; I couldn't find an explicit statement about this in the vault docs, but creating a role with none of them fails with
However, I am not sure how to model this in the terraform schema definition. Another question: is it necessary to add |
…vice_account_namespace_selector
Good catch, I made
Regarding this, I'm not sure how to model this too. Maybe a reviewer can help on this. |
Description
Permits to use namespace selectors for allowing kubernetes namespaces to access roles.
The bound_service_account_namespace_selector field was implemented in Vault v1.16
Closes #1882
Checklist
Output from acceptance testing:
Community Note