Actualizar Clusterkey.txt

This commit is contained in:
2025-07-23 22:45:25 +00:00
parent a39dd91832
commit 5b5c9739c1

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: 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 5ze0il.1gsjideun93rvzk0 \ kubeadm join 192.168.0.20:6443 --token iksja1.azpmfyakfg3j8q98 \
--discovery-token-ca-cert-hash sha256:ee11899c8d2ab7c6c44abc1b49ee249c53d457677b717723497c32e3ce216010 \ --discovery-token-ca-cert-hash sha256:d41f0edb90c66c0555bdf4feca55f1e69019764be0fcd649a254e99ff124568f \
--control-plane --certificate-key 65b4a316ccfafd5ea6c5fa12eb4012fed142bae70f73747049fa46a94903019f --control-plane --certificate-key 06034ca8efb33004a3ee5eedbe887488db9819ede85394e8fb173361b16d4022
Please note that the certificate-key gives access to cluster sensitive data, keep it secret! 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 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: 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 5ze0il.1gsjideun93rvzk0 \ kubeadm join 192.168.0.20:6443 --token iksja1.azpmfyakfg3j8q98 \
--discovery-token-ca-cert-hash sha256:ee11899c8d2ab7c6c44abc1b49ee249c53d457677b717723497c32e3ce216010 --discovery-token-ca-cert-hash sha256:d41f0edb90c66c0555bdf4feca55f1e69019764be0fcd649a254e99ff124568f