How to manage the Juju dashboard
See also: The Juju dashboard, Charmhub |
juju-dashboard
This document demonstrates how to use the Juju dashboard.
Starting with juju v.3.0
, the Juju dashboard needs to be set up via the juju-dashboard
charm. (Previously it came automatically with every controller.)
See more: Charmhub |
juju-dashboard
Contents:
Set up the dashboard
First, switch to the controller model (always called controller
; see juju status
):
juju switch controller
Then, deploy the juju-dashboard
charm:
juju deploy juju-dashboard
Next, integrate it with the controller application (always called controller
; see juju status
):
juju integrate juju-dashboard controller
Now, expose the juju-dashboard
application:
juju expose juju-dashboard
Your application is now ready to be accessed.
Access the dashboard
See also:
juju dashboard
First, use the dashboard
command to get the IP address and login credentials to access the dashboard:
juju dashboard
This will produce output similar to the following:
Dashboard for controller "my-controller is enabled at:
https://10.55.60.10:17070/dashboard
Your login credential is:
username: admin
password: 1d191f0ef257a3fc3af6be0814f6f1b0
Now copy-paste the URL into the browser to access the dashboard.
If you don’t want to copy and paste the URL manually, typing juju dashboard --browser
will open the link in your default browser automatically.
Your browser will give you an error message when you open the URL warning that the site certificate should not be trusted. This is because Juju is generating a self-signed SSL certificate rather than one from a certificate authority (CA). Depending on your browser, choose to manually proceed or add an exception to continue past the browser’s error page.
After opening the Juju dashboard URL, you are greeted with the login window, where you will have to provide the credentials to access the model. These credentials can be copied from the output of juju dashboard
.
If you’d rather not have your login credentials displayed in the output of juju dashboard
, they can be suppressed by adding the --hide-credential
argument.
Last updated 2 months ago.