Kubernetes
Try Vault with Kubernetes in different environments such as a standalone cluster, on OpenShift, or via an external Vault server.
Use case
Secure Kubernetes clusters with the power of Vault and dynamic secrets.
Challenge
Running Vault with Kubernetes can be done differently based on the environments and needs, whether you are running Vault side-by-side or within Kubernetes. The goal is to provide a variety of options around how to leverage Vault with Kubernetes.
Solution
Instead of sharing credentials and tokens across pods and services, Vault allows each service to uniquely authenticate and request their own unique credentials. Vault set out to provide a variety of options around how to leverage Vault and Kubernetes to securely introduce secrets into applications and infrastructure. Vault supports the following Kubernetes integrations:
Vault Secrets Operator for Kubernetes - Provides a more native method to retrieve and sync Kubernetes Secrets that include post-rotation updates.
vault-k8s - Provides access to Vault secrets by deploying a vault-agent sidecar into a Kubernetes Pod.
vault-csi-provider - Fetches secrets stored in Vault and uses the Secrets Store Container Storage Interface (CSI) driver interface to mount them into Kubernetes Pods.
Try Vault with Kubernetes in different environments such as a standalone cluster, on OpenShift, or via an external Vault server.
The Vault Helm chart is the recommended way to install and configure Vault on Kubernetes.
Alters pod specifications to include Vault Agent containers that render Vault secrets to a shared memory volume using Vault Agent Templates.
This deployment guide covers the steps required to install and configure a single HashiCorp Vault cluster on Kubernetes.
Vault can manage secrets for Kubernetes application pods from outside the cluster.
Learn how to inject Vault secrets into Kubernetes Pods via a sidecar container.