Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add gatewayAPI resources as an Ingress alternative. #2634

Closed
sboulkour opened this issue Apr 9, 2024 · 6 comments · May be fixed by #2689
Closed

Add gatewayAPI resources as an Ingress alternative. #2634

sboulkour opened this issue Apr 9, 2024 · 6 comments · May be fixed by #2689

Comments

@sboulkour
Copy link

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

@pdrastil pdrastil self-assigned this Apr 9, 2024
@peschmae
Copy link

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
Copy link
Author

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
Copy link
Member

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.

Copy link

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.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 19, 2024
@lucasfcnunes
Copy link
Contributor

Go away, bot!
Can someone pin this issue?

@pdrastil
Copy link
Member

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants