Actualizar Clusterkey.txt
This commit is contained in:
@ -1,4 +1,3 @@
|
||||
|
||||
Your Kubernetes control-plane has initialized successfully!
|
||||
|
||||
To start using your cluster, you need to run the following as a regular user:
|
||||
@ -17,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 uj81es.cg9kog8blbh5s10r \
|
||||
--discovery-token-ca-cert-hash sha256:39d7f802768f2a09cb5e00476f949e0db5fe06b3631fe5893570cf14ed86940d \
|
||||
--control-plane --certificate-key a1cf76052b4e90ad2cce60334ae79f28cfaefc3ff4ccf405deedb8fe22fe4236
|
||||
kubeadm join 192.168.0.20:6443 --token wg0s2g.lbnur25vlznfgz5u \
|
||||
--discovery-token-ca-cert-hash sha256:27edbaad29f1a2202190b4b968ca6f24072225c6b3f477af29496742a58d2385 \
|
||||
--control-plane --certificate-key a3063e4f7b57f168220421a9440f430e5b0cee37b772b16189e942c5bf9dc9e7
|
||||
|
||||
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
|
||||
@ -27,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 uj81es.cg9kog8blbh5s10r \
|
||||
--discovery-token-ca-cert-hash sha256:39d7f802768f2a09cb5e00476f949e0db5fe06b3631fe5893570cf14ed86940d
|
||||
kubeadm join 192.168.0.20:6443 --token wg0s2g.lbnur25vlznfgz5u \
|
||||
--discovery-token-ca-cert-hash sha256:27edbaad29f1a2202190b4b968ca6f24072225c6b3f477af29496742a58d2385
|
||||
|
Reference in New Issue
Block a user