Documentation/Services
Services · v0.0.1

Velero add-on

Kubernetes resource and volume backup workflows. Catalog version: v1.15.0.

AudienceCluster service operatorsReading time9 minutesCommands in contextNo terminal requiredReviewed sourcefcc5871 · 30 July 2026
RC

Exact release scope. This page documents the reviewed v0.0.1 source at fcc5871. Check release status before enabling a gated capability.

Catalog contract

FieldValue
Keyvelero
Versionv1.15.0
CategoryBackup
v0.0.1 postureInstall preview · gated
Upgrade / uninstallContract stubs; no OperationRun

Kubernetes resource and volume backup workflows.

Before planning

  • Cluster state is ReadyForAddons and no conflicting lifecycle operation is active
  • The add-on artifact and every required image have immutable approved identities
  • Dependency: object-storage
  • No catalog-level conflict
  • Required SecretRefs exist and values are never copied into plan input

Operator values

The catalog exposes a validated values schema. Unknown or secret-shaped plain values should fail before install.

ValueUse
cloudCredentialsSecretRefReference existing secret material; never provide a plaintext value
objectStorageModeReview and set only when required by the selected profile
objectStorageProfileIdReview and set only when required by the selected profile
valuesRefReview and set only when required by the selected profile
healthGatePolicyReview and set only when required by the selected profile

Plan, preflight and install

  1. 01

    Select the catalog entry

    Confirm key, version, source identity, dependencies, conflicts and dashboard capability.

  2. 02

    Create an AddonPlan

    Review ordered issues, namespace, values profile, artifacts and images.

  3. 03

    Run preflight

    Require cluster readiness, dependency, registry reachability, artifact lock and image lock evidence.

  4. 04

    Install through the OperationRun

    Use the compatible lifecycle agent and follow each Helm/apply and health step.

  5. 05

    Accept semantic health

    Do not stop at running pods; use the catalog health checks and retained evidence.

Dashboard and access

No curated dashboard.

Failure and recovery

FailureSafe response
Preflight blockedFix dependency, lock, registry, secret reference or cluster readiness; create no install run
Install step failedUse the OperationRun error and evidence; retry only a classified retryable step
Health gate failedKeep dependants and dashboard access blocked; inspect semantic checks
Reapply requiredUse the saved plan and targeted install/reapply path with a new approved intent
Removal requiredv0.0.1 uninstall is not implemented; use an environment-approved manual runbook outside the claimed product capability