Connection Between Cluster Scheduling Components and Kubernetes Clusters Is Abnormal

Symptom

The connection between cluster scheduling components and the Kubernetes clusters is abnormal.

Causes

The KubeConfig file has been imported to node B in Kubernetes cluster A. After node B is added to a new Kubernetes cluster, the imported KubeConfig file is used by default during component startup.

Solution

• If the component is started using the ServiceAccount, find and delete the KubeConfig file corresponding to the component based on Table 5, and then delete the corresponding pod.
• If the component is started by importing the KubeConfig file, import the new KubeConfig file and delete the pod.