We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The pod shows FailedMount in its describe logs. More precisely
MountVolume.MountDevice failed for volume "myvolume" : rpc error: code = Unknown desc = stat /var/lib/kubelet/plugins/kubernetes.io/csi/ru.yandex.s3.csi/6906bd35218cf1d989e23a82b60f291f35eb9b7412b0038d021fb75d3c10dc24/globalmount: software caused connection abort
Here the yaml for the PV:
apiVersion: v1 kind: PersistentVolume metadata: name: MyPV spec: accessModes: - ReadWriteOnce capacity: storage: 10Gi claimRef: apiVersion: v1 kind: PersistentVolumeClaim name: claimname namespace: claimnamespace csi: controllerPublishSecretRef: name: csi-s3-secret namespace: kube-system driver: ru.yandex.s3.csi nodePublishSecretRef: name: csi-s3-secret namespace: kube-system nodeStageSecretRef: name: csi-s3-secret namespace: kube-system volumeAttributes: capacity: 10Gi mounter: s3fs options: "" volumeHandle: mybucket/myfolder persistentVolumeReclaimPolicy: Retain storageClassName: csi-s3 volumeMode: Filesystem
The text was updated successfully, but these errors were encountered:
It seems that s3fs is actually currently buggy as multiple users commented on #16
(if someone asks, I actually want to try out s3fs because I am also running into chmod problems with geesefs)
Sorry, something went wrong.
I also encountered this problem:
No branches or pull requests
The pod shows FailedMount in its describe logs. More precisely
Here the yaml for the PV:
The text was updated successfully, but these errors were encountered: