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:
petroche
2025-07-28 12:56:33 +02:00
parent 3664a46cc3
commit 5b5ef9944c
1 changed files with 7 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
Clusterkey.txt
View File

@@ -1,3 +1,5 @@
Your Kubernetes control-plane has initialized successfully! Your Kubernetes control-plane has initialized successfully!
To start using your cluster, you need to run the following as a regular user: 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: 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 \ kubeadm join 192.168.0.20:6443 --token w75kwy.agecjz9xz1t6c230 \
--discovery-token-ca-cert-hash sha256:3f35741ffc7824dda6276c781cf279d689abe0798154c6789afefcebd4c4f0cb \ --discovery-token-ca-cert-hash sha256:8dec67e48df4b7e862b9fc43465d15d7dbc816c009bed5b094209f4d693b2500 \
--control-plane --certificate-key 2f51db87d68e0f71bef56a5f1759d35d92361dbb8c2be5ec3ae653c68096e4d8 --control-plane --certificate-key d691e496da342743d4408be81b8a54712155cf89ba851e91805dd9a46412be2d
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 +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: 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 \ kubeadm join 192.168.0.20:6443 --token w75kwy.agecjz9xz1t6c230 \
--discovery-token-ca-cert-hash sha256:3f35741ffc7824dda6276c781cf279d689abe0798154c6789afefcebd4c4f0cb --discovery-token-ca-cert-hash sha256:8dec67e48df4b7e862b9fc43465d15d7dbc816c009bed5b094209f4d693b2500