Modified the Karmada tutorial description #614
Conversation
karmada-bot
added
the
kind/documentation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
karmada-bot
added
the
size/M
Signed-off-by: Shivansh Bhatnagar <shivansh.bhatnagar.mat22@itbhu.ac.in>
Signed-off-by: Shivansh Bhatnagar <shivansh.bhatnagar.mat22@itbhu.ac.in>
shivansh-bhatnagar18
force-pushed
the
resourcemigrationdocs
branch
from
8697ac6
to
c0e2471
Compare
|
|
||
| ```shell | ||
| $ kubectl --context karmada-apiserver apply -f /tmp/pp-for-nginx-app.yaml | ||
| kubectl --context karmada-apiserver apply -f /tmp/pp-for-nginx-app.yaml |
There was a problem hiding this comment.
| kubectl --context karmada-apiserver apply -f /tmp/pp-for-nginx-app.yaml | |
| $ kubectl --context karmada-apiserver apply -f /tmp/pp-for-nginx-app.yaml |
This $ can be remained. Line 1 is command and line 2 is output.
|
|
||
| ```shell | ||
| kubectl --context member1 get deploy -o wide |
There was a problem hiding this comment.
| kubectl --context member1 get deploy -o wide | |
| $ kubectl --context member1 get deploy -o wide |
| nginx-deploy 2/2 2 2 5m24s nginx nginx:latest app=nginx | ||
|
|
||
| kubectl --context member1 get svc -o wide |
There was a problem hiding this comment.
| kubectl --context member1 get svc -o wide | |
| $ kubectl --context member1 get svc -o wide |
|
|
||
| ```shell | ||
| kubectl --context member2 get deploy -o wide |
There was a problem hiding this comment.
| kubectl --context member2 get deploy -o wide | |
| $ kubectl --context member2 get deploy -o wide |
| nginx-deploy 2/2 2 2 5m24s nginx nginx:latest app=nginx | ||
|
|
||
| kubectl --context member2 get svc -o wide |
There was a problem hiding this comment.
| kubectl --context member2 get svc -o wide | |
| $ kubectl --context member2 get svc -o wide |
| ``` | ||
|
|
||
| This confirms that the higher priority `PropagationPolicy` has effectively propagated the `nginx` application resources to both `member1` and `member2` clusters, meeting the desired propagation requirements. |
There was a problem hiding this comment.
| This confirms that the higher priority `PropagationPolicy` has effectively propagated the `nginx` application resources to both `member1` and `member2` clusters, meeting the desired propagation requirements. | |
| This confirms that the higher priority `PropagationPolicy` has effectively propagated the `nginx` application | |
| resources to both `member1` and `member2` clusters, meeting the desired propagation requirements. |
Wrapping long lines can make it prettier in the editing mode.
|
|
||
|
|
There was a problem hiding this comment.
hi, why here added two empty line?
| You should see the `nginx` application related resources originally in `member1` also propagated to `member2`, completing the migration of resources : |
There was a problem hiding this comment.
Thank you for finding and correcting the mistake here!
|
I'm so sorry that I missed this PR. Do you still have time to fix the comment above? We will merge it ASAP. |
What type of PR is this?
/kind documentation
What this PR does / why we need it
Initially, the resource migration documentation led to a misunderstanding that the
nginxapplication-related resources are propagated tomember2but they are also propagated tomember1Which issue(s) this PR fixes:
Fixes #486