CKS Lab-Use Bootstrap token for authentication Q.4

On the 4th question, the node join hangs indefinetely:

You need to ensure you are consistent with the token-id and token-secret throughout the lab.

  • In Q2 it gives you these values with which you create the token secret.
  • In Q3 you need to create a join command with “random values”. Note that we are doing a dry run here. The reason for this is simply to get the cert hash. If you look in the solution to this question, we change only one hex digit in the token-id from the previous question to make it easier to edit the command for the next question.
  • In Q4 you are instructed to join the node using the bootstrap token created in Q2 which means you need to join it using 07401b.f395accd246ae52d, not a random value because the node-join secret for that value doesn’t exist.