Issue loading clusters when running Meshery via in-cluster setup on Minikube

Meshery
3

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.

Further, output of kubectl config view:

apiVersion: v1
clusters:
- cluster:
    certificate-authority: C:\Users\USERNAME\.minikube\ca.crt
    extensions:
    - extension:
        last-update: Tue, 03 Jun 2025 17:51:33 IST
        provider: minikube.sigs.k8s.io
        version: v1.35.0
      name: cluster_info
    server: https://127.0.0.1:53961
  name: minikube
contexts:
- context:
    cluster: minikube
    extensions:
    - extension:
        last-update: Tue, 03 Jun 2025 17:51:33 IST
        provider: minikube.sigs.k8s.io
        version: v1.35.0
      name: context_info
    namespace: default
    user: minikube
  name: minikube
current-context: minikube
kind: Config
preferences: {}
users:
- name: minikube
  user:
    client-certificate: C:\Users\USERNAME\.minikube\profiles\minikube\client.crt
    client-key: C:\Users\USERNAME\.minikube\profiles\minikube\client.key

Would you suggest simply using an out-of-cluster deployment on Docker instead, and applying the virtual network connectivity steps?