xavor/kubernetes
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Actualizar Clusterkey.txt

Browse Source
This commit is contained in:
xavor
2025-07-23 19:59:57 +00:00
parent 167d6a6329
commit 72b9526cee
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
Clusterkey.txt
View File

@ -16,9 +16,9 @@ Run "kubectl apply -f [podnetwork].yaml" with one of the options listed at:
You can now join any number of control-plane nodes running the following command on each as root:
kubeadm join 192.168.0.20:6443 --token wg0s2g.lbnur25vlznfgz5u \
--discovery-token-ca-cert-hash sha256:27edbaad29f1a2202190b4b968ca6f24072225c6b3f477af29496742a58d2385 \
--control-plane --certificate-key a3063e4f7b57f168220421a9440f430e5b0cee37b772b16189e942c5bf9dc9e7
kubeadm join 192.168.0.20:6443 --token 5ze0il.1gsjideun93rvzk0 \
--discovery-token-ca-cert-hash sha256:ee11899c8d2ab7c6c44abc1b49ee249c53d457677b717723497c32e3ce216010 \
--control-plane --certificate-key 65b4a316ccfafd5ea6c5fa12eb4012fed142bae70f73747049fa46a94903019f
Please note that the certificate-key gives access to cluster sensitive data, keep it secret!
As a safeguard, uploaded-certs will be deleted in two hours; If necessary, you can use
@ -26,5 +26,5 @@ As a safeguard, uploaded-certs will be deleted in two hours; If necessary, you c
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 wg0s2g.lbnur25vlznfgz5u \
--discovery-token-ca-cert-hash sha256:27edbaad29f1a2202190b4b968ca6f24072225c6b3f477af29496742a58d2385
kubeadm join 192.168.0.20:6443 --token 5ze0il.1gsjideun93rvzk0 \
--discovery-token-ca-cert-hash sha256:ee11899c8d2ab7c6c44abc1b49ee249c53d457677b717723497c32e3ce216010