-
Notifications
You must be signed in to change notification settings - Fork 3
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.
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
add killercoda example: install karmada through CLI #2
Conversation
Welcome @JadeFlute0127! It looks like this is your first PR to karmada-io/playground 🎉 |
Please replace the word |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great job! Just some nits.
We currently do not require the killercoda-sample
directory.
killercoda-sample/karmada-CLI-installtion-example/foreground.sh
Outdated
Show resolved
Hide resolved
killercoda-sample/karmada-CLI-installtion-example/foreground.sh
Outdated
Show resolved
Hide resolved
010fab3
to
412a7d0
Compare
I think these problems have been solved~ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other looks good to me
Could you please share the scenario link for your experiment on Killercoda? |
https://killercoda.com/zhangdiandian/scenario/karmada-CLI-installtion-and-deploy-example |
} | ||
|
||
function scpOperations() { | ||
scp installKind.sh root@${member_cluster_ip}:~ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
how about the name copyConfigFilesToNode
?
``` | ||
3. join member clusters(kind-member1 and kind-member2)to karmada cluster | ||
|
||
```shell |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tried the example, but it requires manual input from you.
How about this one, just click,it will exec the command?
https://killercoda.com/kubevela/course/quick-start/kubevela-first-app
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The MD file should specify that the subsequent operations can only be performed after the kind cluster is prepared.
KUBECONFIG_PATH=${KUBECONFIG_PATH:-"${HOME}/.kube"} | ||
|
||
function installKind() { | ||
cat << EOF > installKind.sh |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please leave a space of four. other places should be the same
03e5232
to
5d9e9f8
Compare
fix done |
@@ -0,0 +1,43 @@ | |||
### Background: | |||
|
|||
1. The kubeconfig files for the Karmada cluster, member1 cluster, and member2 cluster are located in the $HOME/.kube directory. These files are named config, config-member1, and config-member2 respectively. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't usually say Karmada cluster
, if you mean the cluster where installing Karmada, I'd prefer to use host cluster
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for pointing out
8c7b554
to
9201620
Compare
@@ -0,0 +1,3 @@ | |||
#!/bin/bash | |||
|
|||
kubectl --kubeconfig=$HOME/.kube/config-member1 config get-contexts kind-member1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add a line break, same as in other places.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this comment hasn't been addressed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok
cc @RainbowMango, could you please review this? Overall, it looks good to me. |
Sure. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally looks good to me. Just some small touches.
- I see you name the steps by
step1
/spep2
..., can we give them meaningful names? - Do we need
verification
for each steps?
@@ -0,0 +1,38 @@ | |||
{ | |||
"title": "install Karmada cluster through CLI", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't usually say Karmada cluster
. How about
"title": "install Karmada cluster through CLI", | |
"title": "install Karmada through CLI", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@@ -0,0 +1,38 @@ | |||
{ | |||
"title": "install Karmada cluster through CLI", | |||
"description": "Installing a Karmada cluster with Kubernetes member through the Karmada CLI", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"description": "Installing a Karmada cluster with Kubernetes member through the Karmada CLI", | |
"description": "Installing Karmada on Kubernetes through the Karmada CLI", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok
@@ -0,0 +1,3 @@ | |||
#!/bin/bash | |||
|
|||
kubectl --kubeconfig=$HOME/.kube/config-member1 config get-contexts kind-member1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this comment hasn't been addressed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need a new line at end of file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need a new line at end of this file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add a newline at end of this file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fix done
@@ -0,0 +1 @@ | |||
**The end** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It'd be great to have a summarize of this playground and make rooms for guiding people to other scenarios.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will add the summary section.
Do you mean to switch to other scenes in Karmada? Other scenarios have not yet been implemented, and the website provides links to other scenarios in Killercoda.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For now, since we don't have any other scenarios yet, so a summary would be fine.
But in the future, we might need to add links to other scenarios for people to experience other features.
it looks fix done |
I think that the following steps require the completion of the previous steps. |
/lgtm |
@@ -0,0 +1,3 @@ | |||
**Summary** | |||
|
|||
In this scenario, we learned how to initialize the Karmada control plane, join a cluster, and deploy workloads across multiple clusters. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and deploy workloads across multiple clusters
Seems we didn't have the step for deploying workloads, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We plan to work on it separately, and it should be completed in the next PR.
|
||
Karmada aims to provide turnkey automation for multi-cluster application management in multi-cloud and hybrid cloud scenarios, with key features such as centralized multi-cloud management, high availability, failure recovery, and traffic scheduling. | ||
|
||
In this scenario, we will learn how to initialize the Karmada control plane, join clusters, and deploy workloads across multiple clusters. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ditto.
cc @jwcesign
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
remove about deploy workload info in intro.md and finish.md |
|
||
Karmada aims to provide turnkey automation for multi-cluster application management in multi-cloud and hybrid cloud scenarios, with key features such as centralized multi-cloud management, high availability, failure recovery, and traffic scheduling. | ||
|
||
In this scenario, we will learn how to initialize the Karmada control plane, join clusters. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In this scenario, we will learn how to initialize the Karmada control plane and join clusters.
@@ -0,0 +1,3 @@ | |||
**Summary** | |||
|
|||
In this scenario, we learned how to initialize the Karmada control plane, join a cluster. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In this scenario, we learned how to initialize the Karmada control plane and join a cluster.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, thank you for your pointing out, that's a typo.
I think fix done.
Signed-off-by: zhangdiandian <1635468471@qq.com>
/lgtm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/hold cancel
Signed-off-by: [JadeFlute0127] [1635468471@qq.com]
What this PR does / why we need it:
add killercoda example: install karmada through CLI
Which issue(s) this PR fixes:
Part of #1
Special notes for your reviewer:
Does this PR introduce a user-facing change?: