Description of the change
There is documentation for ingress-nginx to configure caldav and webdav redirects
https://github.com/nextcloud/helm/tree/main/charts/nextcloud#service-discovery-with-nginx-and-ingress
With gateway-api we can define this by-default because no implementation specific config is needed.
It is also not currently possible to define this configuration because backendRefs are always templated on to rules, which is not allowed for redirect filters:
HTTPRoute/nextcloud: HTTPRoute.gateway.networking.k8s.io "nextcloud" is invalid: spec.rules[1]: Invalid value: RequestRedirect filter must not be used together with backendRefs
Benefits
Properly setup caldav and webdav redirects for all gateway api users
Possible drawbacks
None
Additional information
Description of the change
There is documentation for ingress-nginx to configure caldav and webdav redirects
https://github.com/nextcloud/helm/tree/main/charts/nextcloud#service-discovery-with-nginx-and-ingress
With gateway-api we can define this by-default because no implementation specific config is needed.
It is also not currently possible to define this configuration because backendRefs are always templated on to rules, which is not allowed for redirect filters:
Benefits
Properly setup caldav and webdav redirects for all gateway api users
Possible drawbacks
None
Additional information