veleroFsfreezeImage setting in helm chart

[asokolsky4clari]

Describe the problem/challenge you have

velero injects the following sidecar container into my vault pod:

• name: "velero-fsfreeze"
• Image: "ubuntu:bionic"

Because docker imposed anonymous pull rate restrictions and I would like to be able to customize the image, e.g. set it to 'public.ecr.aws/docker/library/ubuntu:bionic'.

I am aware of the veleroFsfreezeImage API.

Describe the solution you'd like

Ideally a helm chart value veleroFsfreezeImage which defaults to ubuntu:bionic with possibility to customize it.

Anything else you would like to add:

Environment:

• Velero version (use velero version): velero:v1.13.0, velero-plugin-for-aws:v1.9.0
• Kubernetes version (use kubectl version): Client Version: v1.28.2, Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3, Server Version: v1.27.13-eks-3af4770
• Kubernetes installer & version: n/a
• Cloud provider or hardware configuration: AWS
• OS (e.g. from /etc/os-release): Ubuntu 18.04.6 LTS (Bionic Beaver)

Vote on this issue!

This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.

• :+1: for "The project would be better with this feature added"
• :-1: for "This feature will not enhance the project in a meaningful way"

[blackpiglet]

I didn't find the ubuntu and the fsfreeze-related information in the Velero helm chart repository for tag velero-5.4.1. @jenting Could you please give some insight?

[asokolsky4clari]

My problem seems to be caused by bank-vaults. Closing the issue.