hashicorp / hashicorp/vault-helm

K8S hosted vault with external consul as HA storage

Open
#474 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Shell
Stars
1.3k
Forks
898
Avg merge
3d 1h
Merged PRs (30d)
1

Description

Hi,
We would like to setup a Vault on Kubernetes cluster using Consul as HA backend storage. The kubernetes cluster where Vault planned to be installed has Consul agents installed in client mode and associated with Consul cluster deployed outside the Kubernetes environment. As far as I see all the docs shows examples where Vault with Consul HA is installed on the same K8S cluster where Consul cluster deployed.
How should I configure my helm chart in order to have vault configured with my external Consul cluster as HA storage as well as how to have Vault registered as a service in the Consul registry where it’s instances will be associated with appropriate K8S nodes.
Thanks in advance.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the Vault Helm chart configuration relevant to Consul HA storage and service registration, with the external Consul cluster and Kubernetes client agents described in the issue as the deployment context. Done means documenting or clarifying a supported configuration for external Consul storage and registering Vault instances with the Consul registry.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm, kubernetes
Domain
devops, infrastructure
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.