[bitnami/external-dns] Istio Gateways not populating

[chruzcruz]

Name and Version

1.12.1

What architecture are you using?

None

What steps will reproduce the bug?

Good Afternoon,

I am trying to use external-dns to autopopulate GCP Cloud DNS, but noticed the entries are not being populated.
If I add in the annotations, the DNS upsert works accordingly, but would like to avoid having to hard-code load balancer/IP Values within the deployment manifests.

kind: Gateway
metadata:
  name: sample-gateway
  namespace: default
  annotations:
    external-dns.alpha.kubernetes.io/target: x.x.x.x
    external-dns.alpha.kubernetes.io/hostname: sample.dev.mydomain.com

Are you using any custom parameters or values?

logFormat: json
policy: upsert-only
sources:
  - istio-gateway
provider: google
serviceAccount:
  annotations:
    iam.gke.io/gcp-service-account: "xxxxxxxx"
domainFilters: ["xxxxx"]
txtOwnerId: "xxxx-owner"
policy: "upsert-only"
logLevel: debug
extraArgs:
  - "--google-project=xxxx-dns-project"

What do you see instead?

level=debug msg="No endpoints could be generated from Gateway default/sample-gateway"

Additional information

kubernetes-sigs/external-dns#1718
#3275

[javsalgar]

Hi,

Looking at the issue, it is not clear to me that problem lies in the Bitnami packaging but in the application itself. Did the upstream external-dns devs confirm that it is an issue with our packaging?

[github-actions]

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

[github-actions]

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.