-
Notifications
You must be signed in to change notification settings - Fork 3
karmada init on existing cluster
sonyafenge edited this page Jan 25, 2023
·
2 revisions
ubuntu@karmada-host:~$ curl -s https://raw.githubusercontent.com/karmada-io/karmada/master/hack/install-cli.sh | sudo bash -s kubectl-karmada
ubuntu@karmada-host:~$ kubectl-karmada version
kubectl karmada version: version.Info{GitVersion:"v1.4.1", GitCommit:"4c56b19a6ba8258399767b4cd5f98779a321f7db", GitTreeState:"clean", BuildDate:"2022-12-15T09:47:49Z", GoVersion:"go1.19.4", Compiler:"gc", Platform:"linux/amd64"}
Karmada init Tips : ensure master nodes for Karmada host can be scheduled, remove taint
kubectl taint nodes --all node-role.kubernetes.io/control-plane-
sudo kubectl karmada init --kubeconfig /home/ubuntu/.kube/config
Karmada join Tips : Ensure current-context of member cluster config is match with Karmada’s name request, if not, please add context alias for join
kubectl config view
kubectl config set-context karmada-member1 --cluster=kubernetes --user=kubernetes-admin
kubectl config use-context karmada-member1
kubectl config current-context
- Copy kubeconfig from member master to karmada host
- Run karmada join
MEMBER_CLUSTER_NAME=$(cat ~/.kube/member1_config | grep current-context | sed 's/: /\n/g'| sed '1d')
echo $MEMBER_CLUSTER_NAME
kubectl karmada --kubeconfig /etc/karmada/karmada-apiserver.config join ${MEMBER_CLUSTER_NAME} --cluster-kubeconfig=$HOME/.kube/member1_config
ubuntu@karmada-host:~$ kubectl --kubeconfig /etc/karmada/karmada-apiserver.config get clusters
NAME VERSION MODE READY AGE
karmada-member1 v1.26.0 Push True 87s
refer https://karmada.io/docs/get-started/nginx-example/ to get more details related karmada