[release-1.23] Switch from Google Buckets to AWS S3 Buckets #6571
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.
Proposed Changes
The Google storage account will be deactivated soon by the end of Nov 2022. So, we need to shift AWS s3. This PR makes it possible
Types of Changes
New Feature - storing build artifacts and logs into amazon s3 bucket
Verification
rancher-internal
account in AWS -> https://s3.console.aws.amazon.com/s3/buckets/k3s-ci-builds.drone-publish
pipeline by @ivan-claire who is part of eio team. Can you confirm ?Linked Issues