mirror of
https://github.com/hashicorp/vault.git
synced 2025-11-29 14:41:09 +01:00
add new config option use_annotations_as_alias_metadata for k8s auth on api docs (#24941)
This commit is contained in:
parent
2a566f40fc
commit
aab72100fb
@ -42,6 +42,10 @@ access the Kubernetes API.
|
|||||||
extracted. Not every installation of Kubernetes exposes these
|
extracted. Not every installation of Kubernetes exposes these
|
||||||
keys.
|
keys.
|
||||||
- `disable_local_ca_jwt` `(bool: false)` - Disable defaulting to the local CA cert and service account JWT when running in a Kubernetes pod.
|
- `disable_local_ca_jwt` `(bool: false)` - Disable defaulting to the local CA cert and service account JWT when running in a Kubernetes pod.
|
||||||
|
- `use_annotations_as_alias_metadata` `(bool: false)` - Use annotations from the client token's associated service account
|
||||||
|
as alias metadata for the Vault entity. Only annotations with the prefix `vault.hashicorp.com/alias-metadata-` will be used.
|
||||||
|
For example, if an annotation "vault.hashicorp.com/alias-metadata-foo" is configured, "foo" with its value will be added
|
||||||
|
to the alias metadata. NOTE: Vault will need permission to read service accounts from the Kubernetes API.
|
||||||
|
|
||||||
### Deprecated parameters
|
### Deprecated parameters
|
||||||
|
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user