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: gc doc for cli (#570) 

Signed-off-by: Yin Da <yd219913@alibaba-inc.com>
This commit is contained in:
Somefive 2022-04-06 21:53:15 +08:00 committed by GitHub
parent e6892fff16
commit 85f06b5441
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 20 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
docs/end-user/policies/gc.md
View File

@ -43,14 +43,11 @@ vela up -f app.yaml
```
```shell
$ kubectl get app
NAME COMPONENT TYPE PHASE HEALTHY STATUS AGE
first-vela-app express-server webservice running true 29s
$ vela ls
APP COMPONENT TYPE TRAITS PHASE HEALTHY STATUS CREATED-TIME
first-vela-app express-server webservice ingress-1-20 running healthy Ready:1/1 2022-04-06 16:20:25 +0800 CST
```
> In the following steps, we'll use `kubectl` command to do some verification. You can also use `vela status first-vela-app` to check the aggregated application status and see if components are healthy.
2. update the app
```yaml
@ -84,13 +81,15 @@ vela up -f app1.yaml
```
```shell
$ kubectl get app
NAME COMPONENT TYPE PHASE HEALTHY STATUS AGE
first-vela-app express-server-1 webservice running true 9m35s
$ vela ls
APP COMPONENT TYPE TRAITS PHASE HEALTHY STATUS CREATED-TIME
first-vela-app express-server-1 webservice ingress-1-20 running healthy Ready:1/1 2022-04-06 16:20:25 +0800 CST
```
check whether legacy resources are reserved.
> In the following steps, we'll use `kubectl` command to do some verification. You can also use `vela status first-vela-app` to check the aggregated application status and see if components are healthy.
```
$ kubectl get deploy
NAME READY UP-TO-DATE AVAILABLE AGE
@ -123,7 +122,7 @@ first-vela-app-v2-default 2m56s
3. delete the app
```
$ kubectl delete app first-vela-app
$ vela delete first-vela-app
```
> If you hope to delete resources in one specified version, you can run `kubectl delete resourcetracker first-vela-app-v1-default`.
@ -173,7 +172,7 @@ hello-world ClusterIP 10.96.160.208 <none> 8000/TCP 78s
If you upgrade the application and use a different component, you will find the old versioned deployment is deleted but the service is kept.
```shell
$ cat <<EOF | kubectl apply -f -
$ cat <<EOF | vela up -f -
apiVersion: core.oam.dev/v1beta1
kind: Application
metadata:

20
i18n/zh/docusaurus-plugin-content-docs/current/end-user/policies/gc.md
View File

@ -43,9 +43,9 @@ vela up -f app.yaml
```
```shell
$ kubectl get app
NAME COMPONENT TYPE PHASE HEALTHY STATUS AGE
first-vela-app express-server webservice running true 29s
$ vela ls
APP COMPONENT TYPE TRAITS PHASE HEALTHY STATUS CREATED-TIME
first-vela-app express-server webservice ingress-1-20 running healthy Ready:1/1 2022-04-06 16:20:25 +0800 CST
```
2. 然后更新它
@ -81,15 +81,15 @@ vela up -f app1.yaml
```
```shell
$ kubectl get app
NAME COMPONENT TYPE PHASE HEALTHY STATUS AGE
first-vela-app express-server-1 webservice running true 9m35s
$ vela ls
APP COMPONENT TYPE TRAITS PHASE HEALTHY STATUS CREATED-TIME
first-vela-app express-server-1 webservice ingress-1-20 running healthy Ready:1/1 2022-04-06 16:20:25 +0800 CST
```
> 在下述步骤中，我们将使用 `kubectl` 命令来做一些验证。你也可以使用 `vela status first-vela-app` 来检查应用及其组件的健康状态。
可以发现旧版本的应用资源和新版本的应用资源同时存在于集群中。
> 在下述步骤中，我们将使用 `kubectl` 命令来做一些验证。你也可以使用 `vela status first-vela-app` 来检查应用及其组件的健康状态。
```
$ kubectl get deploy
NAME READY UP-TO-DATE AVAILABLE AGE
@ -122,7 +122,7 @@ first-vela-app-v2-default 2m56s
在删除该应用时所有的版本资源会被一并回收。
```
$ kubectl delete app first-vela-app
$ vela delete first-vela-app
```
> 如果你希望删除某个应用版本下的过时资源，你可以运行`kubectl delete resourcetracker first-vela-app-v1-default`。
@ -172,7 +172,7 @@ hello-world ClusterIP 10.96.160.208 <none> 8000/TCP 78s
如果你升级该应用并使用一个新的组件，你会发现旧版本应用中通过 webservice 组件创建的 Deployment 被删除掉了，但是通过 expose 这一运维特征创建的 Service 资源仍然保留下来。
```shell
$ cat <<EOF | kubectl apply -f -
$ cat <<EOF | vela up -f -
apiVersion: core.oam.dev/v1beta1
kind: Application
metadata: