-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Comments
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. |
Hello everyone, FTR, Gateway API released v1.1.0 yesterday.
https://github.com/kubernetes-sigs/gateway-api/releases/tag/v1.1.0 |
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. |
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. |
Go away, bot! |
@lucasfcnunes Pinned - I'm currently experimenting with Contour with latest 1.1 API and this is still planned. |
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
The text was updated successfully, but these errors were encountered: