Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update resource-propagating.md #564

Merged
merged 1 commit into from
Feb 17, 2024
Merged

update resource-propagating.md #564

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 0 additions & 14 deletions docs/userguide/scheduling/resource-propagating.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,27 +45,21 @@ kubectl create deployment nginx --image nginx
> Note: The resource exists only as a template in karmada. After being propagated to a member cluster, the behavior of the resource is the same as that of a single kubernetes cluster.

> Note: Resources and PropagationPolicy are created in no sequence.

3. Display information of the deployment:
```shell
karmadactl get deployment
```
The output is similar to this:
```shell
The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.

NAME CLUSTER READY UP-TO-DATE AVAILABLE AGE ADOPTION
nginx member1 1/1 1 1 52s Y
```

4. List the pods created by the deployment:
```shell
karmadactl get pod -l app=nginx
```
The output is similar to this:
```shell
The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.

NAME CLUSTER READY STATUS RESTARTS AGE
nginx-6799fc88d8-s7vv9 member1 1/1 Running 0 52s
```
Expand Down Expand Up @@ -97,15 +91,11 @@ kubectl apply -f propagationpolicy-update.yaml
```
2. Display information of the deployment (the output is similar to this):
```shell
The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.

NAME CLUSTER READY UP-TO-DATE AVAILABLE AGE ADOPTION
nginx member2 1/1 1 1 5s Y
```
3. List the pods of the deployment (the output is similar to this):
```shell
The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.

NAME CLUSTER READY STATUS RESTARTS AGE
nginx-6799fc88d8-8t8cc member2 1/1 Running 0 17s
```
Expand All @@ -117,15 +107,11 @@ You can update the deployment template. The changes will be automatically synchr
1. Update deployment replicas to 2
2. Display information of the deployment (the output is similar to this):
```shell
The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.

NAME CLUSTER READY UP-TO-DATE AVAILABLE AGE ADOPTION
nginx member2 2/2 2 2 7m59s Y
```
3. List the pods of the deployment (the output is similar to this):
```shell
The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.

NAME CLUSTER READY STATUS RESTARTS AGE
nginx-6799fc88d8-8t8cc member2 1/1 Running 0 8m12s
nginx-6799fc88d8-zpl4j member2 1/1 Running 0 17s
Expand Down
12 changes: 0 additions & 12 deletions ...saurus-plugin-content-docs/current/userguide/scheduling/resource-propagating.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,8 +52,6 @@ karmadactl get deployment
```
The output is similar to this:
```shell
The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.

NAME CLUSTER READY UP-TO-DATE AVAILABLE AGE ADOPTION
nginx member1 1/1 1 1 52s Y
```
Expand All @@ -64,8 +62,6 @@ karmadactl get pod -l app=nginx
```
The output is similar to this:
```shell
The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.

NAME CLUSTER READY STATUS RESTARTS AGE
nginx-6799fc88d8-s7vv9 member1 1/1 Running 0 52s
```
Expand Down Expand Up @@ -97,15 +93,11 @@ kubectl apply -f propagationpolicy-update.yaml
```
2. Display information of the deployment (the output is similar to this):
```shell
The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.

NAME CLUSTER READY UP-TO-DATE AVAILABLE AGE ADOPTION
nginx member2 1/1 1 1 5s Y
```
3. List the pods of the deployment (the output is similar to this):
```shell
The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.

NAME CLUSTER READY STATUS RESTARTS AGE
nginx-6799fc88d8-8t8cc member2 1/1 Running 0 17s
```
Expand All @@ -117,15 +109,11 @@ You can update the deployment template. The changes will be automatically synchr
1. Update deployment replicas to 2
2. Display information of the deployment (the output is similar to this):
```shell
The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.

NAME CLUSTER READY UP-TO-DATE AVAILABLE AGE ADOPTION
nginx member2 2/2 2 2 7m59s Y
```
3. List the pods of the deployment (the output is similar to this):
```shell
The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.

NAME CLUSTER READY STATUS RESTARTS AGE
nginx-6799fc88d8-8t8cc member2 1/1 Running 0 8m12s
nginx-6799fc88d8-zpl4j member2 1/1 Running 0 17s
Expand Down
14 changes: 0 additions & 14 deletions ...s-plugin-content-docs/version-v1.3/userguide/scheduling/resource-propagating.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,27 +45,21 @@ kubectl create deployment nginx --image nginx
> Note: The resource exists only as a template in karmada. After being propagated to a member cluster, the behavior of the resource is the same as that of a single kubernetes cluster.

> Note: Resources and PropagationPolicy are created in no sequence.

3. Display information of the deployment:
```shell
karmadactl get deployment
```
The output is similar to this:
```shell
The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.

NAME CLUSTER READY UP-TO-DATE AVAILABLE AGE ADOPTION
nginx member1 1/1 1 1 52s Y
```

