rancher: Imported AKS clusters show in error. Can we mark Imported AKS to silence alarms?

What kind of request is this (question/bug/enhancement/feature request): Enhancement/Bug

Steps to reproduce (least amount of steps as possible):

Create AKS Cluster in Azure Portal
Create Cluster in Rancher, select import
Run kubectl command to import AKS Cluster in Rancher

Result:

Rancher will show the cluster in error. Specifically the Controller Manager and Scheduler are shown as unhealthy. This is already a known upstream k8s bug from rancher/rancher#23451

Other details that may be helpful:

If you create an AKS cluster, Rancher seems to know that it’s managed and will gray out those errors and ignore. Ideally, there would be a way to annotate if the imported cluster is from a managed service so the same “feature” of ignoring the error could be used.
This could affect other cloud providers EKS or GKE.

Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): v2.3.1
Installation option (single install/HA): HA

gz#11712

gz#12343

About this issue

Original URL
State: closed
Created 5 years ago
Reactions: 11
Comments: 15 (1 by maintainers)

Most upvoted comments

Same issue here on Rancher version 2.4.4 and AKS 1.16.9

spmoreno on Jul 8, 2020

@codyrancher I was hoping that we could use an annotation or some configuration options to disable to monitoring of the scheduler and controller manager. I don’t need Rancher to figure it out. I’m more than happy to just not have an imported Managed-Kubernetes show as in error. Is not helpful because there are times where the cluster is in error, but we ignore because the icon is always there.

slessardjr on Jun 6, 2020

Summary of this issue as of November '20

We can’t see the component status for controller manager or scheduler for AKS clusters, this is a bug inside AKS.
ComponentStatus itself is being deprecated starting in 1.19, which is why AKS isn’t fixing the bug.
For Rancher created AKS clusters we simply hide these components (17344), but for imported clusters we don’t know its AKS and therefore can’t hide.
In the medium/long term for 2.5.x we’ll handle the deprecation of component status by transitioning to something else which would ideally also work on AKS imported clusters https://github.com/rancher/rancher/issues/28943
The proposed (2.4 compatible) alternative is the annotation PR above. Beyond that we could also look into better identifying imported clusters.

cbron on Nov 9, 2020

I have this problem for a while and found this issue now. Can’t UI team check out a good way to mute the alert and warning? Or check out the nodes’ system info?

elvishsu66 on May 29, 2020

v2.3.3 same issue

ThEWiZ76 on Dec 18, 2019