Ivan Ka

@quintush wdyt? What is your view, I could further enhance the behaviour, may just need some pointers here

If we want behavior like-to-like helm, then most likely values do need to be supplied in specific order to helm or normalised. I actually did not known about such value...

Anything could work. This is how helm community solves it https://github.com/helm/helm/blob/261233caec499c18602c61ac32507fa4656ebc9b/pkg/cli/values/options.go#L33 Most likely this project may require some architecture revisit for how values handling is implemented, something like. ```go type...

There are concerns Regarding TXT Caching as a Solution I'm unclear how caching will resolve the underlying issue. From my perspective, this looks like a bug in either the CRD...

TXT registry already have a cache https://github.com/kubernetes-sigs/external-dns/blob/36bc7d6bc47d4d8862aa02f88ac57d0608919a2a/registry/txt.go#L46 and local endpoints and TXT records cache https://github.com/kubernetes-sigs/external-dns/blob/master/registry/txt.go#L138-L141 This is a high-impact issue, and without being able to reproduce it, it's tough to...

Fixes https://github.com/kubernetes-sigs/external-dns/issues/5340

Fixes https://github.com/kubernetes-sigs/external-dns/issues/5003 ^ this issue is related, but not sure where scope of the fix will cover it

Have you managed to validate that issue is still present or it's related to specific flags - upsert-only - sync ?

relates: https://github.com/kubernetes-sigs/external-dns/issues/3977

For now, worth to create an issue to track the scenario where TXT registry records are deleted. This is a prime candidate for a follow-up pull request in my opinion....