-
Notifications
You must be signed in to change notification settings - Fork 880
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Separate annotations per service #588
Comments
enable ui, which creates a new service and you have the option: https://github.com/hashicorp/vault-helm/blob/master/values.yaml#L693 active vault pod only. It will add an extra label to the label selector, so that ui will always go to the active pod. edit: |
Thanks, that seems to be what I have been looking for but the UI part is what confused me. I assumed it is used only for exposing the UI and I was looking for the api and actually never looked into it. |
np :) |
I opened a PR for this 3 months ago but never got any traction -> #546 (comment) |
This is an important feature, hope the PR can be reviewed soon... |
Same issue with the labels, which makes it impossible to use label selectors to select only one service. |
Seems they got some comments on the PR |
This is related to my support ticket 101566, hopefully the ticket reference gives this issue an extra vote to get resolved faster. |
Is your feature request related to a problem? Please describe.
Currently, the chart can accept only a single configuration for service annotations. My use case is that in AWS I want to present the active service via an NLB and that happens with the service annotations but as it set on all services, I get 3 NLBs deployed which is not what I want.
Describe the solution you'd like
Ability to specify annotations for specific service - active, standby, headless...
Describe alternatives you've considered
Present the service with an ingress.
The text was updated successfully, but these errors were encountered: