minio | Minio Object Storage in Kubernetes , used by Deis Workflow | Cloud Storage library

I'm using Minio Server to handle files in my nodejs API, basically to emulate s3 locally. I generated Presigned Url to upload images directly.

Presign Url Generation works fine but when I upload my file from Postman the file it gives me this error:

My objective is connect two different containers to get data, in other words:

• I have an instance of OpenCTI working in my docker , and I can access it through my browser (http://localhost:8080).
• Consequently, I am developing another one to get data from OpenCTI.

To connect both, I already created a docker network called "minharede".

However is not working.

The configuration of my containers is:

Docker-compose file of OpenCTI:

What is the preferred Kubernetes storageClass for a PersistentVolume used by a Postgresql database? Which factors should go into consideration choosing the storageClass when I have the choice between S3 (Minio), NFS and HostPath?

I was taking a look at Hub—the dataset format for AI—and noticed that hub integrates with GCP and AWS. I was wondering if it also supported integrations with MinIO.

I know that Hub allows you to directly stream datasets from cloud storage to ML workflows but I’m not sure which ML workflows it integrates with.

I would like to use MinIO over S3 since my team has a self-hosted MinIO instance (aka it's free).

I'm experimenting with kubernetes and a minio deployment. I have a k3s 4 node cluster, each one with 4 50GB disk. Following the instructions here I have done this:

1. First I installed krew in order to install the minio and the directpv operators.

2. I installed those two without a problem.

3. I formatted every Available hdd in the node using kubectl directpv drives format --drives /dev/vd{b...e} --nodes k3s{1...4}

4. I then proceed to make the deployment, first I create the namespace with kubectl create namespace minio-tenant-1, and then I actually create the tenant with:

   kubectl minio tenant create minio-tenant-1 --servers 4 --volumes 8 --capacity 10Gi --storage-class direct-csi-min-io --namespace minio-tenant-1

5. The only thing I need to do then is expose the port to access, which I do with: kubectl port-forward service/minio 443:443 (I'm guessing it should be a better way to achieve this, as the last command isn't apparently permanent, maybe using a LoadBalancer or NodePort type services in the kubernetes cluster).

So far so good, but I'm facing some problems:

• When I try to create an alias to the server using mc the prompt answer me back with:

mc: Unable to initialize new alias from the provided credentials. Get "https://127.0.0.1/probe-bucket-sign-9aplsepjlq65/?location=": x509: cannot validate certificate for 127.0.0.1 because it doesn't contain any IP SANs

I can surpass this with simply adding the --insecure option, but I don't know why it throws me this error, I guess is something how k3s manage the TLS auto-signed certificates.

• Once created the alias (I named it test) of the server with the --insecure option I try to create a bucket, but the server always answer me back with:

  mc mb test/hello

  mc: Unable to make bucket \test/hello. The specified bucket does not exist.

So... I can't really use it... Any help will be appreciated, I need to know what I'm doing wrong.

I have a Minio Replicated system with 4 nodes. It worked well for about 1 year. Then, recently, after some curruption and uploading errors, it has been decided to upgrade the Minio version several times during the last two weeks to check if the corruption problem derived from some already fixed issues. Then suddenly files started to disappear from Minio, more than 1TB of data has been lost, so it has been decided to downgrade the minio cluster to a single minio instance temporary.

Therefore, i would like to understand the logic of how distributed minio communicates to the others nodes to delete objects, and if there is a chance that minio could, by itself, delete objects because they are currupted or inconsistent, due to disk damage or a power blackout.

I am using django 3.1.0 with django-storages 1.12.3. I am using an S3 backend to store media files (Minio). I am trying to post the file to S3, and include additional user metadata to the S3 object. This additional metadata comes from the POST request used to upload the file to django. With S3, custom metadata can be added by including additional key-value pairs to the HTTP header for the POST request sent to the S3 server when the file is uploaded, where the custom keys would be prefixed with 'X-Amz-Meta-'.

I am using a FileField in a django model, and files are uploaded using a REST API endpoint. As far as I understand it, when django receives the file, it stores it temporarily, and then, when saving the FielField on the model instance, the file is posted to the S3 server. I want to modify the flow, so that the custom metadata is taken from the request and included in the post to the S3 server.

Any idea how I can take data from the initial request, and pass it to the header of the POST request being sent to S3?

After trying Option 1 from Helge Schneider's answer, I did a little modification and got it to work.

I am using django rest framework, so I modified the serializer .save() method.

I had the previous version (from last yr) of minio running well behind traefik and on portainer with no issues. I attempted an upgrade 4 days ago to the new version and it's been downhill since then. I get the login page but it won't accept credentials; Error: {"code":500,"detailedMessage":"Post \"https://storage.example.com/\": dial tcp :443: i/o timeout","message":"invalid Login"} I suspect it has something to do with the TLS certificate.

Below is my compose file, I've generated the certs as required; any assistance is is welcomed:

i am working on nginx and minio on the ubuntu.

the minio server is started from

'nohup /usr/local/bin/minio server /data/tenant1 --address :9001 > /opt/logs/minio.log 2>&1 &#',

and it is working.

then I started the nginx and configure the nginx server with the following configuration.