Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

After update from k3s version v1.30.4+k3s1 to v1.31.0+k3s1 #10812

Closed
husarzlukasz opened this issue Sep 4, 2024 · 2 comments
Closed

After update from k3s version v1.30.4+k3s1 to v1.31.0+k3s1 #10812

husarzlukasz opened this issue Sep 4, 2024 · 2 comments

Comments

@husarzlukasz
Copy link

Problem with secrets-store-csi-driver after update to v1.31.0+k3s1

Environmental Info:
K3s Version before update:
k3s version v1.30.4+k3s1
after update:
v1.31.0+k3s1

Node(s) CPU architecture, OS, and Version:
3x nodes: Linux 6.9.7+bpo-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.9.7-1~bpo12+1 (2024-07-03) x86_64 GNU/Linux

Cluster Configuration:
3 master/agent nodes

Describe the bug:
After upgrade to latest version of k3s i notice a lot of warnings of:

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 was okay:

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 ^

Steps To Reproduce:
Have https://github.com/kubernetes-sigs/secrets-store-csi-driver deployed and used
k3s version v1.30.4+k3s1 upgrade to v1.31.0+k3s1

Expected behavior:
no warnings: driver name secrets-store.csi.k8s.io not found in the list of registered CSI drivers

Actual behavior:

Downgrade cluster to previous version resolved the problem

@brandond
Copy link
Member

brandond commented Sep 4, 2024

I would probably open an issue with the secrets-store-csi-driver project. They can suggest steps to troubleshoot. Did you perhaps need to upgrade it to be compatible with Kubernetes 1.31?

@brandond brandond closed this as completed Sep 4, 2024
@husarzlukasz
Copy link
Author

@brandond Thanks for the answer. I've created a ticket in the secrets-store-csi-driver project. I currently have the latest version ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done Issue
Development

No branches or pull requests

2 participants