Argo Rollouts With Canary Headers Issues #4126
Unanswered
Nicolas-Vazquez-1
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi all,
I am trying to configure a Canary Header to route traffic to the canary deployment, while routing 0% live traffic to the Canary and 100% to live route. I have created two services (canary/regular) and have the rollout strategy configured as the following:
strategy:
canary:
canaryService: {{fullName}}-canary
stableService: {{fullName}}
trafficRouting:
managedRoutes:
- name: set-header-1
istio:
virtualService:
name: {{fullName}-rollout-vs
steps:
- setCanaryScale:
weight: 50
- setHeaderRoute:
name: "set-header-1"
match:
- headerName: "x-canary-version"
headerValue:
exact: "canary"
- pause:
duration: 10m
And a virtual service setting 100 weights on stable, with 0 on canary.
When I run a helm update and describe the rollout, it all works successfully and spins up a 3rd canary pod. But, on some further looking into it always says the following:
rollouts controller VirtualService 'xyz' set headerRoute 'set-header-1'
RolloutStepCompleted Rollout step 2/3 completed (invalid)
I have followed nearly every guide and the argo rollouts spec to a T -https://argo-rollouts.readthedocs.io/en/stable/features/traffic-management/#traffic-router-support-istio_1
I can't provide all my files, but anyone have any idea why this is happening or if I can get some more insight then Rollout step 2/3 completed (invalid)? I have spent far too many hours on this and can't seem to get this step to work, API requests with the header are not routing to the Canary route either.
Any help is much appreciated, thank you!!
Beta Was this translation helpful? Give feedback.
All reactions