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

* 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

View File

@@ -50,12 +50,18 @@ details.
### Does the Nomad-Vault integration affect client counts? ((#nomad)) ### Does the Nomad-Vault integration affect client counts? ((#nomad))
**Maybe**. **Yes**.
[Nomad Vault integration](/nomad/docs/integrations/vault-integration#token-role-based-integration) The [Nomad Vault integration](/nomad/docs/integrations/vault-integration)
uses token roles where a single token role creates tokens for many Nomad jobs. uses either Workload Identity (JWT) or token roles for client count:
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. - 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)) ### Are batch tokens counted differently than service tokens? ((#batch-tokens))