Problem after update from k3s version v1.30.4+k3s1 to v1.31.0+k3s1

[husarzlukasz]

What steps did you take and what happened:
Problem with secrets-store-csi-driver after update k3s to v1.31.0+k3s1

before update to version: v1.31.0+k3s1 everything working excelent, after instantly had a tons of warnings:

Warning:
 kubernetes.io/csi: mounter.SetUpAt failed to get CSI client: driver name secrets-store.csi.k8s.io not found in the list of registered CSI drivers

 Warning  FailedMount             48s (x31 over 47m)    kubelet                     MountVolume.SetUp failed for volume "backend" : kubernetes.io/csi: mounter.SetUpAt failed to get CSI client: driver name secrets-store.csi.k8s.io not found in the list of registered CSI drivers

nothing changes in volumes configuration and csi-driver configuration:
csidriver seems to be okay, I have a latest version.

secrets-store.csi.k8s.io false true false <unset> false Ephemeral

Volumes:
  backend:
    Type:              CSI (a Container Storage Interface (CSI) volume source)
    Driver:            secrets-store.csi.k8s.io
    FSType:            
    ReadOnly:          true
    VolumeAttributes:      secretProviderClass=backend

Delete pod with warning to recreate cause a pod stuck in init state because of error with mounting

after downgrade cluster to previous version: v1.30.4+k3s1 everything back to normal and working

What did you expect to happen:
Working as before with new k3s version

Anything else you would like to add:

Which provider are you using:
HashiCorp Vault

Environment:

• Secrets Store CSI Driver version: 1.4.5):
• Kubernetes version: v1.31.0+k3s1:

[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

[aramase]

/remove-lifecycle rotten

[brandond]

Are you sure that the CSIDriver is still registered?

brandond@dev01:~$ kubectl get node -o wide
NAME           STATUS   ROLES                  AGE   VERSION        INTERNAL-IP   EXTERNAL-IP   OS-IMAGE           KERNEL-VERSION   CONTAINER-RUNTIME
k3s-server-1   Ready    control-plane,master   69s   v1.31.4+k3s1   172.17.0.4    <none>        K3s v1.31.4+k3s1   6.8.0-1016-aws   containerd://1.7.23-k3s2

brandond@dev01:~$ kubectl get csidriver
NAME                       ATTACHREQUIRED   PODINFOONMOUNT   STORAGECAPACITY   TOKENREQUESTS   REQUIRESREPUBLISH   MODES       AGE
secrets-store.csi.k8s.io   false            true             false             <unset>         false               Ephemeral   5s