Read-only archive. These discussions are from Tracston's earlier
technical forum and are kept online because the answers are still useful.
New replies are closed. Need help with something like this?
Talk to us.
Question
15 Oct 2020
When installing a Kubernetes cluster a token is first initialized to add new workers nodes to the cluster. ** Tokens only available for 24-hours, after that you will not be able to add new worker nodes with the same token. This Guide allows you to add more workers to an existing cluster after 24 hours of token expiration
Managing your Cluster’s Tokens
Using the kubeadm command, list your current tokens. (after 24 hours since the cluster was initialized, the list will likely be empty )
kubeadm token list
Create a new token using kubeadm.
* By using the –print-join-command argument kubeadm will output the token and SHA hash required to securely communicate with the master.
kubeadm token create –print-join-command
Use kubeadm to list all tokens in order to verify the newly created token.
kubeadm tokens list
Joining the New Worker to the Cluster
With our new token generated for the next 24 Hours add the new worker to the cluster with the following commandsFirst Login with SSH to the new worker node you configured
With our new token generated for the next 24 Hours add the new worker to the cluster with the following commandsFirst Login with SSH to the new worker node you configured
ssh username@192.168.1.130
Use the kubeadm join command with the new token to join the node to our cluster.
kubeadm join 192.168.1.130:6443 –token qt57zu.wuvqh64un13trr7x –discovery-token-ca-cert-hash sha256:5ad014cad868fdfe9388d5b33796cf40fc1e8c2b3dccaebff0b066a0532e8723
List & Verify cluster’s nodes .
kubectl get nodes
Verify that the worker’s status to ensure no errors encountered.
kubectl get nodes my-new-node
Need this fixed properly?
We do this for a living.
Kubernetes, DevOps and platform engineering, delivered in days — not another weekend lost to a stack trace.
Start a project →