[bitnami/external-dns] Records not generated for two-level subdomains

[philipp-durrer-jarowa]

Name and Version

bitnami/external-dns 8.6.1

What architecture are you using?

amd64

What steps will reproduce the bug?

1. Use the Azure integration, and have a DNS zone e.g. example.com
2. Try to create an ingress with an external-dns annotation for hostname: my.sub.example.com

Are you using any custom parameters or values?

provider: azure
azure:
    resourceGroup: "my-rg"
    tenantId: "XXXXX"
    subscriptionId: "XXXXX"
    useManagedIdentityExtension: true
txtOwnerId: "my-aks"
policy: sync # to cleanup old entries!
metrics:
  enabled: true
domainFilters:
- example.com

What is the expected behavior?

I expect external-dns to create a new A record my.sub. pointing to the ingress IP, since example.com is in the domainfilter list and my.sub.example.com is a valid domain it should be created in the Azure DNS Zone of example.com

What do you see instead?

external-dns is ignoring my.sub.example.com until I add sub.example.com to the domainfilters but then it obviously complains about the lack of subdns-zone sub.example.com (which I really don't want to create).

What I think is needed is to adapt the zoneMatchParent feature from the AWS provider for Azure so external-dns can create the two-level subdomain entry. Alternatively, the domainfilter logic could be more explicit and when *.example.com is set, to accept all subdomains of that domain. Or as a rather ugly alternative, there should be a domain -> zone map where I could say sub.example.com -> example.com

[carrodher]

Hi, the issue may not be directly related to the Bitnami container image/Helm chart, but rather to how the application is being utilized, configured in your specific environment, or tied to a particular scenario that is not easy to reproduce on our side.

If you think that's not the case and want to contribute a solution, we'd like to invite you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.

Your contribution will greatly benefit the community. Please feel free to contact us if you have any questions or need assistance.

Suppose you have any questions about the application, customizing its content, or technology and infrastructure usage. In that case, we highly recommend that you refer to the forums and user guides provided by the project responsible for the application or technology.

With that said, we'll keep this ticket open until the stale bot automatically closes it, in case someone from the community contributes valuable insights.

[philipp-durrer-jarowa]

Filed bug with upstream application: kubernetes-sigs/external-dns#4937