How does Rancher manage the state of K8S components

This article introduces the knowledge of "how Rancher manages the state of K8S components". In the operation of actual cases, many people will encounter such a dilemma, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

Recently installed K8s, component controller-manager and scheduler status Unhealthy through kubeadm

The import to Rancher2.4.5 is shown as follows:

Check the cluster status by installing kubernetes v1.18.6 through kubeadm, and find the component controller-manager and scheduler status Unhealthy

Check that the port is not listening

The pod component is running normally

Check that non-secure ports are disabled in the kube-scheduler and kube-controller-manager component configuration

Vim / etc/kubernetes/manifests/kube-scheduler.yaml

Vim / etc/kubernetes/manifests/kube-controller-manager.yaml

Kube-scheduler.yaml

Kube-controller-manager.yaml

Remove the port=0 (comments are added to the screenshot)

And then systemctl restart kubelet

Check again that the status of the cluster components is normal.

This is the end of the content of "how Rancher manages the state of K8S components". Thank you for reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!