[feature] Use s3:// for MinIO usage

[AndersBennedsgaard]

Feature Area

/area frontend
/area backend
/area sdk

(I am a little unsure which area is affected by this feature request, so feel free to change the area labels)

What feature would you like to see?

Use s3:// for MinIO instead of minio://.

What is the use case or pain point?

Since MinIO exposes an S3 compatible API we might as well just use s3:// as the URL protocol prefix.

A big reason for this, is that not many other tools use minio:// as prefix (in fact, I was not able to find any), so if you want to integrate with any of these tools in a pipeline (such as KServe), you have to do a url.replace("minio://", "s3://") based on the artifact location.

Since multiple vendors exposes cloud storage with an S3 compatible API (IBM, Google Cloud) and you can use a reverse proxy such as gaul/s3proxy for those that doesn't, it doesn't make sense to distinguish between the underlying backend solution.

Is there a workaround currently?

• Use url.replace("minio://", "s3://") in pipelines.
• Close your eyes and don't worry about it 🙈 🙉 🙊

---

Love this idea? Give it a 👍.