Job secrets-store-csi-driver-upgrade-crds fails on Oracle Linux 8.9

[girishrau]

What steps did you take and what happened:
I am trying to deploy the secrets-csi-driver helm chart on a cluster running v1.30.1. The helm chart fails to deploy as the pre-install hook Job secrets-store-csi-driver-upgrade-crds fails to execute. The job pod logs seem to indicate a kubectl error. It seems like an architecture mismatch on the packaged binary.

$ kubectl -n csi-system get all
NAME                                              READY   STATUS   RESTARTS   AGE
pod/secrets-store-csi-driver-upgrade-crds-d4tqc   0/1     Error    0          15s
pod/secrets-store-csi-driver-upgrade-crds-zs4p9   0/1     Error    0          4s

NAME                                              STATUS    COMPLETIONS   DURATION   AGE
job.batch/secrets-store-csi-driver-upgrade-crds   Running   0/1           15s        15s

$ kubectl -n csi-system logs secrets-store-csi-driver-upgrade-crds-d4tqc
exec /kubectl: exec format error

I am unable to understand this error as I am deploying the helm chart with linux images on a linux amd64 platform. I need help understanding this error.

What did you expect to happen:
The helm chart should be successfully installed and all pods should be running.

Anything else you would like to add:
The cluster nodes are using an OS image based on Oracle Linux 8.9 amd64.

System Info:
  Kernel Version:             5.15.0-206.153.7.el8uek.x86_64
  OS Image:                   Oracle Linux Server 8.9
  Operating System:           linux
  Architecture:               amd64
  Container Runtime Version:  cri-o://1.30.0-296.el8
  Kubelet Version:            v1.30.1
  Kube-Proxy Version:         v1.30.1

The helm chart default values are being overridden only for the image repository and the image pull secrets. Default values for linux.enabled: true and windows.enabled: false are being used.

Which provider are you using:
I am just deploying the stock helm chart for now.

Environment:

• Secrets Store CSI Driver version: (use the image tag): 1.4.5
• Kubernetes version: (use kubectl version): 1.30.1

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten