Ivan Ka
I recently added a null guard for similar case https://github.com/kubernetes-sigs/external-dns/pull/5639 and issue https://github.com/kubernetes-sigs/external-dns/issues/5634 staging docker image, you could try ``` pull gcr.io/k8s-staging-external-dns/external-dns:v20250714-v0.18.0-46-gfaeee122 ``` Did you actually deleted all the records...
Btw in 0.18 there are only new TXT registry formats.
Hi @bdrewery, Would you be able to share an abstract with a use case for that annotation? This would be incredibly helpful for our documentation; it's always valuable to provide...
I think there is a great explanation about one of the use cases, we could re-use and add it to docs https://github.com/kubernetes-sigs/external-dns/issues/5391#issue-3061231028 > Customers need to be able to resolve...
In docs use-cases missing. And would you be able to share evidences that the code is working and make changes expected?
Example use cases for another annotation https://github.com/kubernetes-sigs/external-dns/blob/master/docs/advanced/ttl.md#use-cases-for-external-dnsalphakubernetesiottl-annotation. This will help us and a community to decide which annotation to use
This PR abandoned. If anyone interested to add feature what is required; - https://github.com/kubernetes-sigs/external-dns/pull/5487#issuecomment-2960293781 So just run it against a cluster and confirm it's working. Example result https://github.com/kubernetes-sigs/external-dns/pull/5828#issuecomment-3280180526 If needed,...
Hard to say. Another option is to 1. validate arguments and fail fast 2. Introduce an interface, pattern [chain of responsibility](https://refactoring.guru/design-patterns/chain-of-responsibility) ```go type Handler interface { execute() setNext(*Source, options...) error...