COS configuration
Platform:
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| 2/stable | 79 | 12 Nov 2025 | |
| 2/candidate | 108 | 18 Jun 2026 | |
| 2/beta | 108 | 18 Jun 2026 | |
| 2/edge | 108 | 17 Jun 2026 | |
| dev/edge | 110 | 23 Jun 2026 | |
| dev/edge | 103 | 10 Jun 2026 | |
| 1/stable | 71 | 08 Jul 2025 | |
| 1/candidate | 71 | 26 Jun 2025 | |
| 1/beta | 71 | 10 Jun 2025 | |
| 1/edge | 71 | 14 May 2025 |
juju deploy cos-configuration-k8s --channel dev/edgePush user (3rd-party) rules to COS charms.
COS Configuration K8s is a Juju charm that syncs observability configurations — such as Prometheus alert rules, Loki alert rules, Grafana dashboards, and SLO specifications — from a Git repository and forwards them to the corresponding COS charms. It is a complementary charm to the Canonical Observability Stack (COS): https://documentation.ubuntu.com/observability
This charm enables an infrastructure-as-code workflow for observability, allowing operators to manage alert rules and dashboards in version control and have them automatically applied to the running stack.
Key features:
- Automatic synchronization of configurations from a Git repository using git-sync.
- Forwarding of Prometheus alert and recording rules, Loki alert rules, Grafana dashboards, and SLO specifications to their respective COS charms via Juju relations.
- Support for private repositories via SSH keys, including Juju secrets integration for secure key storage.
- Configurable paths within the repository for each type of configuration.
- Configurable branch, revision, and clone depth for fine-grained control over the sync.
- On-demand sync via the sync-now action, in addition to periodic automatic updates.