luxolus/open-vault
2
0
Fork 0
Code Issues 1 Pull requests Releases Activity

define batch token interaction with lease count quota (#13127)

Browse source
This commit is contained in:
swayne275 2021-11-11 16:09:44 -07:00 committed by GitHub
parent 9ae3e5cdd6
commit 12faa5227b
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
website/content/docs/enterprise/lease-count-quotas.mdx
View file

@ -17,6 +17,9 @@ It is important to note that lease count quotas do not apply to the root tokens.
If the number of leases in the cluster hits the configured limit, `max_leases`, If the number of leases in the cluster hits the configured limit, `max_leases`,
an operator could still create a root token and access the cluster to try to recover. an operator could still create a root token and access the cluster to try to recover.
Additionally, batch token creation is blocked when the lease count quota is
exceeded, but batch tokens do not count towards the quota.
All the nodes in the Vault cluster will share the lease quota rules, meaning that All the nodes in the Vault cluster will share the lease quota rules, meaning that
the lease counters will be shared, regardless of which node in the Vault cluster the lease counters will be shared, regardless of which node in the Vault cluster
receives lease generation requests. Lease quotas can be imposed across Vault's API, receives lease generation requests. Lease quotas can be imposed across Vault's API,