Which s3 compatible blob storage?

Question

I want deploy a s3 compatible blob storage in my Kubernetes Cluster. I already use GlusterFS for volumes like mongodb, and I tried to set up minio with the helm chart https://github.com/helm/charts/tree/master/stable/minio. I just realize I can't scale up minio easily because of erasure code.

So I have some questions about blob storage solutions :

Is GlusterFS blob storage service stable and reliable (https://github.com/gluster/gluster-kubernetes/tree/master/docs/examples/gluster-s3-storage-template) ?
Do I must use OpenShift to deploy GlusterFS blob storage as I read in the web ? I think no because I can see simple Kubernetes manifests in the GlusterFS repo like this one : https://github.com/gluster/gluster-kubernetes/blob/master/deploy/kube-templates/gluster-s3-template.yaml.
Is it easy to use Minio federation in Kubernetes ? Is it easily scalable with a "helm upgrade --set replicas=X" or do I need manually upgrade minio configuration ?

As you can see, I feel lost with this s3 storage. So if you have more information/solutions, do not hesitate.

Thanks in advance !

score 0 · Answer 1 · answered Sep 10 '19 at 11:35

About reliability you should read more about user experience like:

Why openshift with glusterFS:

For standalone Red Hat Gluster Storage, there is no component installation required to use it with OpenShift Container Platform. OpenShift Container Platform comes with a built-in GlusterFS volume driver, allowing it to make use of existing volumes on existing clusters but Red Hat Gluster Storage is a commercial storage software product, based on Gluster.

How to deploy it in AWS

For minio please follow official docs:

ConfigMap allows injecting containers with configuration data even while a Helm release is deployed.

To update your MinIO server configuration while it is deployed in a release, you need to

Check all the configurable values in the MinIO chart using helm inspect values stable/minio.

Override the minio_server_config settings in a YAML formatted file, and then pass that file like this helm upgrade -f config.yaml stable/minio.

Restart the MinIO server(s) for the changes to take effect

I didn't try but, but as per documentation:

For federation I can see additional environment variables in the values.yaml.

In addition you should Run MinIO in federated mode Federation Quickstart Guide

Here you can find differences between google and amazon s3 sotrage or Cloud Storage interoperability from gcloud perspective.

Hope this help.

Thank you Hanx. I know GlusterFS and it is reliable in my opinion. But I would talk about GlusterFS S3, not GlusterFS. I don't want have buckets in a cloud provider. I already read the minio documentation about federation and yes, I know there are values to configure federation. But with the federation, I have to restart all minio pods with the new configuration if I update these values to add a new minio cluster. — Antoine, Sep 10 '19 at 14:33
If it's crucial than you can consider using [configmap or secrets as environment variables](https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/#mounted-configmaps-are-updated-automatically) instead of using pure env varaibles `Mounted configmaps and secrets are updated automatically`. In addition I didn't use GlusterFS S3, — Mark, Sep 11 '19 at 09:10

Which s3 compatible blob storage?

1 Answers1