Before deploying anything you must have a Juju model. It is usually a good idea to create a dedicated model for the COS Lite bundle. So let’s do just that and call the new model cos
:
juju add-model cos
juju switch cos
Next, deploy the bundle with:
juju deploy cos-lite \
--channel=edge \
--trust
Now you can sit back and watch the deployment take place:
juju status \
--relations \
--color \
--watch 2s
The status of your deployment should eventually be very similar to the following:
> juju status --relations
Model Controller Cloud/Region Version SLA Timestamp
cos cos-uk8s microk8s/localhost 2.9.15 unsupported 16:53:38-00:00
App Version Status Scale Charm Store Channel Rev OS Address Message
alertmanager active 1 alertmanager-k8s charmhub edge 6 kubernetes 10.152.183.175
grafana active 1 grafana-k8s charmhub edge 10 kubernetes 10.152.183.156
loki active 1 loki-k8s charmhub edge 6 kubernetes 10.152.183.6
prometheus active 1 prometheus-k8s charmhub edge 10 kubernetes 10.152.183.227
Unit Workload Agent Address Ports Message
alertmanager/0* active idle 10.1.24.70
grafana/0* active idle 10.1.24.71
loki/0* active idle 10.1.24.82
prometheus/0* active idle 10.1.24.73
Relation provider Requirer Interface Type Message
alertmanager:alerting prometheus:alertmanager alertmanager_dispatch regular
alertmanager:replicas alertmanager:replicas alertmanager_replica peer
grafana:grafana-peers grafana:grafana-peers grafana_peers peer
loki:grafana-source grafana:grafana-source grafana_datasource regular
prometheus:grafana-source grafana:grafana-source grafana_datasource regular
Now COS Lite is good to go: you can relate software with it to begin the monitoring!
Alternatively, you may want to deploy the bundle with one or more of our readily available overlays, which is what we’ll cover next.