[components] Upgrade minio to the latest version

[haoxins]

Feature Area

/area components

Is there any reason not to upgrade the minio to the latest version?
Is it open for others to submit PR for this?

[Bobgy]

@haoxins Yes, absolutely welcome a PR on this!

[MatthiasCarnein]

Just a heads up, Minio changed its license from Apache 2.0 to AGPL v3.There is a bit of controversy surrounding this decision:

minio/minio#12157
minio/minio#12158
minio/minio#12156

[Bobgy]

Thanks, we don't allow AGPL, so if upgrade, we can only choose a version before it was changed to AGPL.

[Bobgy]

We might need to consider a MinIO alternative, so that people can keep getting security fixes.

[NikeNano]

We might need to consider a MinIO alternative, so that people can keep getting security fixes.

What alternative are there out there I am only aware of rook/ceph. What are we looking for when it comes to replacing Minio except the license?

[haoxins]

I think SeaweedFS could be another alternative.

[MatthiasCarnein]

It seems that NooBaa could be another alternative using an Apache License. The Datashim project uses it in their tutorials with BackingStore PV-Pool to setup an S3 Object Store. The other BackingStores could potentially replace Minio's Gateway functionality.

[haoxins]

@MatthiasCarnein just a bit curious about the License details.

Because this project uses argo-workflows, and argo-workflows uses MinIO v7 APIs, https://github.com/argoproj/argo-workflows/blob/master/go.mod#L35
Is this also influence Kubeflow pipelines?

[MatthiasCarnein]

@haoxins I'm not a lawyer but from my understanding the Minio Client SDK for Go is a separate piece of software that uses the Apache 2.0 license: https://github.com/minio/minio-go/blob/master/LICENSE

[MatthiasCarnein]

Minio alternatives are also discussed here: #7878