Great question. Reason you see these errors is most likely because your account has a Kubernetes connection registered, however, that Kubernetes’s cluster is not currently available to the running Meshery server.
Meshery’s default behavior is to act in a greedy way in so much as to always ensure that a connected state Kubernetes connection has Meshery Operator installed in the cluster.
In context of Meshery Server, Layer5 Cloud, and Kubernetes clusters, communication and status is determined betwixt Meshery Server and Kubernetes cluster.
Cloud will retain a record of the connection and credential, so that it remains with your account.
Communication only occurs between Meshery Server and Kubernetes.
It might be the case that Meshery Server is able to communicate with Kubernetes cluster, however, that the Meshery Operator deployment is separately failing.
