Add gatewayAPI resources as an Ingress alternative.

[sboulkour]

Is your feature request related to a problem?

No response

Related helm chart

argo-cd

Describe the solution you'd like

As gatewayAPI has gone GA in late 2023, many ingress controllers have enabled or are enabling the use of HTTPRoute and other gatewayAPI resources. Also, as it is meant to replace ingress ressources, we would need to have the ability to deploy ArgoCD with ingresses or with gateway API objects.

Describe alternatives you've considered

Deploying HTTPRoute etc manually alongside the Argo charts.

Additional context

• Current implementations https://gateway-api.sigs.k8s.io/implementations/
• Current implementation work being done in ingress-nginx https://github.com/kubernetes/ingress-nginx/issues/7517#issuecomment-2025441175

[peschmae]

Currently GRPC is still experimental, but the HTTP(S) routes are GA.

We've already got around to add this as custom templates on an internal setup, and I'll try to check next week, if we can contribute those back upstream, or what might be needed to make this happen.

[sboulkour]

Hello everyone,

FTR, Gateway API released v1.1.0 yesterday.

GRPCRoute has graduated to GA (v1) and is now part of the Standard Channel

https://github.com/kubernetes-sigs/gateway-api/releases/tag/v1.1.0

[pdrastil]

Hi - I've created draft PR that you can try - feedback from community about initial interface is welcome as lots of ingress controller implementations are still under development.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[lucasfcnunes]

Go away, bot! Can someone pin this issue?

[pdrastil]

@lucasfcnunes Pinned - I'm currently experimenting with Contour with latest 1.1 API and this is still planned.