Learn about namespaces and secure multi-tenancy (SMT) support in Vault.| Namespace and SMT support in Vault | Vault | HashiCorp Developer
Configure Nomad server and client integration with HashiCorp Vault in the `vault` block of a Nomad agent configuration. Configure cluster name and the role for creating tokens. For Nomad clients, configure Vault's address, namespace, and certificate or TLS authentication. Specify the JWT authentication path. For Nomad servers, configure the server's default workload identity, which includes workload identity recipients, workload TTL, and key-value pairs for additional identity claims.| vault Block in Agent Configuration | Nomad | HashiCorp Developer
Configure a Nomad client in the `client` block of a Nomad agent configuration. Enable a client, configure allocation directories, artifact and template behavior, networking, node pools, servers to join, garbage collection, workload behavior, client resources, chroot, host volumes, host network, and driver-specific behavior.| client Block in Agent Configuration | Nomad | HashiCorp Developer
Learn how Nomad uses allocation working directories to store job task templates, storage volumes, artifacts, dispatch payloads, and logs. Review image and chroot isolation, as well as when Nomad uses isolation mode.| Allocation Filesystems | Nomad | HashiCorp Developer
Nomad is a distributed, highly available, datacenter-aware cluster manager and scheduler that deploys applications on any infrastructure, at any scale.| www.hashicorp.com
The "vault" block allows the task to specify that it requires a token from a HashiCorp Vault server. Nomad will automatically retrieve a Vault token for the task and handle token renewal for the task.| vault Block - Job Specification | Nomad | HashiCorp Developer