Adding an s3 default provisioner based on minio #89
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.
Fixes: #65
This PR brings some much needed compatibility with
score-compose
by adding an s3 bucket provisioner by default using an in-cluster object storage based on minio.This follows the current best practises of k8s provisioner development:
s3
resource. We intentionally use a shared access key across all buckets for now to match score-compose behavior.testing
This was tested with the following score file:
This started up a pod with the minio object storage client cli.
I could then run the following:
I've also tested it with the following score file that uses a duckdb s3 client: https://gist.github.com/astromechza/b5cedbce68dd0baa6252728ff1de9505