This is great. “Meshery Broker” is the name of the component. Will you update the post title to use this name? Also, it is how to expose “as” a load balancer, not “and” given that there is only one entity that is being dealt with here.
There are a couple of ways through which I debug such problems:
Check if you see logs like:
INFO[2022-09-11T18:33:30+05:30] Updated object: kube-root-ca.crt/dashboard-docker-3 of kind: ConfigMap in the database app=meshery
INFO[2022-09-11T18:33:30+05:30] Updated object: operator-cbaa153a-bb7b-4cd7-8187-2b561927eccb.meshery.layer5.io/meshery of kind: ConfigMap in the database app=meshery
This proves that MeshSync precisely discovered resources in your cluster and were successfully saved in your local Meshery DB
Watch your local Meshery DB
Meshery uses SQLite DB to store the K8s resources. In order to visualize this, you may use any VS Code extension that helps in opening up local DB. Configure it and then point it to ~/.meshery/config/mesherydb.sql (SQL file for the Meshery DB).
Check logs of your MeshSync pod in case that is having some issues in reconciling by Meshery Operator. In this case, you can try deleting the MeshSync pod.
Use
k delete po meshery-meshsync-XXXXXXXX-XXXXX -n meshery
Try hard resetting your Meshery DB. You can do it by going to the settings page on Meshery UI