You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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.
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: