HashiCorp Vault DNS Set To 10.* Addresses

[rfpludwick]

I'm not sure where the problem lies here between my external-dns setup and the hashicorp/vault Helm chart. I have the following values.yaml snippet for my Vault installation:

server:
  ingress:
    enabled: true
  service:
    annotations:
      external-dns.alpha.kubernetes.io/hostname: "vault.k8s-cluster.local"

In the Vault helm chart, the annotation actually gets applied to both the vault-internal service, and the vault service. I believe that's causing the issue. As of right now there is no way for me to ensure the annotation is only applied to the vault service. Is this expected behavior from external-dns when the annotation is duplicated? Is there some way I can get external-dns to ignore the duplicate on vault-internal?

Pertinent logs from external-dns:

external-dns-2 time="2024-12-31T04:20:44Z" level=info msg="add vault-0.vault.k8s-cluster.local IN A -> 10.244.4.28"
external-dns-2 time="2024-12-31T04:20:44Z" level=info msg="add vault.k8s-cluster.local IN A -> 10.244.4.28"

[saikatharryc]

You can potentially add a label or annotation filter to the etxernal-dns and then have the extraAnnotation applied to the vault.
that way you can make sure that there is only one rule getting applied.
If you search around the issues you would be able to find a solution, but this seems to be purely the consumer play. you could customize the chart and use it as well.