commit c114baf7c2941020d3ac57b01c486cc3deb22b39 parent 63f51b371676fc14ec196fe55d9d5b0e31d9aaf9 Author: Minerva_juppiter <94231606+minerva-jupiter@users.noreply.github.com> Date: Mon, 14 Jul 2025 19:19:32 +0900 Update memo.md Diffstat:
| M | k8s/memo.md | | | 25 | +++++++++++++++++++++++++ |
1 file changed, 25 insertions(+), 0 deletions(-)
diff --git a/k8s/memo.md b/k8s/memo.md @@ -2,3 +2,28 @@ ip table ||| |ironkube-con|20| |ironkube-work01|16| + +``` +kubeadm join 192.168.0.20:6443 --token zt030g.2dtrbf8zeq0ubqj8 \ + --discovery-token-ca-cert-hash sha256:58d950d150754c3f73fef844eba6e905335ce8172ba920f9a8fbefce2cfd720e +``` + +``` +Your Kubernetes control-plane has initialized successfully! + To start using your cluster, you need to run the following as a regular user: + + mkdir -p $HOME/.kube + sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config + sudo chown $(id -u):$(id -g) $HOME/.kube/config + Alternatively, if you are the root user, you can run: + + export KUBECONFIG=/etc/kubernetes/admin.conf + +You should now deploy a pod network to the cluster. +Run "kubectl apply -f [podnetwork].yaml" with one of the options listed at: https://kubernetes.io/docs/concepts/cluster-administration/addons/ + +Then you can join any number of worker nodes by running the following on each as root: +kubeadm join 192.168.0.20:6443 --token zt030g.2dtrbf8zeq0ubqj8 \ + --discovery-token-ca-cert-hash sha256:58d950d150754c3f73fef844eba6e905335ce8172ba920f9a8fbefce2cfd720e +tetsu@ironkube-con:~$ kubectl get nodes +```