external-dns
external-dns copied to clipboard
kubernetes-sigs
Inconsistencies in semantics of --domain-filter between providers
When you specify --domain-filter=foo.example.com then all providers will match zones with exactly that name. However, some providers, like PowerDNS, will also match zones that are a suffix/parent, like example.com. See #2113, for example.
This is rather confusing because one would expect a general parameter like this to have the same behavior everywhere.
I'd like to take one step further and say that the parent matching behavior should be supported by every provider for the reasons mentioned in #2040. Since the parameter is called --domain-filter and not --zone-filter it makes sense that it should match any zone that may contain domains that are matched by this filter.
Similar behaviour reported here https://github.com/kubernetes-sigs/external-dns/issues/3948, but this ticket is prob more generic and focusing on consistency across providers.
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/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas 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
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/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas 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
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/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas 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