
Juju Dashboard k8s
Channel | Revision | Published | Runs on |
---|---|---|---|
latest/stable | 16 | 28 Mar 2025 | |
latest/edge | 15 | 27 Mar 2025 | |
0.15/beta | 51 | 14 Aug 2025 | |
0.14/beta | 52 | 22 Aug 2025 |
juju deploy juju-dashboard-k8s
Deploy Kubernetes operators easily with Juju, the Universal Operator Lifecycle Manager. Need a Kubernetes cluster? Install MicroK8s to create a full CNCF-certified Kubernetes system in under 60 seconds.
Platform:
Juju Dashboard for Kubernetes
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-k8s 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 Microk8s environment.
To deploy Juju Dashboard with a TLS certificate we’ll make use of the Kubernetes ingress API. First of all you’ll need to enable the ingress addon:
sudo microk8s enable ingress
In this scenario the dashboard will need to be deployed in a model that is not the controller model (See this issue). However the dashboard requires a relation to the controller, so we need to offer the controller interface so we can make a cross model integration.
juju switch controller
juju offer controller:dashboard
Now create a model for the dashboard:
juju add-model juju-dashboard
Inside that model deploy nginx-ingress-integrator. This application will provide a bridge between the Kubernetes ingress and Juju Dashboard as well as terminate the TLS certificate.
juju deploy nginx-ingress-integrator dashboard-ingress --config service-hostname="dashboard.localhost" service-port=80
juju trust dashboard-ingress --scope cluster
Now deploy the self signed certificates charm and integrate it with the ingress app:
juju deploy self-signed-certificates --channel 1/stable dashboard-cert
juju integrate dashboard-ingress:certificates dashboard-cert:certificates
Deploy the dashboard:
juju deploy juju-dashboard-k8s dashboard
Next, get the name of the controller offer and integrate with the dashboard:
juju find-offers # The offer will be something like "admin/controller.controller"
juju integrate admin/controller.controller dashboard
Integrate the dashboard with the ingress app:
juju integrate dashboard dashboard-ingress
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.
-
Issues with the Dashboard VM or K8s charm.
-
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.