-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
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
Failed to create S3 client when enabling authenticationSource: pod #293
Comments
Hey @inesshz, thanks for the report. Would you be able to share your Mountpoint logs with us after enabling debug CRT logs by adding |
Here are the logs from the driver's pod :
Logs from the node ([ERROR]):
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
/kind bug
What happened?
I upgraded to version 1.9.0 and set podInfoOnMountCompat to true and also added authenticationSource=pod to PV and I'm now receiving the following :
Warning FailedMount 37s (x12 over 9m13s) kubelet MountVolume.SetUp failed for volume "s3-pv" : rpc error: code = Internal desc = Could not mount "" at "/var/lib/kubelet/pods/78dfad8e-3eaf-44ba-93c8-fbf8cae8abc0/volumes/kubernetes.io~csi/s3-pv/mount": Mount failed: Failed to start service output: Error: Failed to create S3 client Caused by: 0: initial ListObjectsV2 failed for bucket in region us-east-1 1: Client error 2: No signing credentials available, see CRT debug logs Error: Failed to create mount process
If I switch back to using s3 csi driver role instead of using pod role, it works fine and the mount operation works successfully.
What you expected to happen?
S3 bucket is mounted
How to reproduce it (as minimally and precisely as possible)?
I followed the following https://github.com/awslabs/mountpoint-s3-csi-driver/blob/main/examples/kubernetes/static_provisioning/pod_level_identity.yaml
Deploy s3 csi with podInfoOnMountCompat set to true.
Both driver and pod roles are configured correctly and they have the correct Trusted entities and policies attached (s3:* and kms:*)
Here is the pv yaml :
Anything else we need to know?:
Environment
kubectl version
): 1.30The text was updated successfully, but these errors were encountered: