Modify Meshery Operator's behaviour to provide intelligent networking abstractions

[humblenginr]

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

[welcome]

Thanks for opening this issue. A contributor will be by to give feedback soon. In the meantime, please review the Layer5 Contributors' Welcome Guide, engage in the discussion forum, and be sure to join the community Slack.

[github-actions]

This issue has been labeled with 'design-required'. Note that prior to commencing on implementation, a design specification needs to be created and reviewed for approval. See Creating a Functional Specification to create a design spec.

---

        Be sure to join the community, if you haven't yet and please leave a ⭐ star on the project 😄

[leecalcote]

@sudo-NithishKarthik related issue: #333

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue is being automatically closed due to inactivity. However, you may choose to reopen this issue.

[stale]

This issue is being automatically closed due to inactivity. However, you may choose to reopen this issue.