### Problem to solve In the [Category Vision for Secrets Management](https://about.gitlab.com/direction/release/secrets_management/), we are invested in making HashiCorp's Vault Easy to Use with GitLab. For the ~"group::release management", we have the next step of enabling users to install Vault on Kubernetes Cluster in #9982. Before this can be done, we need to research the implementation of #28321 and also #20306 ### Intended users * [Delaney (Development Team Lead)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#delaney-development-team-lead) * [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer) * [Devon (DevOps Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#devon-devops-engineer) ### Proposal/Action Plan * [ ] Investigate and learn the instrumentation of #28321 completed by the Verify Team * [ ] Iterate on #9982 until scope is clear enough to build * [ ] Define iteration 1 of the MVC ### Documentation * https://gitlab.com/gitlab-org/gitlab/issues/28321 ### What does success look like, and how can we measure that? * We have a defined implementation path to have users installing HashiCorp Vault on Kube Cluster in #9982 * New Issues created have weights * Reach Minimal by 12.8