feat(sync): add Traefik IngressRoute support (routingType: ingressroute)#1384
Open
feat(sync): add Traefik IngressRoute support (routingType: ingressroute)#1384
Conversation
Add an alternative routing backend for the zenith-service Helm chart,
controlled by a new ingress.routingType value ('ingress' by default,
'ingressroute' for Traefik).
When routingType is 'ingressroute', Kubernetes Ingress resources are
replaced by Traefik IngressRoute CRDs (processed by the always-enabled
kubernetesCRD provider), with TLS termination using the same per-service
secrets already created by secret-tls.yaml. OIDC authentication is
preserved via a Traefik ForwardAuth Middleware pointing to the
oauth2-proxy sidecar.
This fixes Zenith tunnel routing on management clusters that run Traefik
with kubernetesIngress disabled.
Add a routingType option to global.ingress ('ingress' by default for
backward compatibility, 'httproute' for Gateway API). When set to
'httproute', the registrar Ingress is replaced by a native
gateway.networking.k8s.io/v1 HTTPRoute, with configurable gateway
parentRef and timeouts. The existing Ingress template is gated on
routingType: ingress.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add an alternative routing backend for the zenith-service Helm chart, controlled by a new ingress.routingType value ('ingress' by default, 'ingressroute' for Traefik).
When routingType is 'ingressroute', Kubernetes Ingress resources are replaced by Traefik IngressRoute CRDs (processed by the always-enabled kubernetesCRD provider), with TLS termination using the same per-service secrets already created by secret-tls.yaml. OIDC authentication is preserved via a Traefik ForwardAuth Middleware pointing to the oauth2-proxy sidecar.
This fixes Zenith tunnel routing on management clusters that run Traefik with kubernetesIngress disabled.