[mesheryctl] New subcommand: system dashboard

[leecalcote]

Current Situation

Meshery UI's URL is presented to users on system start, but it not recallable by a subsequent command after initial start.

Proposal for Discussion

Have a mesheryctl system dashboard that invokes this logic:

1. test connection to Meshery UI
   1. if available, open the user's default browser
   2. if not available, and current-context's platform is "kubernetes", then initiate a kube proxy tunnel.
      1. suggest that users run this command with & in order to background the tunnel

Benefits to Users

1. Ability to recall the location of their Meshery UI
2. Ability to bypass what might be challenging K8s networking by providing a tunnel from local machine to K8s deployment of Meshery.

Drawbacks

1. If Meshery UI is ever deployed as a component separate from Meshery Server, this command's behavior will need to be evaluated.
2. Benefit Create appropriate interfaces for different meshes to plugin their implementations #2 is mostly only useful on K8s. <-- is that true?

Prior Art (other examples)

• backyards dashboard - https://banzaicloud.com/docs/backyards/cli/reference/backyards_dashboard/
• linkerd dashboard

[pottekkat]

This could be added to mesheryctl with the recent works by @metonymic-smokey to get the endpoint to which Meshery is deployed and opening it on the browser automatically. So, I guess it should open up the UI even for the Kubernetes platform. If not then port-forward?

[pottekkat]

Okay, I will open up an issue for this

[piyushsingariya]

@navendu-pottekkat Issue hasn't been opened up yet!

[metonymic-smokey]

@navendu-pottekkat I think the endpoint returned for kubernetes by GetServiceEndpoint is still incorrect?
Do you think it would be better to wait till that gets sorted?

[pottekkat]

We are also tunnelling to the k8s cluster right? So the endpoint could be updated?

[pottekkat]

I will open up this issue and we can discuss on the specifics