From 5b5c9739c18837a76aa4f5a79ff48abe6280b721 Mon Sep 17 00:00:00 2001 From: xavor Date: Wed, 23 Jul 2025 22:45:25 +0000 Subject: [PATCH] Actualizar Clusterkey.txt --- Clusterkey.txt | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/Clusterkey.txt b/Clusterkey.txt index 5d6ebc8..15196c1 100644 --- a/Clusterkey.txt +++ b/Clusterkey.txt @@ -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 5ze0il.1gsjideun93rvzk0 \ - --discovery-token-ca-cert-hash sha256:ee11899c8d2ab7c6c44abc1b49ee249c53d457677b717723497c32e3ce216010 \ - --control-plane --certificate-key 65b4a316ccfafd5ea6c5fa12eb4012fed142bae70f73747049fa46a94903019f + kubeadm join 192.168.0.20:6443 --token iksja1.azpmfyakfg3j8q98 \ + --discovery-token-ca-cert-hash sha256:d41f0edb90c66c0555bdf4feca55f1e69019764be0fcd649a254e99ff124568f \ + --control-plane --certificate-key 06034ca8efb33004a3ee5eedbe887488db9819ede85394e8fb173361b16d4022 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 5ze0il.1gsjideun93rvzk0 \ - --discovery-token-ca-cert-hash sha256:ee11899c8d2ab7c6c44abc1b49ee249c53d457677b717723497c32e3ce216010 +kubeadm join 192.168.0.20:6443 --token iksja1.azpmfyakfg3j8q98 \ + --discovery-token-ca-cert-hash sha256:d41f0edb90c66c0555bdf4feca55f1e69019764be0fcd649a254e99ff124568f