stakater/application v9.0.0

on GitHub

This release contains breaking changes that modernize the Velero Backup template with new fields and stricter rendering behavior.

Breaking Changes

1. defaultVolumesToRestic deprecated (#436)

defaultVolumesToRestic is now deprecated in favor of defaultVolumesToFsBackup. The old key still works but will be removed in a future release. Migrate your values:

backup:
  # defaultVolumesToRestic: true  # deprecated
  defaultVolumesToFsBackup: true   # use this instead

2. Backup requires Velero API to be available (#436)

The Backup resource is no longer rendered silently when Velero is not installed. If the velero.io/v1 API group is not available in the cluster, the template will fail with an explicit error message instead of rendering a resource that cannot be applied.

3. Optional fields no longer rendered when unset (#436)

snapshotVolumes, storageLocation, and ttl were previously always included in the Backup manifest regardless of whether they were set. They are now conditionally rendered and will be absent from the output when not explicitly configured.

If you rely on these fields being present (e.g., for GitOps diff stability), set them explicitly:

backup:
  snapshotVolumes: true
  storageLocation: default
  ttl: 720h0m0s

4. labelSelector.matchLabels uses selectorLabels (#436)

The Backup labelSelector.matchLabels now uses the standard selectorLabels helper instead of a hardcoded part-of label. If you rely on the previous label selector behavior, verify your backup selection still matches the expected workloads.

Notable Additions

New Velero backup fields are now supported:

• defaultVolumesToFsBackup
• snapshotMoveData
• csiSnapshotTimeout
• datamover
• itemOperationTimeout
• volumeSnapshotLocations
• includedNamespaceScopedResources
• excludedNamespaceScopedResources
• orderedResources

What's Changed

• feat(backup)!: add support for new velero fields by @Copilot in #436

Full Changelog: v8.2.0...v9.0.0