Once you have deployed Kubeflow, it is time to access the Kubeflow dashboard.
To display your access credentials, run the following commands:
juju config dex-auth static-username juju config dex-auth static-password
Empty values here indicate that static username/password authentication is disabled. If you wish to set these values, add the relevant string to the end of the command, e.g.
juju config dex-auth static-username=admin juju config dex-auth static-password=AxWiJjk2hu4fFga7
To find the IP address of the Kubeflow dashboard for your deployment run:
kubectl get services -n kubeflow
kubeflow is the name you gave to your Juju model, and hence the namespace of your Kubeflow deployment.
For local Kubeflow deployments, such as in a workstation, you can simply access the link found in the previous step, appending
nip.io, for example:
However, for remote deployments, or running on a virtual machine, creating a SOCKS proxy is required to access the dashboard. This can be done as follows:
Logout from the current session with the
Re-establish connection to the machine using
sshwith SOCKS proxy enabled through the
-D 9999parameter. As in the example below:
ssh -D 9999 ubuntu@<machine_public_ip>
On your computer, go to
Settings > Network > Network Proxy, and enable SOCKS proxy pointing to:
On a new browser window, access the link given in the previous step, appended by
.nip.io, for example: