COS configuration
Platform:
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| 2/stable | 79 | 12 Nov 2025 | |
| 2/candidate | 85 | 31 Mar 2026 | |
| 2/beta | 85 | 31 Mar 2026 | |
| 2/edge | 85 | 30 Jan 2026 | |
| dev/edge | 97 | 29 Apr 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/edge
-
git_branch | string
Default: master
The git branch to check out.
-
git_depth | int
Default: 1
Cloning depth, to truncate commit history to the specified number of commits. Zero means no truncating.
-
git_repo | string
URL to repo to clone and sync against.
-
git_rev | string
Default: HEAD
The git revision (tag or hash) to check out
-
git_ssh_key | string
An optional SSH private key to use when cloning the repository. WARNING: This will expose your private key as cleartext in the Juju config. Use the "git_ssh_key_secret" config option instead.
-
git_ssh_key_secret | string
An optional SSH private key to use when cloning the repository. This option takes priority over "git_ssh_key" if both are set. The value must be a Juju secret ID, which references a Juju secret, containing the private SSH key. The format for the input is:
- secret://<secret-id>/<key>
This requires the admin to create a Juju secret. The secret must:
- exist in the same model as the cos-configuration charm
- have a key named <key> with the value of the private SSH key
Make sure to "grant-secret" this secret to the cos-configuration charm.
-
grafana_dashboards_path | string
Default: grafana_dashboards
Relative path in repo to grafana dashboards.
-
known_hosts_config | string
Default: github.com ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQCj7ndNxQowgcQnjshcLrqPEiiphnt+VTTvDP6mHBL9j1aNUkY4Ue1gvwnGLVlOhGeYrnZaMgRK6+PKCUXaDbC7qtbW8gIkhL7aGCsOr/C56SJMy/BCZfxd1nWzAOxSDPgVsmerOBYfNqltV9/hWCqBywINIR+5dIg6JTJ72pcEpEjcYgXkE2YEFXV1JHnsKgbLWNlhScqb2UmyRkQyytRLtL+38TGxkxCflmO+5Z8CSSNY7GidjMIZ7Q4zMjA2n1nGrlTDkzwDCsw+wqFPGQA179cnfGWOWRVruj16z6XyvxvjJwbz0wQZ75XK5tKSb7FNyeIEs4TT4jk+S4dhPeAUC5y+bDYirYgM4GC7uEnztnZyaVWQ7B381AK4Qdrwt51ZqExKbQpTUNn+EjqoTwvqNj4kqx5QUCI0ThS/YkOxJCXmPUWZbhjpCg56i+2aB6CmK2JGhn57K5mj0MNdBXA4/WnwH6XoPWJzK5Nyu2zB3nAZp+S5hpQs+p1vN1/wsjk= github.com ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBEmKSENjQEezOmxkZMy7opKgwFB9nkt5YRrYMjNuG5N87uRgg6CLrbo5wAdT/y6v0mKV0U2w0WZ2YB/++Tpockg= github.com ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIOMqqnkVzrm0SdG6UOoqKLsabgH5C9okWi0dh2l9GKJl git.launchpad.net ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDEFREwBD2ye2Xrc2SVcUmmJ44MF1BCB3W11NTaiqzVj7XZnQmgWZk9UadHVY2wBXvelcDO51MPN5ozJjFAknw09rP7XMRJMlAOLSIVoU6DRF1u1j8kJVY+dfiDHheS7+siADnrmb8HGn2xQQ6EJDjAXrw1x58x5eZjQ0PFWdI+pRTdYGvWkpHdXKFO6a9/lDx4uo9MCnePEGi/QnkCmKqLCBUlYNZYRiB8nVee2tMF0mjV8xk1rJ+/UP+897+FXFR9w/B1EPRjiQ35ZNQZKPP4isxPtyMuCQkZY7ckWr5YsylNfvNcyGDnO1XazZhJ71rzDpi1RmnFXBW5i+2dm2y7
Contents for the SSH known_hosts file used when cloning via SSH. Each line should follow the standard known_hosts format (e.g. "hostname algorithm base64-key"). The remote extracted from git_repo must appear in this value, otherwise the charm will block. The default includes public host keys for github.com and git.launchpad.net. To add another host (e.g. gitlab.com), run "ssh-keyscan gitlab.com" and append the output lines to this value.
-
loki_alert_rules_path | string
Default: loki_alert_rules
Relative path in repo to loki rules.
-
prometheus_alert_rules_path | string
Default: prometheus_alert_rules
Relative path in repo to prometheus rules.
-
slos_path | string
Default: slos
Relative path in repo to SLO (Service Level Objective) files for sloth.