Ivan Ka
Most likely resolved. PR with fix merged https://github.com/kubernetes-sigs/external-dns/pull/5986 The fix should land in next release. If not resolved open a new issue and try to test PRs when someone opens...
Could you share your designs here? I'm working on something similar and have already started adding events. First PR https://github.com/kubernetes-sigs/external-dns/pull/5659. From first look, a lot of work is required, as...
Metrics most likely make sense. When you have time, just add it.
ExternalDNS needs to know which records to manage by reading and filtering all of them—there's no other way. The warning you're seeing is a known issue that will be fixed...
Refactoring, bug fixes, new features - all should be in they own PRs. We are trying to de-resk releases. Way too many issues opened ;-)
I'm unsure how big is the problem. At the moment this change affects only AWS. It could be that same behaviour is relevant for other providers as well. In such...
> @u-kai thanks for this interesting PR. > > Wdyt of re-use existing annotation, `external-dns.alpha.kubernetes.io/alias`, (doc [here](https://kubernetes-sigs.github.io/external-dns/latest/docs/tutorials/aws/#alias)) instead of using a new one ? > > It could be configurable...
Would be nice to get some sort of mermaid diagram https://mermaid.live/edit or similar before and after change behavoir hightlight.
Yeah. You could try. This is a PR where things were moved to specific folder only https://github.com/kubernetes-sigs/external-dns/pull/5466#issue-3089283285. There is already a flag, but this needs to be applied to all...