Actualizar Clusterkey.txt
This commit is contained in:
@@ -1,3 +1,4 @@
|
||||
|
||||
Your Kubernetes control-plane has initialized successfully!
|
||||
|
||||
To start using your cluster, you need to run the following as a regular user:
|
||||
@@ -16,9 +17,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 iksja1.azpmfyakfg3j8q98 \
|
||||
--discovery-token-ca-cert-hash sha256:d41f0edb90c66c0555bdf4feca55f1e69019764be0fcd649a254e99ff124568f \
|
||||
--control-plane --certificate-key 06034ca8efb33004a3ee5eedbe887488db9819ede85394e8fb173361b16d4022
|
||||
kubeadm join 192.168.0.20:6443 --token fukd6o.hwjap7wtnggqnvb0 \
|
||||
--discovery-token-ca-cert-hash sha256:fb3b5db4e4df1a7be1eb4baf9afc7dc71c4dc6e26d6cf92e5bed6d4c6514bf72 \
|
||||
--control-plane --certificate-key ac7755c7662c3b0ab865e3d91351a4096c7b9f0e73f0272a5e510f213fbdedce
|
||||
|
||||
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 +27,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 iksja1.azpmfyakfg3j8q98 \
|
||||
--discovery-token-ca-cert-hash sha256:d41f0edb90c66c0555bdf4feca55f1e69019764be0fcd649a254e99ff124568f
|
||||
kubeadm join 192.168.0.20:6443 --token fukd6o.hwjap7wtnggqnvb0 \
|
||||
--discovery-token-ca-cert-hash sha256:fb3b5db4e4df1a7be1eb4baf9afc7dc71c4dc6e26d6cf92e5bed6d4c6514bf72
|
||||
|
||||
Reference in New Issue
Block a user