TLSRoute v1 in v1.5.0 Gateway API

[hamid-elaosta]

What would you like to be added:

TLSRoute v1 support / Gateway API v1.5.0

Why is this needed:

external-dns currently relies on v1alpha2 TLSRoute so it needs to use an older experimental branch of Gateway API.

Gateway API v1.5.0 was just made available and TLSRoute was promoted to Standard Channel: https://github.com/kubernetes-sigs/gateway-api/releases/tag/v1.5.0

external-dns currently fails when listening for TLSRoutes on Gateway API v1.5.0 because it expect the v1alpha2 version:

time="2026-03-02T14:51:33Z" level=fatal msg="failed to sync *v1alpha2.TLSRoute: context deadline exceeded with timeout 1m0s"

[coveraver]

Also Gateway, HTTPRoute
level=fatal msg="failed to sync *v1beta1.Gateway: context deadline exceeded with timeout 1m0s"
level=fatal msg="failed to sync *v1beta1.HTTPRoute: context deadline exceeded with timeout 1m0s"

Edit:
After moving from bitnami to this chart, I didn't notice the incomplete RBAC. Fixed.

[Marauderrrr]

https://github.com/kubernetes-sigs/external-dns/blob/master/source/gateway_tlsroute.go#L37