Velero Operator Charm
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| latest/edge | 421 | 25 Sep 2025 | |
| 1.15/stable | 421 | 16 Oct 2025 | |
| 1.15/candidate | 421 | 16 Oct 2025 | |
| 1.15/edge | 421 | 16 Oct 2025 |
juju deploy velero-operator --channel edge
Deploy universal operators easily with Juju, the Universal Operator Lifecycle Manager.
Platform:
24.04
Backup config integration
This guide describes how to integrate Charmed Velero with client charms.
Requirements
- Charmed Velero deployed and configured.
- The client charm exposes a
velero_backup_configendpoint.
Same-model relation
juju integrate <client-app>:velero-backup-config velero-operator:velero-backups
The client publishes its backup spec over the relation; the operator consumes it.
Cross-model integration
Charmed Velero can serve multiple models using Cross-model integration (CMI).
You can offer the Charmed Velero relation from the model where the charm is deployed:
juju switch velero
juju offer velero-operator:velero-backups velero-backups
This creates an offer name, i.e., an alias, velero-backups. Juju prints a URL like: <controller>/<model>.velero-backups.
The offered relation can be consumed from a client model as follows:
juju switch <client_model>
juju consume <controller>/<velero-model>.velero-backups