Allow user to install Hashicorp Vault into Kubernetes Cluster
Problem to solve
We want to make it easy for users to have modern secrets management. Hashicorp Vault has won this market, and users that are not already using it for rotating and managing secrets should be.
Delaney, Development Team Lead, https://design.gitlab.com/research/personas#persona-delaney
Devon, DevOps Engineer, https://design.gitlab.com/research/personas#persona-devon
Sidney, Systems Administrator, https://design.gitlab.com/research/personas#persona-sidney
Add a Helm Chart to deploy Vault into the connected Kubernetes cluster as an additional
application next to Knative, Prometheus, etc.
Helm provides a vault operator which might be useful instead of building our own from scratch.
We need to ensure we document clearly how to use the 12.2 CI features around Vault (https://gitlab.com/gitlab-org/gitlab-ce/issues/61053) with this instance.
What does success look like, and how can we measure that?
What is the type of buyer?
(Which leads to: in which enterprise tier should this feature go see https://about.gitlab.com/handbook/product/pricing/#four-tiers )