meshery / meshery-operator

Meshery Operator is a Kubernetes Operator that deploys and manages the lifecycle of two Meshery components critical to Meshery's operations of Kubernetes clusters
https://meshery.io
Apache License 2.0
111 stars 79 forks source link

Modify Meshery Operator's behaviour to provide intelligent networking abstractions #331

Open humblenginr opened 2 years ago

humblenginr commented 2 years ago

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

welcome[bot] commented 2 years ago

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[bot] commented 2 years ago

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: star on the project :smile:

leecalcote commented 2 years ago

@sudo-NithishKarthik related issue: https://github.com/meshery/meshery-operator/issues/333

stale[bot] commented 2 years ago

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[bot] commented 2 years ago

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

stale[bot] commented 2 years ago

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

github-actions[bot] commented 2 years ago

Checking in... it has been awhile since we've heard from you on this issue. Are you still working on it? Please let us know and please don't hesitate to contact a MeshMate or any other community member for assistance.


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

stale[bot] commented 1 year ago

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[bot] commented 1 year ago

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.