hashicorp / hashicorp/vault-helm
[performance-replication] Missing ingress for cluster_address
Open
bug
- Dominant language
- Shell
- Stars
- 1.3k
- Forks
- 897
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 1
Description
We need a additonal ingress ressource to provide for performance cluster the cluster_address endpoint. At the moment you must create a additional service that expose 8201
Contributor guide
Research direction
Start by locating the Vault Helm chart's existing ingress templates and related values. Trace how services expose the cluster_address endpoint and add the requested performance-cluster ingress so port 8201 does not require a separately created service; verify the rendered chart output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100