if I create pv with the manual way as follow
`apiVersion: v1
kind: PersistentVolume
metadata:
name: manualbucket-with-path
spec:
storageClassName: csi-s3
capacity:
storage: 10Gi
accessModes:
attention: the account in the csi-s3-secret-other is different from the acount in the values.yaml,as follow
so it cause an error beacuse of the different account。In the Daemon Pod(csi-s3-driver) show the error message,
failed to set internal data for access key/secret key from passwd file.
I thank, the account first write in the .passwd-s3fs is minio:123456789,after change the account (test:test),finally the .passwd-s3fs file content is test:test56789。so this case the s3fs command error。
if I create pv with the manual way as follow `apiVersion: v1 kind: PersistentVolume metadata: name: manualbucket-with-path spec: storageClassName: csi-s3 capacity: storage: 10Gi accessModes:
attention: the account in the csi-s3-secret-other is different from the acount in the values.yaml,as follow
so it cause an error beacuse of the different account。In the Daemon Pod(csi-s3-driver) show the error message,
failed to set internal data for access key/secret key from passwd file.
I thank, the account first write in the .passwd-s3fs is minio:123456789,after change the account (test:test),finally the .passwd-s3fs file content is test:test56789。so this case the s3fs command error。