Closed sossickd closed 2 months ago
I am also facing the similar issue with external-dns-1.13.1. external_dns_controller_verified_a_records, external_dns_source_a_records and external_dns_registry_a_records all a_records metrics sre showing 0, but endpoint metric is showing correctly.
I got the issue. Here - https://github.com/kubernetes-sigs/external-dns/blob/a86fa4173e4e206a5942fe126db6c598cf1d721a/controller/controller.go#L206 it is checking the total endpoints from registry, which is showing correctly in metrics. and then here- https://github.com/kubernetes-sigs/external-dns/blob/a86fa4173e4e206a5942fe126db6c598cf1d721a/controller/controller.go#L214 it is calculating the A records which only list the record type A - pointing to IP, not other records.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
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:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
What happened:
AWS Provider metrics showing 0 -
external_dns_controller_verified_a_records external_dns_registry_a_records external_dns_source_a_records external_dns_controller_no_op_runs_total
What you expected to happen:
external_dns_controller_verified_a_records
should equal 5 (same asexternal_dns_source_endpoints_total
)external_dns_registry_a_records
should equal 50 (same asexternal_dns_registry_endpoints_total
)external_dns_source_a_records
should equal 5 (same asexternal_dns_source_endpoints_total
)external_dns_controller_no_op_runs_total
should increment on every no-op runAll these metrics behave as expected when using the Azure Provider on AKS with the same external-dns helm chart version.
How to reproduce it (as minimally and precisely as possible):
Helm Values.yaml:
Install:
Anything else we need to know?:
Environment:
external-dns --version
): 0.13.6