diff --git a/Clusterkey.txt b/Clusterkey.txt
index 066d861..325062d 100644
--- a/Clusterkey.txt
+++ b/Clusterkey.txt
@@ -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 fukd6o.hwjap7wtnggqnvb0 \
-        --discovery-token-ca-cert-hash sha256:fb3b5db4e4df1a7be1eb4baf9afc7dc71c4dc6e26d6cf92e5bed6d4c6514bf72 \
-        --control-plane --certificate-key ac7755c7662c3b0ab865e3d91351a4096c7b9f0e73f0272a5e510f213fbdedce
+  kubeadm join 192.168.0.20:6443 --token 0xkqfe.jabbv1ti38pb5kcb \
+        --discovery-token-ca-cert-hash sha256:3f35741ffc7824dda6276c781cf279d689abe0798154c6789afefcebd4c4f0cb \
+        --control-plane --certificate-key 2f51db87d68e0f71bef56a5f1759d35d92361dbb8c2be5ec3ae653c68096e4d8
 
 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 fukd6o.hwjap7wtnggqnvb0 \
-        --discovery-token-ca-cert-hash sha256:fb3b5db4e4df1a7be1eb4baf9afc7dc71c4dc6e26d6cf92e5bed6d4c6514bf72
+kubeadm join 192.168.0.20:6443 --token 0xkqfe.jabbv1ti38pb5kcb \
+        --discovery-token-ca-cert-hash sha256:3f35741ffc7824dda6276c781cf279d689abe0798154c6789afefcebd4c4f0cb