You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I am using external-dns to expose services in my k8s cluster to Pi-holes. Vault is one of those services. I am using the following YAML values for the Helm chart:
This annotation is getting applied to both the vault-internal and vault services. It's causing issues with external-dns and is ending up setting the DNS to 10.* addresses, rather than the 192.168.* address I would be expecting.
Describe the solution you'd like
Feature request: please split the annotations which get applied to these two services, that way I can specify an annotation just for the vault service. Possible YAML values structure could be:
Is your feature request related to a problem? Please describe.
I am using
external-dns
to expose services in my k8s cluster to Pi-holes. Vault is one of those services. I am using the following YAML values for the Helm chart:This annotation is getting applied to both the
vault-internal
andvault
services. It's causing issues withexternal-dns
and is ending up setting the DNS to10.*
addresses, rather than the192.168.*
address I would be expecting.Describe the solution you'd like
Feature request: please split the annotations which get applied to these two services, that way I can specify an annotation just for the
vault
service. Possible YAML values structure could be:Describe alternatives you've considered
I've been unable to determine any alternative action I can take.
The text was updated successfully, but these errors were encountered: