Closed anothertobi closed 11 months ago
@zugao could you maybe have a look at this one (#796 is the fix) and release a new K8up version?
@anothertobi just released v2.7.2. Can you let me know if the problem is fixed?
With K8up v2.7.2 the S3 bucket creation and backups in the AWS region eu-central-2
work as expected. Thanks for the new release 🎉
Description
For recently opened AWS regions, bucket creations through restic fail with a
400 Bad Request
during theBucketExists
check.Additional Context
minio-go defaults to the
s3.dualstack.us-east-1.amazonaws.com
endpoint when an unknown region is provided. The authorization header however still contains the provided, unknown, region. This results in a400 Bad Request
when calling the S3 API.New regional S3 endpoints were added to minio-go in https://github.com/minio/minio-go/pull/1726 and released with version v7.0.44 (makes
eu-central-2
a "known" region). This version was included in restic in https://github.com/restic/restic/commit/f4d3ed77c458af6fbef2be7fe0acfb4bf4fa509a and released with version v0.15.0.K8up currently uses github.com/restic/restic v0.14.0 and already has a PR pending to upgrade restic to v0.16.0 https://github.com/k8up-io/k8up/pull/796 (fixes the issue).
Logs
Expected Behavior
The packaged restic binary in the K8up container image can create an S3 bucket in the
eu-central-2
AWS region.Steps To Reproduce
Version of K8up
v2.7.1
Version of Kubernetes
1.27
Distribution of Kubernetes
EKS