Modify Meshery Operator's behaviour to provide intelligent networking abstractions

Current Behavior

Users of Meshery bump into some networking issues with meshery-broker(the pub-sub communication platform for meshery). One such example is Minikube which does not have a default load-balancer implementation.

Desired Behavior

1. Make Meshery Operator self-discovering and self-reporting its static configuration to Meshery Server.
2. Make Meshery Operator / Meshery Server intelligent enough to change networking based on what it thinks networking should be, but always allow for manual user override.

Contributor Guides and Resources

• 🛠 Meshery Build & Release Strategy
• 📚 Instructions for contributing to documentation
  • Meshery documentation site and source
• 🎨 Wireframes and designs for Meshery UI in Figma
• 🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

Start by reproducing the meshery-broker networking issue on Minikube and tracing how the Meshery Operator and Meshery Server currently exchange static configuration. Define the discovery and reporting scope, networking decisions, and manual override behavior before implementation. Done means Minikube networking works through an explicit, tested abstraction without removing user control.