title: What is cluster-info configmap in TLS bootstrap in k8s?
body: <p>I was trying to TLS bootstrap a worker node to join my existing cluster of 1 master and  2 worker nodes. Below is the process which I followed -</p>
  
  <ol>
  <li>Create a bootstrap token on master for initial authentication.</li>
  <li>Create proper cluster role bindings for letting kubelet to raise, approve and rotate certificates.</li>
  <li>Create a bootstrap-kubeconfig file on worker node.</li>
  <li>Create a kubelet service and start it.</li>
  </ol>
  
  <p>All this works fine and my new worker node is able to join the cluster without any issues.</p>
  
  <p>But now I came across something called cluster-info configmap signing during the bootstrap process. <a href="https://kubernetes.io/docs/reference/access-authn-authz/bootstrap-tokens/" rel="nofollow noreferrer">link</a></p>
  
  <p>What exactly it is and how it helps me in the bootstrap process ? I went through k8s docs on but they don't give a lot of detail on this. All I know is you have to create a configmap with name cluster-info but not sure how &amp; why this is used.</p>
  
  <p>Thanks in advance !</p>
  
  <p>p.s - If there is any link where this process is elaborated in detail with practical examples then please share.</p>