csi-driver-smb icon indicating copy to clipboard operation
csi-driver-smb copied to clipboard

This driver allows Kubernetes to access SMB Server on both Linux and Windows nodes.

Results 70 csi-driver-smb issues
Sort by recently updated
recently updated
newest added

**What type of PR is this?** /kind failing-test **What this PR does / why we need it**: test: skip one flacky windows test **Which issue(s) this PR fixes**: Fixes #...

kind/failing-test
approved
size/XS
cncf-cla: yes
release-note-none

**What type of PR is this?** /kind bug **What this PR does / why we need it**: fix: delete volume error in archive deletion mode when `onDelete: archive`, there could...

kind/bug
release-note
approved
cncf-cla: yes
size/S

**What happened**: csi-driver-smb doesn't work on AL 2023 Nodes and doesnt spit out any (useful error). I installed a new Kubernetes Cluster on AWS with the Version 1.30. The Standard...

### Preface Apologies if this is an upstream bug, feel free to close if so. **What happened**: 1. have a PVC in a helm chart, no pre-existing PV for whatever...

Checking if there is a possible configuration/option for csi-driver-smb to limit or set the number of mount retries after failing to mount?

lifecycle/stale

MountOptions declared in StorageClass don't seem to apply ``` apiVersion: storage.k8s.io/v1 kind: StorageClass ... mountOptions: - noperm - noserverino ``` **What happened**: the PVC got created but remained in Pending...

lifecycle/stale

**What happened**: Access to the SMB share is not restricted per gid: ``` [admin@mgmt01 fsx]$ k exec -it smb-test -n dev -- bash groups: cannot find name for group ID...

**What happened**: Pod Creation Error with event: ` Warning FailedMount 28s (x8 over 92s) kubelet MountVolume.MountDevice failed for volume "pvc-f03018a6-a450-41a9-b4f7-0609a57120e7" : rpc error: code = Internal desc = volume(viaps012-int.lia.int/archives#pvc-f03018a6-a450-41a9-b4f7-0609a57120e7##) mount...

lifecycle/stale

Hi, I have a question. There is a possiblity to store smbcreds used by Persistent Volume in Vault and inject them with Vault agent somehow for example into smb pods...

**What happened**: Pod stuck in creation phase with: ``` NewSmbGlobalMapping failed. output: "New-SmbGlobalMapping : The Workstation service has not been started. \r\nAt line:1 char:190\r\n+ ... ser, $PWord;New-SmbGlobalMapping -RemotePath $Env:smbremotepath -Cred...