Juju Dashboard
Juju Dashboard displays your controllers and models, allowing you to see the status of your deployments, manage access, run actions and configure applications. The dashboard can be used with your local Juju environments and can also be found as a part of JAAS.
Deploy
Juju Dashboard can be deployed in your controller model using either the VM charm or Kubernetes charm (pre Juju 3.0 controllers included Juju Dashboard automatically).
To deploy the dashboard, first switch to the controller model:
juju switch controller
Next deploy the charm:
juju deploy juju-dashboard dashboard
Then integrate the controller and the dashboard:
juju integrate dashboard controller
Now you can access the dashboard by running:
juju dashboard
This command will open a connection to the dashboard output the dashboard address and credentials.
For further details see the docs on managing the dashboard.
Deploy with TLS
This guide will show the process for deploying Juju Dashboard with a TLS certificate. For demonstration purposes we’ll use self signed certificates. For more information on using certificates in Juju see the docs.
To follow this guide you’ll need a Juju controller bootstrapped in a machine (non-Kubernetes) environment.
This guide will make use of the haproxy charm to terminate the TLS certificate and route traffic to Juju Dashboard. Begin by switching to the controller model and deploy haproxy.
juju switch controller
juju deploy haproxy --channel=2.8/edge --config external-hostname="dashboard.local"
Now deploy the self signed certificates charm and integrate it with haproxy:
juju deploy self-signed-certificates --channel 1/stable dashboard-cert
juju integrate haproxy self-signed-certificates
Deploy the dashboard and integrate with the controller and haproxy:
juju deploy juju-dashboard dashboard
juju integrate dashboard controller
juju integrate haproxy:haproxy-route dashboard:haproxy-route
So that haproxy can route traffic correctly we need to access the dashboard using the hostname we set when deploying haproxy. To do this, point dashboard.local to the haproxy unit’s IP address in your /etc/hosts file.
Get the public address for the haproxy/0 unit:
juju status haproxy
Edit your /etc/hosts and add a new entry:
nano /etc/hosts
# Enter:
[haproxy/0's public ip address] dashboard.local
Check juju status and wait for everything to be ready, then you should be able to view the dashboard by visiting:
Docs
Learn more about the Juju Dashboard in the Juju docs. If you’re new to Juju you may also like to take a look at the getting started docs.
If you think there’s something that needs documenting or an issue with the current docs let us know either via the community or file an issue.
Community
Whether you need help, have suggestions or want to get in contact for any reason you can join us in the Juju Discourse or find us on Mattermost.
Issues
If you’ve found a bug then please let us know by filing an issue. If you’re not sure if it’s a bug you can discuss the issue with us first.
Juju Dashboard integrates with a number of parts of the Juju ecosystem. Filing bugs for the relevant codebase will help the issue to be seen by the right team:
- Issues with Juju Dashboard or its charms.
- Issues with Juju itself or its APIs.
- Issues with the jaas.ai website.
- Issues with the juju.is website.
Contributing
Juju Dashboard is open source and we welcome contributions. Take a look at the contribution guide guide to find out how to contribute to the project and take a look at the development guide to get set up to work on the dashboard.