text: Title: master node becomes worker nodes after network partition
  Body: ### What happened?
  
  When the master node is deleted from k8s cluster due to some network failures, Cloud Provider Controller Manager notices that this node VM is no longer present on the cloud provider due to network partition, so Cloud Provider Controller Manager will remove this node from the cluster. 
  Later when this node is added back to k8s cluster, it is added back without the required master node taints/labels.
  The master node become worker node and some pods are scheduled to that node by mistake and can not be running.
  
  Tho the current behavior of deleting node VM from Cloud Provider when VM failover is on-going is expected, but when the node is re-registered, it should get the same role and behavior as before. And this master role label is added by kubelet.
  
  I'm wondering if this is the expected behavior of kubelet or is that something to be fixed?
  
  
  ### What did you expect to happen?
  
  The master role label should be added to the node when it's re-registered.
  
  ### How can we reproduce it (as minimally and precisely as possible)?
  
  1. delete the master node
  2. re-register the node via kubelet
  3. see the master role label is deleted from the node
  
  ### Anything else we need to know?
  
  _No response_
  
  ### Kubernetes version
  
  <details>
  
  ```console
  $ kubectl version
  # paste output here
  1.21
  ```
  
  </details>
  
  
  ### Cloud provider
  
  <details>
  1.21
  </details>
  
  
  ### OS version
  
  <details>
  
  ```console
  # On Linux:
  $ cat /etc/os-release
  # paste output here
  $ uname -a
  # paste output here
  
  # On Windows:
  C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
  # paste output here
  ```
  
  </details>
  
  
  ### Install tools
  
  <details>
  
  </details>
  
  
  ### Container runtime (CRI) and and version (if applicable)
  
  <details>
  
  </details>
  
  
  ### Related plugins (CNI, CSI, ...) and versions (if applicable)
  
  <details>
  
  </details>
  