4. List the pods created by the deployment:
```shell
karmadactl get pod -l app=nginx
```
The output is similar to this:
```shell
The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.

NAME CLUSTER READY STATUS RESTARTS AGE
nginx-6799fc88d8-s7vv9 member1 1/1 Running 0 52s
```
Expand Down Expand Up @@ -97,15 +91,11 @@ kubectl apply -f propagationpolicy-update.yaml
```
2. Display information of the deployment (the output is similar to this):
```shell
The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.

NAME CLUSTER READY UP-TO-DATE AVAILABLE AGE ADOPTION
nginx member2 1/1 1 1 5s Y
```
3. List the pods of the deployment (the output is similar to this):
```shell
The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.

NAME CLUSTER READY STATUS RESTARTS AGE
nginx-6799fc88d8-8t8cc member2 1/1 Running 0 17s
```
Expand All @@ -118,15 +108,11 @@ You can update the deployment template. The changes will be automatically synchr
1. Update deployment replicas to 2
2. Display information of the deployment (the output is similar to this):
```shell
The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.

NAME CLUSTER READY UP-TO-DATE AVAILABLE AGE ADOPTION
nginx member2 2/2 2 2 7m59s Y
```
3. List the pods of the deployment (the output is similar to this):
```shell
The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.

NAME CLUSTER READY STATUS RESTARTS AGE
nginx-6799fc88d8-8t8cc member2 1/1 Running 0 8m12s
nginx-6799fc88d8-zpl4j member2 1/1 Running 0 17s
Expand Down
14 changes: 0 additions & 14 deletions ...s-plugin-content-docs/version-v1.4/userguide/scheduling/resource-propagating.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,27 +45,21 @@ kubectl create deployment nginx --image nginx
> Note: The resource exists only as a template in karmada. After being propagated to a member cluster, the behavior of the resource is the same as that of a single kubernetes cluster.

> Note: Resources and PropagationPolicy are created in no sequence.

3. Display information of the deployment:
```shell
karmadactl get deployment
```
The output is similar to this:
```shell
The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.

NAME CLUSTER READY UP-TO-DATE AVAILABLE AGE ADOPTION
nginx member1 1/1 1 1 52s Y
```

4. List the pods created by the deployment:
```shell
karmadactl get pod -l app=nginx
```
The output is similar to this:
```shell
The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.

NAME CLUSTER READY STATUS RESTARTS AGE
nginx-6799fc88d8-s7vv9 member1 1/1 Running 0 52s
```
Expand Down Expand Up @@ -97,15 +91,11 @@ kubectl apply -f propagationpolicy-update.yaml
```
2. Display information of the deployment (the output is similar to this):
```shell
The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.

NAME CLUSTER READY UP-TO-DATE AVAILABLE AGE ADOPTION
nginx member2 1/1 1 1 5s Y
```
3. List the pods of the deployment (the output is similar to this):
```shell
The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.

NAME CLUSTER READY STATUS RESTARTS AGE
nginx-6799fc88d8-8t8cc member2 1/1 Running 0 17s
```
Expand All @@ -117,15 +107,11 @@ You can update the deployment template. The changes will be automatically synchr
1. Update deployment replicas to 2
2. Display information of the deployment (the output is similar to this):
```shell
The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.

NAME CLUSTER READY UP-TO-DATE AVAILABLE AGE ADOPTION
nginx member2 2/2 2 2 7m59s Y
```
3. List the pods of the deployment (the output is similar to this):
```shell
The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.

NAME CLUSTER READY STATUS RESTARTS AGE
nginx-6799fc88d8-8t8cc member2 1/1 Running 0 8m12s
nginx-6799fc88d8-zpl4j member2 1/1 Running 0 17s
Expand Down
12 changes: 0 additions & 12 deletions ...s-plugin-content-docs/version-v1.5/userguide/scheduling/resource-propagating.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,8 +52,6 @@ karmadactl get deployment
```
The output is similar to this:
```shell
The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.

NAME CLUSTER READY UP-TO-DATE AVAILABLE AGE ADOPTION
nginx member1 1/1 1 1 52s Y
```
Expand All @@ -64,8 +62,6 @@ karmadactl get pod -l app=nginx
```
The output is similar to this:
```shell
The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.

NAME CLUSTER READY STATUS RESTARTS AGE
nginx-6799fc88d8-s7vv9 member1 1/1 Running 0 52s
```
Expand Down Expand Up @@ -97,15 +93,11 @@ kubectl apply -f propagationpolicy-update.yaml
```
2. Display information of the deployment (the output is similar to this):
```shell
The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.

