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:
xavor
2025-07-23 12:01:27 +00:00
parent 2cf9556f63
commit 52d1503daf
1 changed files with 13 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
Clusterkey.txt
View File

@ -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:
@ -14,7 +15,17 @@ You should now deploy a pod network to the cluster.
Run "kubectl apply -f [podnetwork].yaml" with one of the options listed at:
https://kubernetes.io/docs/concepts/cluster-administration/addons/
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
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
"kubeadm init phase upload-certs --upload-certs" to reload certs afterward.
Then you can join any number of worker nodes by running the following on each as root:
kubeadm join 192.168.4.1:6443 --token schru5.x8r6hfjye1oifkzv \
--discovery-token-ca-cert-hash sha256:eb7cfc30a89635b986111641eb6c6ae8767e5bd510be75b45bdac976e5f05959
kubeadm join 192.168.0.20:6443 --token uj81es.cg9kog8blbh5s10r \
--discovery-token-ca-cert-hash sha256:39d7f802768f2a09cb5e00476f949e0db5fe06b3631fe5893570cf14ed86940d