upstream/vault
1
0
Fork 0
mirror of https://github.com/hashicorp/vault.git synced 2026-02-18 18:38:08 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions 5

update wording of Nomad Client Counting FAQ to reflect the new Integration (#28685)

Browse source 
* update wording of Nomad Client Counting FAQ to reflect Workload Identity and other updates

* Update computing-clients.mdx

* Update website/content/partials/faq/client-count/computing-clients.mdx

Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com>

* Update website/content/partials/faq/client-count/computing-clients.mdx

Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com>

---------

Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com>
This commit is contained in:
Adrian Todorov 2024-10-16 21:35:38 +02:00 committed by GitHub
parent bce085bd3f
commit a78d535945
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 11 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
website/content/partials/faq/client-count/computing-clients.mdx
View file

@ -50,12 +50,18 @@ details.
### Does the Nomad-Vault integration affect client counts? ((#nomad))
**Maybe**.
**Yes**.
[Nomad Vault integration](/nomad/docs/integrations/vault-integration#token-role-based-integration)
uses token roles where a single token role creates tokens for many Nomad jobs.
Unless you have configured explicit identity aliases for your Nomad tokens,
Vault will record every running instance of a Nomad job as a unique client.
The [Nomad Vault integration](/nomad/docs/integrations/vault-integration)
uses either Workload Identity (JWT) or token roles for client count:
- Vault bases Workload Identity client counts on the
[`user_claim`](/vault/api-docs/auth/jwt#user_claim) field. The
recommended default is `nomad_job`, which results in 1 client per
Nomad job.
- Nomad deprecated token roles and will remove the feature in v1.10. Client
counts for legacy token roles treat each unique policy combination as 1
non-entity client.
### Are batch tokens counted differently than service tokens? ((#batch-tokens))