Ivan Ka
You should also investigate Kube API behavior on the cluster. I recently encountered a similar issue where ExternalDNS was throttled by the Kube API, making longer sync intervals (e.g., 5m,...
It's in the helm as well https://github.com/kubernetes-sigs/external-dns/blob/111df9f1fb4c0ee63823cca7dd57ac1a7815104e/charts/external-dns/templates/clusterrole.yaml#L23
Nomad is not a kubernetes source, it's completely different orchestrator/scheduler. Could you explain a little bit more how the integration suppose to work? And what is wrong with native Nomad...
My concern isn't with Nomad itself, but whether it effectively serves our project's target audience. I have no opinion, opeartional support could be tricky as we are mainly kubernetes experts,...
/ok-to-test
/label tide/merge-method-squash
Even if there is a hickaap with GCP, the external-dns should not crash. Worth to submit a fix. The relevant lines responsible should emit soft error https://github.com/kubernetes-sigs/external-dns/blob/0d6c5e25359c661a075297807270ff37b748a417/provider/provider.go#L36
Looks like the flag was deleted unintentionally https://github.com/kubernetes-sigs/external-dns/pull/5836
resolved, fix is in master and should be available in next version https://github.com/kubernetes-sigs/external-dns/pull/6014