Actualizar Clusterkey.txt

This commit is contained in:
petroche
2025-07-29 11:51:57 +02:00
parent 1d19b512e7
commit 883ec48283

View File

@@ -1,32 +1 @@
Your Kubernetes control-plane has initialized successfully!
To start using your cluster, you need to run the following as a regular user:
mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config
Alternatively, if you are the root user, you can run:
export KUBECONFIG=/etc/kubernetes/admin.conf
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 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
"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.0.20:6443 --token w75kwy.agecjz9xz1t6c230 \
--discovery-token-ca-cert-hash sha256:8dec67e48df4b7e862b9fc43465d15d7dbc816c009bed5b094209f4d693b2500
kubeadm join 192.168.0.20:6443 --token rvz86n.c8rdb9ygtikrwnub --discovery-token-ca-cert-hash sha256:f925653dfb3d2b4697395a272e0b07cf4eb16b7ae5a2cc3b33aeab1f36fe7d13 --control-plane --certificate-key eeab98651b2f07f6ce53649b2cca1bf3c449d4fe6270ec0645219cd8c6795ca7 --apiserver-advertise-address=192.168.4.2