Vault
- Canonical Telco
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| latest/edge | 89 | 31 Jan 2024 | |
| latest/edge | 9 | 27 Jan 2023 | |
| 1.16/stable | 323 | 20 Jan 2025 | |
| 1.16/candidate | 323 | 20 Jan 2025 | |
| 1.16/beta | 323 | 20 Jan 2025 | |
| 1.16/edge | 328 | Yesterday | |
| 1.15/stable | 248 | 24 Jul 2024 | |
| 1.15/candidate | 248 | 24 Jul 2024 | |
| 1.15/beta | 248 | 24 Jul 2024 | |
| 1.15/edge | 248 | 10 Jul 2024 |
juju deploy vault-k8s --channel 1.15/beta
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:
Production blueprint
This document outlines recommendations for operating Vault in a production environment.
Infrastructure
Please follow the Vault project reference to deploy the Vault charms on hosts of appropriate size for your deployment.
High Availability
Vault should be deployed with a total of 5 units.
Observability
Vault should be integrated with Canonical Observability Stack:
- Vault should be integrated with Grafana Agent using the
cos-agentcharm relation interface. - Grafana Agent should be integrated with COS using the
loki_push_api,prometheus_remote_write, andgrafana_dashboardcharm relation interfaces.
Backup and Restore
Vault should be integrated with an S3 provider to conduct regular backup operations.