Add interface for downloading kubeconfig file

[hatched]

It would be nice if there was a link in the GUI somewhere obvious where the user could click to download the kubeconfig file if the model has kubernetes running in it as well as a link to the dashboard. and if it's openstack, a link to horizon - @sfabel

[hatched]

This is something that could be done via the JAAS terminal. We could auto open the terminal and perform the necessary commands to outline to the user the actions that are being taken on their behalf to get the config file. Or we could do it transparently in the background and just present them with the file once it's ready to download.

This might be a nice thing to add to the get started section that is available once deploying the k8s bundles.

[sfabel]

If there's kubectl within the JAAS terminal, we should point that out to the user also, otherwise, they won't find this on their own.

[cassiocassio]

Get started.md is an ok halfway house

Agree - Handy arbitrary scripts that charm or bundle can bring, to trigger a terminal, is a feature we want anyway.

But what's missing is a mechanism for charms to declare and describe their endpoints in a usable way. It's probably a juju level feature.

Could there be a generic mechanism in juju to document essential endpoints and their uses that could be sanely surfaced in both GUI and CLI?

endpoint:port/filepath [file icon] "Get kubectl"

endpoint:port [terminal icon] "Open REPL"

endpoint:8080/dashboard.html [webicon] "Stats dashboard"

We already know endpoints, and show them when exposed, but not the full paths to things.

We need to be able to show the full filepath, know how the item can or should be opened, eg. terminal or web or download.

In addition, we need a human-readable description of what the user gets from this.

Hacking something directly for kubernetes would be nice, but a general solution would give the right handles, with context, for both GUI and CLI.