Open zackijack opened 1 month ago
Hello
The documentation page shows TWO standalone examples as "advanced" deployments
One example is "Pinning clients to a specific version". The other example is "Making applications "canary-aware". You are expected to use either one of them. Not both of them at the same time.
I will update the documentation page to make it more clear soon.
In the meantime here is a full example for the first scenario https://github.com/kostis-codefresh/rollouts-header-routing-example/tree/main/static-routing
And a full example for the second scenario https://github.com/kostis-codefresh/argo-rollouts-stateful-example/tree/main/manifests/stateful-rollout
Let me know if that helps.
Thank you, @kostis-codefresh!
I appreciate the clarification and the additional examples. This helps a lot in understanding the correct implementation.
Sorry for my misunderstanding.
Thanks again for your support!
Checklist:
Describe the bug
In the Advanced Deployment methods doc, three HTTPRoute resources are introduced at the beginning (
canary-route
,always-old-version
,always-new-version
). These routes are crucial for implementing different deployment scenarios. However, in the Rollout example provided later in the document, a different HTTPRoute (argo-rollouts-http-route) is used. This inconsistency makes it unclear how to correctly implement the example. When I tried using the three initially mentioned HTTPRoute resources, I encountered the following error:failed to set weight via plugin: backendRef was not found in httpRoute
. I suspect this error occurs because thealways-old-version
andalways-new-version
routes only have one service each.To Reproduce
HTTPRoute
resources introduced initially.Rollout
example and notice the use of a differentHTTPRoute
.HTTPRoute
resources.failed to set weight via plugin: backendRef was not found in httpRoute
.Expected behavior
The Rollout example should either:
canary-route
,always-old-version
,always-new-version
), ensuring that they are correctly configured with one or two services, orScreenshots
Version
Argo Rollouts Controller: v1.7.2 Argo Rollouts Gateway API Plugin: v0.4.0
Logs
Message from the maintainers:
Impacted by this bug? Give it a π. We prioritize the issues with the most π.