Can I have a guest login?

[chattytak]

I tried to login as a guest, but it didn't work because of a parameter error.
Is guest login supported?

[andyzhangx]

what does guest login mean? do you have more details? @chattytak

[chattytak]

I mean the standard option for cifs, which eliminates the need for username and password.-o guest

[andyzhangx]

if you run mount -t cifs -o guest ..., and works on that agent node, I think that should also work with this CSI driver.

[chattytak]

I added the guest option as in this config. In addition, I removed the credential specification. However, the -o username= specification seems to be hard coded and causes an option error.

---
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: smb
provisioner: smb.csi.k8s.io
parameters:
  # On Windows, "*.default.svc.cluster.local" could not be recognized by csi-proxy
  source: "//smb-server.default.svc.cluster.local/share"
  # if csi.storage.k8s.io/provisioner-secret is provided, will create a sub directory
  # with PV name under source
  #csi.storage.k8s.io/provisioner-secret-name: "smbcreds"
  #csi.storage.k8s.io/provisioner-secret-namespace: "default"
  #csi.storage.k8s.io/node-stage-secret-name: "smbcreds"
  #csi.storage.k8s.io/node-stage-secret-namespace: "default"
volumeBindingMode: Immediate
mountOptions:
  - dir_mode=0777
  - file_mode=0777
  - uid=1001
  - gid=1001
  - noperm
  - mfsymlinks
  - cache=strict
  - noserverino  # required to prevent data corruption
  - guest

[andyzhangx]

username and password is hardcoded now, could you make sure mount -t cifs -o guest ... on your agent node? I could make a code change to support guest mount option later.

[andyzhangx]

try with kubectl create secret generic smbcreds --from-literal mountOptions="dir_mode=0777,file_mode=0777,uid=0,gid=0,mfsymlinks,guest" and set ImagePullPolicy: Always for latest driver image, the latest master version should fix the issue with PR: #462

[chattytak]

Setting mountOptions for Secret for credentials is a method that is not written in existing Basic Usage so I don't have an idea of how to use it.
Why is it necessary to set mountOptions on the Secret?
What is the difference from the mountOptions parameter in StorageClass?
Conversely, is StorageClass's mountOptions no longer used? If so, it feels out of standard and redundant and uncomfortable as a setting.
If csi is a framework for standardization, but it seems to evolve on its own by adding more proprietary parameters, that would be a regression, not an evolution.

[andyzhangx]

it's mentioned here: https://github.com/kubernetes-csi/csi-driver-smb/blob/master/docs/driver-parameters.md#provide-mountoptions-for-deletevolume

[andyzhangx]

and here is the reason why there is not mountOptions support in DeleteVolume: container-storage-interface/spec#507 (comment)