Fix issue with S3 bucket access #12
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Z4ck404
approved these changes
Feb 12, 2024
There was a problem hiding this comment.
Hey @fabiorauber,
Good catch, I remember I saw this error when I was testing but didn't verify that the fix was pushed.
Can you also update the version file to trigger a build ?
otherwise LGTM
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I couldn't mount the S3 bucket with S3 CSI Driver, and the following error was recorded:
GRPC error: rpc error: code = Internal desc = Could not mount "s3-bucket" at "/var/lib/kubelet/pods/322559df-ee71-4dc2-9b6f-c981a140ff2f/volumes/kubernetes.io~csi/s3-bucket-s3-pv/mount": Mount failed: Failed to start service output: Error: Failed to create S3 client Caused by: 0: initial ListObjectsV2 failed for bucket s3-bucket in region us-east-1 1: Client error 2: Forbidden: Access Denied Error: Failed to create mount processTurned out there was a slash trailing the bucket resource specification in the IAM Policy.