Component
core/storage/velero
Velero, the cluster backup controller, installed once per cluster in the namespace velero. On the schedules written for it, it copies Kubernetes resources, and the data of the volumes their pods mount, into a bucket reached over the S3 API, and restores them from there. It backs nothing up by itself. A datastore is backed up by attaching core/backup to it in the Release, with the Manifest binding the helm/backup-velero FeatureRecipe, which writes the schedule and its storage location into the velero namespace; they run only where this component is deployed. The Release declares the namespace velero for it. Velero signs its requests to the bucket with the key pair in the credentials file the cloud_credentials slot names; with the slot empty it uses whatever identity its pods' environment offers, such as the role of the node they run on. Realized on Kubernetes by helm/velero-chart, the project's own chart, whose chart repository must be reachable from the build.
Provenance
- Content digest
- sha256:7af2fc16987f757bdcad6c883a62c4f66bb22eae7e8be86a65ab3e29d682b1f4
- Published
- 2026-11-10T10:14:10Z
- Signing identity
- https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
Signature
- Officialapplication/vnd.dev.sigstore.bundle.v0.3+json
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
sha256:65bf733c792abe63156be485b1c06cafd220008651e08f746a499751f5686a4e
Reference at this version
oci://hub.aggrega.ai/component/core/storage/velero:1.0.0Developer parameters
Values the developer sets in the Aggregate.
No developer parameters declared.
Operator sizing
Infrastructure sizing the operator tunes per environment.
| Name | Type | Default | Required | Description |
|---|---|---|---|---|
| source_version | string | — | no | Version of the Velero chart the `velero-chart` realization pulls. Its default is the release whose application version is the tag of the image default below; changing it away from that default does not guarantee value-mapping compatibility with the new chart, and the image follows it only where it is set too. |
| image | string | velero/velero:v1.18.2 | no | Velero image the server Deployment and the node-agent DaemonSet run. Pinned to the release the chart's application version names; a Release pulling from its own registry mirror sets this to that reference instead. |
| aws_plugin_image | string | velero/velero-plugin-for-aws:v1.14.4 | no | Image of Velero's plugin for the S3 API, which the server loads at start to read and write its backup buckets. Its v1.14 releases pair with Velero v1.18. |
Output contract
Values this component publishes to consumers over the uses topology.
No output values declared.
Uses sockets
The dependency sockets this component connects through. The target of every connection wired through a socket must satisfy its label selector, and each connection may carry an attachment in the slots the socket declares. A required slot is owed by each connection the Aggregate or the Release wires through the socket.
No uses sockets declared.
Attachment slots
Named binding points at which a Feature attaches to this component. A slot's selector constrains which Feature may fill it and its inject list names how the Feature's material may be delivered. A required slot must be bound on every instance, by an attachment on the instance or at a scope above it, and a sensitive slot is declared to handle secret material. A Feature may also attach under a name no slot declares.
| Slot | Selector | Required | Inject | Sensitive | Description |
|---|---|---|---|---|---|
| cloud_credentials | feature.aggrega.ai/kind=secret | no | file | yes | The credentials file Velero signs its requests to every backup bucket with: an AWS shared credentials file, a [default] section carrying aws_access_key_id and aws_secret_access_key, held in a Secret in the velero namespace under the key the attached credential names. Velero's server and its node agent read it. Empty, Velero uses whatever identity its pods' environment offers. |
Self-inject allowlist
No self-inject pipes declared.
Relationships
Typed edges to and from other published entities. A reference with no published target renders as a broken edge rather than a link.
Uses
This entity uses nothing in the catalog.
Used by
uses socket «upstream»
uses socket «forward_target»
uses socket «scrape_target»
uses socket «store»
applies to
applies to
applies to
applies to
applies to
applies to
applies to
implements