You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the company I work for bought a Synology SAN to be used as a CSI for our Kubernetes clusters. We need support for ReadWriteMany volumes. I couldn't find anything on the Synology documentation website, if It is officially supported. During my evaluation of the Synology SAN, I however encountered some mixed results. It's seems to be not working as intended.
I created 3 pods with the same RWX pvc and created an individual file for each pod, on the shared location.
kubectl get po -owide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
busybox-pod-1 1/1 Running 0 23m 10.244.1.72 devops-w1 <none><none>
busybox-pod-2 1/1 Running 0 23m 10.244.2.64 devops-w2 <none><none>
busybox-pod-3 1/1 Running 0 23m 10.244.2.65 devops-w2 <none><none>foriin {1..3} ;do kubectl exec -it busybox-pod-"${i}" -- ls /mnt/shared/ ;done
busybox-pod-1.file lost+found
busybox-pod-2.file busybox-pod-3.file lost+found
busybox-pod-2.file busybox-pod-3.file lost+found
Expected behaviour:
Every file should be visible in each pod.
Hello,
the company I work for bought a Synology SAN to be used as a CSI for our Kubernetes clusters. We need support for
ReadWriteMany
volumes. I couldn't find anything on the Synology documentation website, if It is officially supported. During my evaluation of the Synology SAN, I however encountered some mixed results. It's seems to be not working as intended.I created 3 pods with the same
RWX
pvc and created an individual file for each pod, on the shared location.Expected behaviour:
Every file should be visible in each pod.
Bug:
Only files on the same host are visible.
Replication of the bug:
Then create 3 busybox pods using the same
ReadWriteMany
PersistentVolumeClaim
.Thanks for any help or suggestions you can offer.
Kind regards.
The text was updated successfully, but these errors were encountered: