default velero deployment failing due to field not declared in schema

Bug

Description

Deploying Big Bang 3.19.0 with the velero (velero-11.3.2-bb.2) add-on enabled like so:

addons:
  velero:
    enabled: true

results in error:

velero   14m   False   Helm install failed for release velero/velero-velero with chart velero@11.3.2-bb.2: failed to create typed patch object (velero/velero; apps/v1, Kind=Deployment): .spec.template.spec.containers[name="velero"].resources.upgradeJob: field not declared in schema...

Provide any steps possible used to reproduce the error (ideally in an isolated fashion).

Env: AWS/EKS. Enable velero with defaults

BigBang Version

What version of BigBang were you running?

3.19.0