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

fix nginx->ingress (#1207) 

Signed-off-by: 楚岳 <wangyike.wyk@alibaba-inc.com>
This commit is contained in:
wyike 2023-03-27 15:09:01 +08:00 committed by GitHub
parent cc23c157d3
commit 6dc9552a63
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
8 changed files with 18 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/tutorials/helm-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
```
@ -121,7 +121,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
```

6
docs/tutorials/k8s-object-rollout.md
View File

@ -110,7 +110,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
```
@ -221,7 +221,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
```
@ -330,4 +330,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.

4
i18n/zh/docusaurus-plugin-content-docs/current/end-user/traits/rollout.md
View File

@ -62,7 +62,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
```
@ -147,7 +147,7 @@ spec:
- weight: 20
- weight: 90
trafficRoutings:
- type: nginx
- type: ingress
EOF
```

4
i18n/zh/docusaurus-plugin-content-docs/current/tutorials/helm-rollout.md
View File

@ -63,7 +63,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
```
@ -121,7 +121,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
```

4
i18n/zh/docusaurus-plugin-content-docs/version-v1.7/end-user/traits/rollout.md
View File

@ -62,7 +62,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
```
@ -147,7 +147,7 @@ spec:
- weight: 20
- weight: 90
trafficRoutings:
- type: nginx
- type: ingress
EOF
```

4
i18n/zh/docusaurus-plugin-content-docs/version-v1.7/tutorials/helm-rollout.md
View File

@ -63,7 +63,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
```
@ -121,7 +121,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
```

4
versioned_docs/version-v1.7/tutorials/helm-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
```
@ -121,7 +121,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
```

6
versioned_docs/version-v1.7/tutorials/k8s-object-rollout.md
View File

@ -110,7 +110,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
```
@ -221,7 +221,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
```
@ -330,4 +330,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.