rollouts-plugin-trafficrouter-gatewayapi
rollouts-plugin-trafficrouter-gatewayapi copied to clipboard
The Argo Rollouts plugin implementing the Kubernetes Gateway API specification for using different traffic providers in progressive delivery scenarios
Checklist: * [x] I've included steps to reproduce the bug. * [x] I've included the version of argo rollouts. * [x] I've included the version of the gateway API plugin...
There is a set of permissions inside the argo-rollout helm chart already. But it would be nice if there was an assertive list of RBAC permissions this plugin needs.
**Describe the bug** When performing rapid consecutive deployments, the Gateway API traffic router plugin leaves orphaned header-based routes in the HTTPRoute resource. These orphaned routes continue to direct traffic to...
Checklist: * [x] I've included steps to reproduce the bug. * [x] I've included the version of argo rollouts. * [x] I've included the version of the gateway API plugin...
The current integration tests are based on [timeouts](https://github.com/argoproj-labs/rollouts-plugin-trafficrouter-gatewayapi/blob/main/test/e2e/testdata/single-header-based-grpcroute-rollout.yml#L29). Several times, either locally or in GitHub action they fail without any changes in the code. This makes regression testing impossible as...
Seems like when using a http route with multiple backendRefs and an external load balancer type in Google, it fails with this error: ``` Error GWCER104: HTTPRoute "xxx" is misconfigured,...
I have an Argo Rollout that is using this plugin. The Rollout has no idea what it's namespace is, since it's managed by Argo. I'm also using Kustomize for my...