-
Notifications
You must be signed in to change notification settings - Fork 261
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
ACK S3 bucket - MalformedXML #2336
Closed
itaiatu opened this issue
Feb 19, 2025
· 3 comments
· Fixed by aws-controllers-k8s/s3-controller#154
Closed
ACK S3 bucket - MalformedXML #2336
itaiatu opened this issue
Feb 19, 2025
· 3 comments
· Fixed by aws-controllers-k8s/s3-controller#154
Labels
target/q1-2025
Issues scheduled for Q1 in 2025
Comments
We will take a look and see if it's reproducible on our end |
We have found the issue and will post back with next steps. |
ack-prow bot
pushed a commit
to aws-controllers-k8s/s3-controller
that referenced
this issue
Feb 21, 2025
…#154) fixes aws-controllers-k8s/community#2336 Description of changes: Handles bucket creation in relation to the `LocationConstraint`, particularly for the `us-east-1` region 1. **LocationConstraint Region Behavior** - **us-east-1**: - If no `LocationConstraint` is provided, creation succeeds (no `CreateBucketConfiguration` is sent). - If a user specifies `LocationConstraint=us-east-1`, S3 returns `InvalidLocationConstraint` (marked as terminal). - If a user specifies a different region (e.g., `LocationConstraint=us-west-2`), S3 returns `PermanentRedirect` (also marked as terminal). - **Non-us-east-1**: - If no `LocationConstraint` is specified, controller defaults it to match its own region, creation succeeds. - If `LocationConstraint` matches the region, creation succeeds. - If `LocationConstraint` mismatches the region, terminal error. 2. **Terminal Errors** - `PermanentRedirect`, `InvalidLocationConstraint` and `IllegalLocationConstraintException` are now handled as terminal conditions to avoid repeated reconciles. 3. **Bucket Name Immutability** - Enforced via CRD validation (`x-kubernetes-validations`) and generator config (`is_immutable: true`). By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Hi @itaiatu, the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
We have upgraded the ACK S3 controller from v1.0.18 to v1.0.23.
When trying to create a simple s3 bucket, we get the following error from AWS:
Steps to reproduce
Create and apply simple s3 bucket ack object
The object looks like this after it's being reconciled by the ACK controller:
When looking in CloudTrail for the
test-bucket-v1.0.23
resource, we have theCreateBucket
event:Then, we used the old
v1.0.18
ACK S3 controller version and it correctly reconciled the bucket and created it in the cloud.Another thing is that, in the CloudTrail, the event for the same bucket (but with name
test-bucket-v1.0.18
), when created with thev1.0.18
ACK S3 controller version, looks like this:We can see that the
CreateBucketConfiguration
is missing.The problem could be from the migration to
aws-sdk-go-v2
.Expected outcome
Create the s3 bucket in the cloud.
Environment
The text was updated successfully, but these errors were encountered: