From 5b5ef9944c31377c57839297a191650245ed49e1 Mon Sep 17 00:00:00 2001 From: petroche Date: Mon, 28 Jul 2025 12:56:33 +0200 Subject: [PATCH] Actualizar Clusterkey.txt --- Clusterkey.txt | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/Clusterkey.txt b/Clusterkey.txt index 325062d..cced0f6 100644 --- a/Clusterkey.txt +++ b/Clusterkey.txt @@ -1,3 +1,5 @@ + + Your Kubernetes control-plane has initialized successfully! To start using your cluster, you need to run the following as a regular user: @@ -16,9 +18,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 0xkqfe.jabbv1ti38pb5kcb \ - --discovery-token-ca-cert-hash sha256:3f35741ffc7824dda6276c781cf279d689abe0798154c6789afefcebd4c4f0cb \ - --control-plane --certificate-key 2f51db87d68e0f71bef56a5f1759d35d92361dbb8c2be5ec3ae653c68096e4d8 + kubeadm join 192.168.0.20:6443 --token w75kwy.agecjz9xz1t6c230 \ + --discovery-token-ca-cert-hash sha256:8dec67e48df4b7e862b9fc43465d15d7dbc816c009bed5b094209f4d693b2500 \ + --control-plane --certificate-key d691e496da342743d4408be81b8a54712155cf89ba851e91805dd9a46412be2d 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 +28,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 0xkqfe.jabbv1ti38pb5kcb \ - --discovery-token-ca-cert-hash sha256:3f35741ffc7824dda6276c781cf279d689abe0798154c6789afefcebd4c4f0cb +kubeadm join 192.168.0.20:6443 --token w75kwy.agecjz9xz1t6c230 \ + --discovery-token-ca-cert-hash sha256:8dec67e48df4b7e862b9fc43465d15d7dbc816c009bed5b094209f4d693b2500