Closed blackpegaz closed 8 months ago
In this case, does the namespace app-ns-3 use the tag prod-canary or has it already been relabelled to use the tag prod-stable ?
It has been relabelled to prod-stable as you can see there's a command to overwrite the webhook:
istioctl tag set prod-stable --revision 1-20-2 --overwrite
BTW I think the pic in the doc needs to be fixed, I'll transfer the issue.
/assign To fix the image in doc
In this case, does the namespace app-ns-3 use the tag prod-canary or has it already been relabelled to use the tag prod-stable ?
It has been relabelled to prod-stable as you can see there's a command to overwrite the webhook:
istioctl tag set prod-stable --revision 1-20-2 --overwrite
Thank you @hanxiaop. I read this information previously.
From my user perspective this part of the documentation gives a technical explanation on why and how to use "Stable revision labels" in a canary upgrade context, but, when I read it for the first time, I asked myself:
prod-canary
tag at this step ?prod-canary
tag ? Regarding helm canary upgrade, trying and testing step by step helped me to understand the solution.
In the below schema the prod-canary
tag still exists at step 3 to show a possible situation. Personally, I choose to delete this tag as soon as the canary upgrade is finished.
Is this the right place to submit this?
Bug Description
Hi,
Into the Stable revision labels section, this schema shows the same namespace name (
app-ns-2
) tree times.app-ns-3
use the tagprod-canary
or has it already been relabelled to use the tagprod-stable
?Doc page : Canary Upgrades
Regards
Benjamin
Version
Additional Information
No response