kubevela
/
kubevela.github.io
mirror of https://github.com/kubevela/kubevela.github.io.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

upgreade doc,the doc is too old,modified doc is rollout.md (#1018) 

Signed-off-by: root <195446040@qq.com>

Signed-off-by: root <195446040@qq.com>
This commit is contained in:
huangxiaoping 2022-10-25 17:03:27 +08:00 committed by GitHub
parent da87f0612e
commit d94a69215d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/end-user/traits/rollout.md
View File

@ -60,7 +60,7 @@ spec:
# The second batch of Canary releases 90% Pods, and 90% traffic imported to the new version.
- weight: 90
trafficRoutings:
- type: nginx
- type: ingress
EOF
```
@ -146,7 +146,7 @@ spec:
- weight: 20
- weight: 90
trafficRoutings:
- type: nginx
- type: ingress
EOF
```
@ -247,4 +247,4 @@ $ curl -H "Host: canary-demo.com" <ingress-controller-address>/version
Demo: V1
```
Any rollback operation in middle of a runningWorkflow will rollback to the latest succeeded revision of this application. So, if you deploy a successful `v1` and upgrade to `v2`, but this version didn't succeed while you continue to upgrade to `v3`. The rollback of `v3` will automatically to `v1`, because release `v2` is not a succeeded one.
Any rollback operation in middle of a runningWorkflow will rollback to the latest succeeded revision of this application. So, if you deploy a successful `v1` and upgrade to `v2`, but this version didn't succeed while you continue to upgrade to `v3`. The rollback of `v3` will automatically to `v1`, because release `v2` is not a succeeded one.