|Sean Johnson 41beff87bc||3 weeks ago|
|.circleci||3 months ago|
|.github||3 months ago|
|agent-inject||4 weeks ago|
|build/docker||3 weeks ago|
|deploy||4 weeks ago|
|helper/cert||2 months ago|
|leader||2 months ago|
|subcommand||4 weeks ago|
|version||4 weeks ago|
|.gitignore||11 months ago|
|CHANGELOG.md||4 weeks ago|
|LICENSE||1 year ago|
|Makefile||4 weeks ago|
|README.md||6 months ago|
|commands.go||1 year ago|
|go.mod||2 months ago|
|go.sum||2 months ago|
|kustomization.yaml||1 year ago|
|main.go||1 year ago|
This is a basic fork for simplifying building multi-arch Docker images since my K8s cluster is a mix of arm64 and amd64 nodes.
vault-k8s binary includes first-class integrations between Vault and
Kubernetes. Currently the only integration in this repository is the
Vault Agent Sidecar Injector (
agent-inject). In the future more integrations
will be found here.
The Kubernetes integrations with Vault are documented directly on the Vault website. This README will present a basic overview of each use case, but for full documentation please reference the Vault website.
This project is versioned separately from Vault. Supported Vault versions for each feature will be noted below. By versioning this project separately, we can iterate on Kubernetes integrations more quickly and release new versions without forcing Vault users to do a full Vault upgrade.
vault-k8s is distributed in multiple forms:
The recommended installation method is the official Vault Helm chart. This will automatically configure the Vault and Kubernetes integration to run within an existing Kubernetes cluster.
A Docker image
hashicorp/vault-k8s is available. This can be used to manually run
vault-k8s within a scheduled environment.
Raw binaries are available in the HashiCorp releases directory. These can be used to run vault-k8s directly or build custom packages.