hashicorp / hashicorp/vault-helm

Support for using custom service account for vault server and vault agent injector

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

Description

I need the ability to add a custom service account in the custom values file for the vault server and the vault agent injector. This is needed while POD Security Policy is enabled at Cluster level which has/use a restricted service account in the namespace.

Here is what is needed:
* A injection variable for using custom service account
This must exclude file: injector-serviceaccount.yaml
This must replace serviceaccount in injector-deployment.yaml, injector-clusterrolebinding.yaml
* A server variable for using custom service account
This must exclude file: The server-serviceaccount.yaml
This must replace serviceaccount in server-clusterrolebinding.yaml, server-discovery-rolebinding.yaml, and server-statefulset.yaml

Contributor guide

Open the contributing guide

Research direction

Start with the chart's custom values and the named templates: injector-serviceaccount.yaml, injector-deployment.yaml, injector-clusterrolebinding.yaml, server-serviceaccount.yaml, server-clusterrolebinding.yaml, server-discovery-rolebinding.yaml, and server-statefulset.yaml. Trace how service accounts are currently selected, then verify that custom accounts replace the references and the default service-account manifests are excluded for both injector and server.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm, kubernetes
Domain
devops, infrastructure
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.