Velero CRD upgrade job failure when upgrading to 8.2.0

[mymasse]

What steps did you take and what happened:

The upgrade CRD job fails when upgrading the chart.

error validating "STDIN": error validating data: the server is currently unable to handle the request; if you choose to ignore these errors, turn validation off with --validate=false

What did you expect to happen:

Expected the job to succeeds and continue the upgrade of the chart.

The output of the following commands will help us better understand what's going on:

Running from my machine the following commands results in the same error (this is after the rollback, hence why 1.15.0):

❯ velero version
Client:
	Version: v1.15.0
	Git commit: 1d4f1475975b5107ec35f4d19ff17f7d1fcb3edf
Server:
	Version: v1.15.0
❯ kubectl version
Client Version: v1.30.8
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.30.7-eks-56e63d8
❯ velero install --crds-only --dry-run -o yaml | kubectl apply -f -
error: error validating "STDIN": error validating data: the server is currently unable to handle the request; if you choose to ignore these errors, turn validation off with --validate=false

Anything else you would like to add:

This worked with Chart version 8.1.0 and started failing with 8.2.0. Rolling back to 8.1.0 now also fails with the same error messages. EKS minor version unchanged between initial deployment of 8.1.0 and 8.2.0.

Chart is deployed with the default kubectl values:

kubectl:
  image:
    repository: docker.io/bitnami/kubectl    
  containerSecurityContext: {}
  resources: {}
  annotations: {}
  labels: {}

Environment:

• helm version (use helm version): N/A
• terraform-helm-provider: 2.17.0
• helm chart version and app version (use helm list -n <YOUR NAMESPACE>): 8.2.0
• Kubernetes version (use kubectl version):
• Kubernetes installer & version: EKS v1.30.7-eks-56e63d8
• Cloud provider or hardware configuration: AWS EKS
• OS (e.g. from /etc/os-release): Amazon Linux 2

[mymasse]

So it looks like this was a problem with the EKS version, we upgraded our clusters to 1.31.4 and have re-enabled the upgrade crds job and it is now working.