Cluster Scheduling Components Fail to Connect Kubernetes

Symptom

The cluster scheduling components fail to connect Kubernetes.

Cause Analysis

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

Solution

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