External DNS, Azure Private-DNS, combine-fqdn-annotation produce douplicate IP

[chris8205]

What happened: If fqdn-template is used, and combine-fqdn-annotation is set, external dns would like to update the A record to the same ip ex: A ---> IPv4 --> 100.50.0.48;100.50.0.48 but a record can't get multiple time the same ip

seems, that there is a "filter" missing to prevent if the template match the service annotation: external-dns.alpha.kubernetes.io/hostname: mytestworkload.mytestnamespace.myzone

external-dns-privatezone-xxxxxxxxxxxxxx {"level":"error","msg":"Failed to update A record named 'mytestworkload.mytestnamespace' to '100.50.0.48;100.50.0.48' for Azure Private DNS zone 'myzone': PUT https://management.azure.com/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/resourceGroups/xxxxxxxxxxxxxxxxxxxxx/providers/Microsoft.Network/privateDnsZones/myzone/A/mytestworkload.mytestnamespace\n--------------------------------------------------------------------------------\nRESPONSE 400: 400 Bad Request\nERROR CODE: BadRequest\n--------------------------------------------------------------------------------\n{\n \"code\": \"BadRequest\",\n \"message\": \"The list of record sets of type 'A' may not contain multiple entries with the same 'ipv4Address'.\"\n}\n--------------------------------------------------------------------------------\n","time":"2024-06-17T07:40:20Z"}

• External-DNS version (use external-dns --version): external-dns:v0.14.1
• DNS provider: azure-private-dns

• Others:

  --log-level=debug
  --log-format=json
  --interval=1m
  --source=service
  --source=ingress
  --policy=sync
  --registry=txt
  --txt-owner-id=myowner
  --domain-filter=myzone
  --provider=azure-private-dns
  --fqdn-template={{.Name}}.{{.Namespace}}.myzone
  --ingress-class=myinternal-ingress-ctrl
  --service-type-filter=LoadBalancer
  --combine-fqdn-annotation

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten