Kubectl get componentstatus fails for scheduler and controller-manager

My k8S clusters are imported clusters.

My cluster version is rancher / rancher: v2.3.1

ALL CLUSTER HAVE THE SAME ERRORS
+++++++++++++++++++++++++++++++++++

To be more exact, I sometimes have these errors and sometimes I don’t have them.

All the cluster that you can see are identical and all have the same problem:

clusters_imported|690x105

JMONTERO CLUSTER:
++++++++++++++++++++++
For example:

In the Dasboard of jmontero Cluster ,You can see Controller Manager and Scheduler unhealthy:

but nevertheless the pods Controller Manager and Scheduler of jmontero cluster are always running fine as you can see in the folowing screen:

I dont undestan

THIS SMALL ERROR
+++++++++++++++++++++

However, I can manage the cluster well even if the Dashboard shows these errors.

I can scale up and down pods,delete pods, and take any action on my workloads.

The only thing is that it hurts the eye and for that simple and silly reason my bosses don’t let me put Rancher into production.

My boss say me, this causes confusion for operators, administrators of the clusters of k8s[quote=“jsanguino, post:1, topic:15801, full:true”]
Dood afternoon,

I have imported some clusters and the Rancher Dashboard can see the folowing alerts

Alert: Component controller-manager is unhealthy.

Alert: Component scheduler is unhealthy.

How can I fix this error?
[/quote]

Hi again,

As you can see the componentscontroll Manager and Scheulder in jmontero cluster are green now:

sas

But later they will appear in red.

What can I do to solve this behavior?