Skip to content

Commit b653abd

Browse files
yrahman82myasnikovdaniil
authored andcommitted
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 <[email protected]> Assisted-by: LLM (cherry picked from commit 83aaa65) Signed-off-by: Myasnikov Daniil <[email protected]>
1 parent 13e202a commit b653abd

2 files changed

Lines changed: 2 additions & 2 deletions

File tree

‎packages/system/velero/tests/velero_test.yaml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ tests:
2121
asserts:
2222
- equal:
2323
path: spec.template.spec.initContainers[0].image
24-
value: velero/velero-plugin-for-aws:v1.14.1
24+
value: velero/velero-plugin-for-aws:v1.14.4
2525
- equal:
2626
path: spec.template.spec.initContainers[1].image
2727
value: quay.io/kubevirt/kubevirt-velero-plugin:v0.9.0

‎packages/system/velero/values.yaml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ velero:
66
upgradeCRDs: false
77
initContainers:
88
- name: velero-plugin-for-aws
9-
image: velero/velero-plugin-for-aws:v1.14.1
9+
image: velero/velero-plugin-for-aws:v1.14.4
1010
imagePullPolicy: IfNotPresent
1111
volumeMounts:
1212
- mountPath: /target

0 commit comments

Comments
 (0)