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

update tutorial to support minikube in mac m1 (#36) 

* update tutorial to support minikube in mac m1

Signed-off-by: 晓杰 <2561589453@qq.com>

* add delte title

Signed-off-by: 晓杰 <2561589453@qq.com>
This commit is contained in:
晓杰 2022-05-26 11:21:44 +08:00 committed by GitHub
parent e557a759b5
commit 35e09e1819
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
docs/getting_started/introduction.md
View File

@ -38,3 +38,4 @@ The native Kubernetes Deployment Object supports the **RollingUpdate** strategy
Here are some recommended next steps:
- Start to [Install Kruise Rollout](./installation.md).
- Learn Kruise Rollout's [Basic Usage](../tutorials/basic_usage.md).
- [Demo video](https://www.bilibili.com/video/BV1wT4y1Q7eD?spm_id_from=333.880.my_history.page.click)

BIN
docs/images/rollout_canary.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 232 KiB

After

Width:  |  Height:  |  Size: 260 KiB

6
docs/tutorials/basic_usage.md
View File

@ -30,6 +30,7 @@ spec:
spec:
containers:
- name: echoserver
# mac m1 should choics image can support arm64,such as image e2eteam/echoserver:2.2-linux-arm64
image: cilium/echoserver:1.10.2
imagePullPolicy: IfNotPresent
ports:
@ -129,6 +130,7 @@ spec:
...
containers:
- name: echoserver
# mac m1 can choice image e2eteam/echoserver:2.2-linux-arm
image: cilium/echoserver:1.10.3
imagePullPolicy: IfNotPresent
```
@ -142,7 +144,7 @@ As shown in the figure below, replicas(5)*replicas(20%)=1 new versions of Pods a
**The Rollout status shows that the current rollout status is *StepPaused*, which means that the first 20% of Pods are released success and 5% of traffic is routed to the new version.**
After that, developers can use some other methods, such as prometheus metrics business metrics,
to determine that the release meets expectations and then continue the subsequent releases via **kubectl-kruise rollout approve rollout/rollouts-demo -n default** and wait deployment release is complete, as follows:
to determine that the release meets expectations and then continue the subsequent releases via **[kubectl-kruise](https://github.com/openkruise/kruise-tools) rollout approve rollout/rollouts-demo -n default** and wait deployment release is complete, as follows:
![approve](../images/approve_rollout.png)
@ -181,6 +183,7 @@ spec:
...
containers:
- name: echoserver
# m1 should rollback to e2eteam/echoserver:2.2-linux-arm64
image: cilium/echoserver:1.10.2
imagePullPolicy: IfNotPresent
```
@ -199,6 +202,7 @@ spec:
...
containers:
- name: echoserver
# m1 can choice image e2eteam/echoserver:2.2-linux-arm
image: cilium/echoserver:1.10.3
imagePullPolicy: IfNotPresent
```