Multi-Tenant Nomad: Considerations for Your Cluster
summary
Covers concrete steps to make a HashiCorp Nomad cluster multi-tenant: create logical partitions with Namespaces, limit consumption with Resource Quotas (example: 2500 MHz CPU and 1 GB RAM limits), enforce fine-grained permissions via ACL tokens via Vault (nomad acl token create, nomad namespace apply, nomad quota init, vault read nomad/creds), and provision secrets into jobs so services get dynamic DB creds 30m; demo shows quotas enforced, tokens issued from Vault to Nomad, and a web job using rendered Vault secrets.
AI-written summary · about
chapters (9)
- 0:00Introduction and customer story
- 2:28Nomad for multi-tenancy
- 4:54Namespaces in Nomad
- 7:43Resource quotas
- 11:33Access control and policies
- 15:25Vault integration
- 20:15Demo overview
- 20:37Live demo walkthrough
- 29:09Key takeaways and closing
related talks
39mBuilding Efficient Continuous Integration Pipelines with Nomad, Vault and Jenkins
05mNamespace Multi-Tenancy, But All The Problems Related To It
35mDeep Dive: Kubernetes Working Group for Multi-tenancy
37mTenant Autonomy & Isolation In Multi-Tenant Kubernetes Clusters - A Comprehensive Guide
29mBuilding for massive scale and security with the HashiCorp Cloud Platform
01h 00mArchitecting multi-tenant PaaS offerings
29mManaging a Multi-Tenanted Kubernetes Cluster in Production
37mMulti-Tenancy in Kubernetes: Best Practices Today, and Future Directions