feat(argo-workflows): Add Gateway API HTTPRoute support #3567
Conversation
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
lexfrei
requested review from
jmeridth,
tico24,
vladlosev and
yu-croco
as code owners
lexfrei
force-pushed
the
feat/argo-workflows-add-httproute-support
branch
from
4e0165c to
8013792
Compare
Add support for Gateway API HTTPRoute and BackendTLSPolicy resources as an alternative to traditional Kubernetes Ingress for Argo Workflows server. Changes: - Add server-httproute.yaml template for Gateway API v1 HTTPRoute - Add server-backendtlspolicy.yaml template for v1alpha3 BackendTLSPolicy - Add httproute and backendTLSPolicy configuration sections to values.yaml - Add documentation for Gateway API usage in README.md.gotmpl - Bump chart version to 0.46.0 Key differences from Argo CD implementation: - No GRPCRoute support (Argo Workflows uses HTTP/HTTPS only, not gRPC) - Simplified port logic (single service port) All features are disabled by default for backward compatibility. Gateway API support is marked as EXPERIMENTAL. Co-Authored-By: Claude <[email protected]> Signed-off-by: Aleksei Sviridkin <[email protected]>
lexfrei
force-pushed
the
feat/argo-workflows-add-httproute-support
branch
from
8013792 to
9fa1639
Compare
18 tasks
mkilchhofer
reviewed
Dec 22, 2025
| @@ -0,0 +1,26 @@ | |||
| {{- if and .Values.server.enabled .Values.server.backendTLSPolicy.enabled -}} | |||
| {{- $fullName := include "argo-workflows.server.fullname" . -}} | |||
| apiVersion: gateway.networking.k8s.io/v1alpha3 | |||
Member
There was a problem hiding this comment.
I think we can directly go with v1 now
Xref on argo-cd chart:
Merge upstream/main and update Gateway API BackendTLSPolicy from v1alpha3 to stable v1, matching the argo-cd chart update. Co-Authored-By: Claude <[email protected]> Signed-off-by: Aleksei Sviridkin <[email protected]>
jmeridth
approved these changes
Jan 5, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Summary
This PR adds Gateway API support to the Argo Workflows Helm chart, providing a modern alternative to traditional Ingress resources.
Added resources
Motivation
Gateway API is the successor to Ingress and is becoming the standard for traffic management in Kubernetes. This addition provides users with a modern, vendor-neutral way to expose Argo Workflows, aligning with the evolving Kubernetes ecosystem.
Key differences from Argo CD implementation
Testing
Notes
Experimental Status: Gateway API support is marked as EXPERIMENTAL. Support depends on your Gateway controller implementation. Some controllers may require additional configuration (e.g., BackendTLSPolicy for HTTPS backends). Not all Gateway controllers support BackendTLSPolicy (e.g., Cilium does not yet support it).
Checklist: