This repository has been archived by the owner on Nov 30, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 180
Configurable endpoint for S3 object storage #481
Labels
Comments
Adding a note here: Probably also want to include an option to toggle secure yes/no for the docker storage driver. |
If anyone has a good doc on getting this set up, that would be appreciated. We can fizzle that down into a consumable document for other users. |
Closed
This was referenced May 1, 2017
Closed
kingdonb
pushed a commit
to kingdonb/workflow-deis
that referenced
this issue
Aug 28, 2017
for an External minio server using s3.accesskey and s3.secretkey, will add s3.regionendpoint later WIP: to resolve deis#481 More changes will go in deis/builder deis/controller deis/database deis/registry, all of which have dependencies on s3/swift storage (In PoC I overrode DEIS_MINIO_SERVICE_HOST and DEIS_MINIO_SERVICE_PORT, I'd like to use that shortcut and it seems safe, but expose it in values as s3.regionendpoint, reorganizing values.yaml so the off-cluster minio configuration is very obvious.)
This issue was moved to teamhephy/workflow#52 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Deis currently supports Minio (S3-compatible API) for object storage only within the cluster and not for production deployments. Deis also supports S3 for object storage, but not with a configurable "regionendpoint", requiring the use of specific Amazon AWS regions.
Request is to modify Deis to accept a s3.region_endpoint parameter within the generate_params.toml file on the deis/charts project, which will be stored as a Kubernetes secret like the other parts of configuration. This will allow for operators to configure Deis Object Storage to use hosted S3-compatible deployments outside of the cluster.
(Related) Is a change to the deis/object-storage-cli to pass in the configurable endpoint above to the s3 driver via the optional "regionendpoint" param.
(per doc: https://github.com/docker/distribution/blob/master/docs/storage-drivers/s3.md)
The text was updated successfully, but these errors were encountered: