You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I am connecting to a cluster running in Rancher Desktop but Conductor is showing the control plane as not running whilst also showing that the injector, operator, placement and sentry are all running.
To Reproduce
Install Rancher Desktop 1.13.1, deploy the conductor agent and dapr to the cluster.
Expected behavior
To either show that the control plane is running or to show what the problem is.
Screenshots
Additional context
I'm new to Kubernetes and Dapr so the problem could be with my setup, but I was hoping Conductor would provide more insights.
The text was updated successfully, but these errors were encountered:
We have identified and fixed an issue that is the likely cause of the discrepancy.
Apart from this issue, were you able to deploy apps and see insights about them? Please note, we haven't tested Conductor with Rancher/K3S - see supported k8s distros, which might be the reason for this behavior.
Are you able to try Conductor again and tell me if it is fixed?
Describe the bug
I am connecting to a cluster running in Rancher Desktop but Conductor is showing the control plane as not running whilst also showing that the injector, operator, placement and sentry are all running.
To Reproduce
Install Rancher Desktop 1.13.1, deploy the conductor agent and dapr to the cluster.
Expected behavior
To either show that the control plane is running or to show what the problem is.
Screenshots
Additional context
I'm new to Kubernetes and Dapr so the problem could be with my setup, but I was hoping Conductor would provide more insights.
The text was updated successfully, but these errors were encountered: