MinIO FAQ

The file size is too large to upload files to MinIO using the Web-UI

The ingress controller limits the maximum body size for HTTP requests. If you encounter an error like 413 Request Entity Too Large, you will need to increase the limit in the ingress controller configuration. When using the ingress-nginx controller, this can be done by adding or editing the relevant annotation on that ingress resource. For example, to set the maximum body size to 500Mi, you can add the following annotation:

annotations:
  nginx.ingress.kubernetes.io/proxy-body-size: "500m"

Alternatively use the MinIO command line client and port forwarding to upload bigger files.

The MinIO tenant is not getting ready

If you have an error message such as

Get "https://operator.minio.svc.cluster.local:4222/webhook/v1/getenv/minio/defaulttenant?key=MINIO_ARGS": x509: certificate has expired or is not yet valid: current time 2024-06-11T15:49:46Z is after 2024-05-15T12:39:48Z

MinIO's TLS certificate has expired and needs to be renewed.

Storage is slow

You can try attaching another SSD to the node and use that as a dedicated storage class for MinIO. You can check the performance with:

fio --randrepeat=1 --ioengine=libaio --direct=1 --gtod_reduce=1 --name=fiotest --filename=testfio --bs=4k --iodepth=64 --size=8G --readwrite=randrw --rwmixread=75

MinIO has run out of space

If MinIO has run out of space, you can either increase the size of the underlying PersistentVolume (if your StorageClass supports that) or delete old objects. You can also set up lifecycle rules to automatically delete old objects, this needs to be set up for each bucket individually and makes sense if you have objects that can be deleted after a certain time (e.g. old pipeline runs).