NAME CLUSTER READY UP-TO-DATE AVAILABLE AGE ADOPTION
nginx member2 1/1 1 1 5s Y
```
3. List the pods of the deployment (the output is similar to this):
```shell
The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.

NAME CLUSTER READY STATUS RESTARTS AGE
nginx-6799fc88d8-8t8cc member2 1/1 Running 0 17s
```
Expand All @@ -117,15 +109,11 @@ You can update the deployment template. The changes will be automatically synchr
1. Update deployment replicas to 2
2. Display information of the deployment (the output is similar to this):
```shell
The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.

NAME CLUSTER READY UP-TO-DATE AVAILABLE AGE ADOPTION
nginx member2 2/2 2 2 7m59s Y
```
3. List the pods of the deployment (the output is similar to this):
```shell
The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.

NAME CLUSTER READY STATUS RESTARTS AGE
nginx-6799fc88d8-8t8cc member2 1/1 Running 0 8m12s
nginx-6799fc88d8-zpl4j member2 1/1 Running 0 17s
Expand Down
12 changes: 0 additions & 12 deletions ...s-plugin-content-docs/version-v1.6/userguide/scheduling/resource-propagating.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,8 +52,6 @@ karmadactl get deployment
```
The output is similar to this:
```shell
The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.

NAME CLUSTER READY UP-TO-DATE AVAILABLE AGE ADOPTION
nginx member1 1/1 1 1 52s Y
```
Expand All @@ -64,8 +62,6 @@ karmadactl get pod -l app=nginx
```
The output is similar to this:
```shell
The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.

NAME CLUSTER READY STATUS RESTARTS AGE
nginx-6799fc88d8-s7vv9 member1 1/1 Running 0 52s
```
Expand Down Expand Up @@ -97,15 +93,11 @@ kubectl apply -f propagationpolicy-update.yaml
```
2. Display information of the deployment (the output is similar to this):
```shell
The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.

NAME CLUSTER READY UP-TO-DATE AVAILABLE AGE ADOPTION
nginx member2 1/1 1 1 5s Y
```
3. List the pods of the deployment (the output is similar to this):
```shell
The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.

NAME CLUSTER READY STATUS RESTARTS AGE
nginx-6799fc88d8-8t8cc member2 1/1 Running 0 17s
```
Expand All @@ -117,15 +109,11 @@ You can update the deployment template. The changes will be automatically synchr
1. Update deployment replicas to 2
2. Display information of the deployment (the output is similar to this):
```shell
The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.

NAME CLUSTER READY UP-TO-DATE AVAILABLE AGE ADOPTION
nginx member2 2/2 2 2 7m59s Y
```
3. List the pods of the deployment (the output is similar to this):
```shell
The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.

NAME CLUSTER READY STATUS RESTARTS AGE
nginx-6799fc88d8-8t8cc member2 1/1 Running 0 8m12s
nginx-6799fc88d8-zpl4j member2 1/1 Running 0 17s
Expand Down
12 changes: 0 additions & 12 deletions ...s-plugin-content-docs/version-v1.7/userguide/scheduling/resource-propagating.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,8 +52,6 @@ karmadactl get deployment
```
The output is similar to this:
```shell
The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.

NAME CLUSTER READY UP-TO-DATE AVAILABLE AGE ADOPTION
nginx member1 1/1 1 1 52s Y
```
Expand All @@ -64,8 +62,6 @@ karmadactl get pod -l app=nginx
```
The output is similar to this:
```shell
The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.

NAME CLUSTER READY STATUS RESTARTS AGE
nginx-6799fc88d8-s7vv9 member1 1/1 Running 0 52s
```
Expand Down Expand Up @@ -97,15 +93,11 @@ kubectl apply -f propagationpolicy-update.yaml
```
2. Display information of the deployment (the output is similar to this):
```shell
The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.

NAME CLUSTER READY UP-TO-DATE AVAILABLE AGE ADOPTION
nginx member2 1/1 1 1 5s Y
```
3. List the pods of the deployment (the output is similar to this):
```shell
The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.

NAME CLUSTER READY STATUS RESTARTS AGE
nginx-6799fc88d8-8t8cc member2 1/1 Running 0 17s
```
Expand All @@ -117,15 +109,11 @@ You can update the deployment template. The changes will be automatically synchr
1. Update deployment replicas to 2
2. Display information of the deployment (the output is similar to this):
```shell
The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.

NAME CLUSTER READY UP-TO-DATE AVAILABLE AGE ADOPTION
nginx member2 2/2 2 2 7m59s Y
```
3. List the pods of the deployment (the output is similar to this):
```shell
The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.

NAME CLUSTER READY STATUS RESTARTS AGE
nginx-6799fc88d8-8t8cc member2 1/1 Running 0 8m12s
nginx-6799fc88d8-zpl4j member2 1/1 Running 0 17s
Expand Down
Loading