incorrect mount option was specified - mount options doesn't work #147
Comments
k8s-ci-robot
added
the
kind/support
|
Not sure if dir_mode and file_mode is valid mount option to nfs client. Where do u see these two option? |
|
And have you tried this #91 (comment) |
|
I see a few different sources indicating these options are available for their storage. But I didn't find anything for EFS Seems it can be used in PV for static provision and Storage class for dynamic provision. I am wondering if that's because EFS doesn't support this. I found note here.
Currently, I just create a launcher to change permission as you attached. This is ok but brings one extra step. Since I know the uid and gid of my applications, if mountOption is supported, I can create PV for specific application with known uid and gid. As there's a workaround, this is not a big deal. |
|
Using access point (without IAM) sounds a good option. Does this work for you? |
|
I try to use iam role but not work for me. efs policy: {
"Version": "2012-10-17",
"Id": "xxxxxx",
"Statement": [
{
"Sid": "allow-xxxxxx-can-use-this-efs",
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws-cn:iam::xxxxxx:role/xxxxxx"
},
"Action": [
"elasticfilesystem:ClientMount",
"elasticfilesystem:ClientWrite",
"elasticfilesystem:ClientRootAccess"
],
"Resource": "arn:aws-cn:elasticfilesystem:cn-north-1:xxxxxx:file-system/fs-xxxxxx"
}
]
}pv.yaml apiVersion: v1
kind: PersistentVolume
metadata:
name: efs-pv
spec:
capacity:
storage: 5Gi
volumeMode: Filesystem
accessModes:
- ReadWriteMany
persistentVolumeReclaimPolicy: Retain
storageClassName: efs-sc
mountOptions:
- tls
- iam
csi:
driver: efs.csi.aws.com
volumeHandle: fs-xxxxxxcd aws-efs-csi-driver/examples/kubernetes/multiple_pods
kubectl apply -f specs/ # branc 0.3
kubectl describe pods app1Error message: I found path |
|
@wanghao923 It looks to me like you're using an older version of the driver. Can you please confirm whether you're running |
|
It's ok if I use master branch. There is the other error when I use branch release-0.3. Error message: Correct DNS name is "fs-xxxxxx.efs.cn-north-1.amazonaws.com.cn", This is the other error. Yesterday I also used branch release-0.3 but I modified the tag of image amazon/aws-efs-csi-driver. default version is 0.2.0. I can reproduce yesterday error if I use version 0.3.0 in branch release-0.3. So before error is beacuse of I updated the version of amazon/aws-efs-csi-driver to 0.3.0. Fortunately, These errors are fixed in the master branch. Thanks |
|
@wanghao923 Good to hear. I've asked for a new tagged release so we don't have to work against a moving target. |
|
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
k8s-ci-robot
added
the
lifecycle/stale
|
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
k8s-ci-robot
added
lifecycle/rotten
|
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
|
@fejta-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
I have a pod with non root user to run. I plan to mount to the user's home disk. The problem that user doesn't have permission to write files because it needs
rootpermission on volumes.I plan to add mountOptions in the PV field and I assume this will use this options to mount the volume.
From the logs, seem options are applied to mount command, what I am curious is why they are
incorrect mount option. Seems they are pretty standard commands. Any insights here?/triage support
The text was updated successfully, but these errors were encountered: