From a40e585c0cee41da9107c5cab5a8645baa095b1e Mon Sep 17 00:00:00 2001 From: Lol3rrr Date: Wed, 27 May 2026 14:48:41 +0200 Subject: [PATCH] Start adding post about vault-agents --- content/vault-agents/index.md | 41 +++++++++++++++++++++++++++++++++++ 1 file changed, 41 insertions(+) create mode 100644 content/vault-agents/index.md diff --git a/content/vault-agents/index.md b/content/vault-agents/index.md new file mode 100644 index 0000000..2ae66cb --- /dev/null +++ b/content/vault-agents/index.md @@ -0,0 +1,41 @@ ++++ +title = "Vault Agents" +date = 2026-06-02 +description = "Setting up vault-agents for my servers" +draft = true + +[taxonomies] +categories = ["Homelab"] +tags = ["Homelab", "Vault"] + +[extra] +toc = true ++++ + +My journey to setting up vault-agents on my servers to handle dynamic secrets in configurations. + + + +# Configuring Vault Itself +We first need to setup vault such that the vault agents can authenticate to vault itself. + +# Deploying Vault Agents +TODO +Testing + +# Using them to template Configs +A couple of examples how I am going to use the vault agents templating features + +## Nomad mTLS +We can use vault agents to template the TLS certificates for nomads mTLS configuration. +1. Get all currently valid CA certificates and store them in the trust bundle +2. Get a leaf certificate for the current node + +## Consul ACLs +To configure the ACL tokens for consul + +# References +[^vault_pki_api]: [Vault PKI API](https://developer.hashicorp.com/vault/api-docs/secret/pki) +[^consul_template_secrets]: [Consul Template Secrets](https://github.com/hashicorp/consul-template/blob/main/docs/templating-language.md#secret) +[^vault_agent_templates]: [Vault Agent Templates](https://developer.hashicorp.com/vault/docs/agent-and-proxy/agent/template) +