failed to sync *v1alpha3.Gateway: context deadline exceeded

[josemrs]

What happened:
At some point I cannot pin-point ExternalDNS started to crash and enter CrashBackLoopOff.

I think it's trying to access a too old version of Gateway API a this error suggest in the logs

{"level":"fatal","msg":"failed to sync *v1alpha3.Gateway: context deadline exceeded","time":"2024-11-26T09:38:10Z"}

These are my sources:

            --source=ingress
            --source=service
            --source=gateway-httproute
            --source=istio-gateway
            --source=istio-virtualservice

I cannot see any mention to this version in the doc https://kubernetes-sigs.github.io/external-dns/v0.15.0/docs/tutorials/gateway-api/

What you expected to happen:
External does not crash if an API version is not available.

How to reproduce it (as minimally and precisely as possible):
Deploy ExternalDNS 0.15.0 with Gateway API 1.1.0 and configure gateway-httproute as source

Anything else we need to know?:
This seems the same issue as #4366 with a later version where it should be fixed.

Environment:

• External-DNS version (use external-dns --version):
  0.15.0
• DNS provider:
  Route 53
• Others:
  Gateway API version: v1.1.0 standard-install.yaml
  Istio 1.23.2

[josemrs]

May this be an Istio specific issue? the only occurrences of v1alpha3 APIs are Istio related.

Indeed, the clusters failing have no Istio deployed so the API is not there. Is it correct to crash the pod and do not recover if an API is not available?

[emily-zall]

We were getting a similar error, also using istio, but then it turned out our certificate expired and once we resolved that issue, this error went away upon restarting the external-dns pods.

[stelucz]

@josemrs check clusterrole if it has all required rules. Exactly same happened to me and role was missing rule for namespaces.

[josemrs]

The problem was Istio CRD not being deployed in the cluster. my question is, should ExternalDNS crash this badly?

[stelucz]

Yes, exactly. Even "debug" log level says literally nothing. No way to troubleshoot it.
Something like "I can't access this or that" would be helpful.