I’m running a Minikube cluster on Windows 11 and was able to successfully deploy Meshery on it, but it doesn’t detect the cluster, and the dashboard stops working after about a minute - reloading or clicking any button doesn’t work
Steps followed:
Started Minikube and enabled Metallb addon according to this guide
Ran minikube tunnel
Ran the make command in mesheryctl folder
Ran mesheryctl system start. Succesfully deployed, dashboard opened in browser, logged in, shows that no clusters are available
Ran mesheryctl system login, logged in succesfully
Ran mesheryctl system config minikube and got the following output:
Configuring Meshery to access Minikube...
Error getting context: no contexts found
Ran mesheryctl system check and this was the output:
Kubernetes API
--------------
✓ can initialize Kubernetes client
✓ can query the Kubernetes API
Kubernetes Version
--------------
✓ running the minimum Kubernetes version
✓ running the minimum kubectl version
Meshery Version
--------------
✓ Meshery Server is up-to-date (stable-v0.8.93)
!! CLI is not up-to-date (stable-)
Meshery Components
--------------
- No components configured in current context
Meshery Operators
--------------
✓ Meshery Operator is running
✓ Meshery Broker is running
!! Meshsync is not running
@SriramKa, assuming that your current mesheryctl context is configured for platform: docker (verify using mesheryctl system context view), one thing that you might try doing is deploying Meshery internal to your cluster so as to avoid having to work through virtual network connectivity.
As far as I’ve understood, using the steps I executed, Meshery is deployed in-cluster itself, with the platform being kubernetes. Output of mesheryctl system context view:
Current Context: local
endpoint: http://127.0.0.1:9081
token: default
token-location: auth.json
platform: kubernetes
components: []
channel: stable
version: latest
provider: Meshery
Minikube is just using Docker as the driver, but the Meshery deployment is in-cluster itself. I had found a solution for Docker deployments of Meshery here, but wanted to troubleshoot an in-cluster installation regardless.
Yes, logs from Meshery Server will help (e.g. mesheryctl system logs). It’d also be helpful for you to verify that Meshery Server has access to this cluster’s certificate files (client-certificate and client-key). If Meshery Server can’t follow that file path, then mesheryctl system config minikube will help prep your kubeconfig for Meshery Server to be able to properly authenticate to your cluster.
@Lee How do I verify certificate access for Meshery Server? Because, as mentioned in the original post, mesheryctl system config minikube gives a “no contexts available” error.
Also, how do I attach logs here? I don’t see any option to attach files, and the logs are pretty long to paste here