-
Notifications
You must be signed in to change notification settings - Fork 19
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 linkerd example with header based routing #91
base: main
Are you sure you want to change the base?
add linkerd example with header based routing #91
Conversation
Signed-off-by: Alon Gluz <[email protected]>
Signed-off-by: Alon Gluz <[email protected]>
3c2640e
to
b942bb1
Compare
@kostis-codefresh Anything wrong with this PR? |
watch "kubectl -n default get httproute.gateway.networking.k8s.io/argo-rollouts-http-route -o custom-columns=NAME:.metadata.name,PRIMARY_SERVICE:.spec.rules[0].backendRefs[0].name,PRIMARY_WEIGHT:.spec.rules[0].backendRefs[0].weight,CANARY_SERVICE:.spec.rules[0].backendRefs[1].name,CANARY_WEIGHT:.spec.rules[0].backendRefs[1].weight" | ||
``` | ||
|
||
## Step 10 - Patch the rollout to see the canary deployment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great. But in this example we also want to test header based routing specifically. How do we know that it works?
Can we add 2 examples of "curl" commands here, one with the header and one without the header to see what happens?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we need some extra instructions in the README specifically for header based routing.
#84