Open mxcd opened 11 months ago
The documentation concerning the IngressRouteCRD configuration (https://argo-cd.readthedocs.io/en/stable/operator-manual/ingress/#ingressroute-crd) will be invalid when using traefik version 3
IngressRouteCRD
With the upcoming traefik v3 release, there is a breaking change to the IngressRouteCRD matchers (see https://doc.traefik.io/traefik/v3.0/migration/v2-to-v3/#matchers) causing the following to be an invalid configuration:
# ... - kind: Rule match: Host(`argocd.example.com`) && Headers(`Content-Type`, `application/grpc`) # ...
The new configuration using apiVersion: traefik.io/v1alpha1 requires to replace Headers with Header
apiVersion: traefik.io/v1alpha1
Headers
Header
Add a dedicated section concerning traefik v3 to the docs, warning the reader about the breaking changes introduced with traefik v3
You can use Header replace for Headers
Summary
The documentation concerning the
IngressRouteCRD
configuration (https://argo-cd.readthedocs.io/en/stable/operator-manual/ingress/#ingressroute-crd) will be invalid when using traefik version 3Motivation
With the upcoming traefik v3 release, there is a breaking change to the
IngressRouteCRD
matchers (see https://doc.traefik.io/traefik/v3.0/migration/v2-to-v3/#matchers) causing the following to be an invalid configuration:The new configuration using
apiVersion: traefik.io/v1alpha1
requires to replaceHeaders
withHeader
Proposal
Add a dedicated section concerning traefik v3 to the docs, warning the reader about the breaking changes introduced with traefik v3