Esta página se tradujo automáticamente. Leer el original en inglés.

FeatureRecipe

backup-velero

Component-scope FeatureRecipe for core/backup on Kubernetes through Velero: writes a Velero Schedule and the BackupStorageLocation it writes to, both in the namespace velero, where core/storage/velero runs. The schedule runs only where that component is deployed; nothing in the build checks it. Each backup holds the attached component's pods, selected by the selectors of the controllers its render emits, in the namespaces they are emitted into; the persistent volume claims and volumes those pods mount; and the data of the pods' volumes, which Velero's node agent copies into the bucket. It runs on infra.schedule, or daily at 03:00 in the time zone of Velero's server where that is unset, and each backup is kept for infra.retention_days days. Point-in-time recovery is off: a restore returns to a backup's moment, and infra.point_in_time_recovery: true halts. The location is the bucket the store connection points at, under a prefix of the schedule's own name, reached at the endpoint and region the store publishes. The build halts, naming the attachment, with no store connection, with a store publishing no S3 API, with a store in the cluster whose namespace is not declared, on a component carrying a second core/backup attachment, on a component whose pods are emitted into no namespace, and on a component whose render emits no workload Velero can select, naming the realization to bind instead. It refuses infra.credentials_secret, infra.role_arn, infra.volume, infra.run_as_user and infra.run_as_group by name: Velero signs with the key core/storage/velero holds, assumes no role an attachment names, keeps backups only in a bucket, and starts no job an attachment writes.

Procedencia

OficialFirmado por una identidad de firma que este catálogo reconoce como editor oficial.
Digest del contenido
sha256:ee09f4d37df4cefd3f970a8baf6b8fe5168b80205105d5b2eb2fd535d43d125d
Publicado
2026-11-10T10:15:14Z
Identidad de firma
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Firma

  • Oficialapplication/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:9fe435159358eee6218c1288f06d353b787d27c14cf054b71ef8f04995aa1253

Referencia en esta versión

oci://hub.aggrega.ai/featurerecipe/helm/backup-velero:1.0.0
Destino
—
Implementa
core/backup:1.0.0

Proporciona

Plantillas de punteros deterministas que esta receta cablea para los consumidores.

No se declararon plantillas provides.

Workload

No se declaró ninguna plantilla de carga de trabajo.

Variables locales

No se declararon variables locales.

Mapeo de valores

No se declaró ningún mapeo de valores.

Relaciones

Aristas tipadas hacia y desde otras entidades publicadas. Una referencia sin un destino publicado se muestra como una arista rota en lugar de como un enlace.

Usa

Usado por

Nada en el catálogo depende de esta entidad.

Referencia del concepto FeatureRecipe →

El catálogo de Aggrega — un índice abierto de componentes, funcionalidades, recetas y los plugins que los renderizan.

Creado con el sistema de diseño compartido de Aggrega.

Privacidad