Files
cozystack/packages/system/velero/values.yaml
T
Yasar Rahman 83aaa65ed1 fix(velero): bump velero-plugin-for-aws to v1.14.4 so backups work on R2
velero-plugin-for-aws v1.14.1 sets x-amz-tagging on every PutObject,
empty when the BackupStorageLocation configures no tags. Cloudflare R2
answers that with 501 NotImplemented ("Header 'x-amz-tagging' with value
'' not implemented"), so Velero cannot write backup metadata and every
backup to an R2 location fails, the cozy-default location included when
the platform bucket is on R2.

The plugin sends the header only when tags are configured since v1.14.3
(velero-plugin-for-aws#309, a backport of #299). v1.14.4 is the current
patch release of the 1.14 line, which upstream lists as the one
compatible with Velero 1.18, and adds only CVE dependency bumps on top
of v1.14.3.

Signed-off-by: Yasar Rahman <yasar.rehman@gmail.com>
Assisted-by: LLM
2026-10-10 01:18:13 +05:00

73 lines
3.2 KiB
YAML

velero:
# Disable the upgrade-crds Job: CRD lifecycle is owned by the generated
# HelmRelease instead (upgradeCRDs: CreateReplace on the velero PackageSource),
# which applies the chart's crds/ directory on install and on every upgrade,
# so the Job is redundant.
upgradeCRDs: false
initContainers:
- name: velero-plugin-for-aws
image: velero/velero-plugin-for-aws:v1.14.4
imagePullPolicy: IfNotPresent
volumeMounts:
- mountPath: /target
name: plugins
- image: quay.io/kubevirt/kubevirt-velero-plugin:v0.9.0
name: kubevirt-kubevirt-velero-plugin
imagePullPolicy: IfNotPresent
volumeMounts:
- mountPath: /target
name: plugins
deployNodeAgent: true
nodeAgent:
# node-agent is a DaemonSet and ran BestEffort. A memory limit is what sets
# memory.max on the pod cgroup, and the Talos userspace OOM handler (v1.12+)
# only ever kills cgroups that lack one — so it was an eviction candidate on
# every node, independent of what caused the pressure. Killing it mid-backup
# fails the backup, so the limit is deliberately loose: 14d peak is 121Mi at
# idle on a dev cluster, but the agent streams volume data during a backup
# and that is exactly when it must not be killed.
resources:
requests:
cpu: 50m
memory: 128Mi
limits:
memory: 2Gi
configuration:
# defaultVolumesToFsBackup: true
# cozy-default BackupStorageLocation lives in the
# backupstrategy-controller chart (single source of truth for
# backupStorage.{endpoint,bucketName,region}); see
# packages/system/backupstrategy-controller/templates/velero-bsl.yaml.
backupStorageLocation: null
volumeSnapshotLocation: null
namespace: cozy-velero
features: EnableCSI
# Increase timeout for item operations to 24 hours to prevent timeouts
# during backups of very large volumes. The Velero default is 4 hours.
defaultItemOperationTimeout: 24h
# Velero binds its metrics/health endpoint (:8085, http-monitoring) only after
# the server finishes loading plugins and connecting to the API server. Under a
# heavy parallel platform install that can take minutes, but the upstream
# liveness probe starts checking /metrics at initialDelaySeconds=10 and kills
# the container after failureThreshold=5 (~130s total) before :8085 is bound.
# The kubelet SIGTERMs velero (exitCode 0/Completed), it BackOff-restarts, and
# never escapes the loop inside the install-gate window, blocking the gate.
#
# Give the server an explicit startup budget. While the startupProbe is failing
# the kubelet holds off the liveness and readiness probes entirely, so steady-
# state liveness stays at the tight upstream default (10s / 30s / 5 failures)
# once startup completes. failureThreshold * periodSeconds = 30 * 10s = 300s of
# grace. The upstream chart does not render a startupProbe, so the velero
# package patches it in (patches/add-startup-probe.patch, re-applied on update).
startupProbe:
httpGet:
path: /metrics
port: http-monitoring
scheme: HTTP
periodSeconds: 10
timeoutSeconds: 5
successThreshold: 1
failureThreshold: 30