Feature Area

/area backend
/area frontend

What is the use case or pain point?

Currently, KFP is using MinIO as the default object store for Artifact payload and Pipeline template. However, MinIO has fully changed its license to AGPLv3 since 2021. This change has prevented KFP from upgrading to the latest of MinIO: using AGPL software requires that anything it links to must also be licensed under the AGPL. Since we are not able to adopt the latest change from MinIO, we are seeking alternatives to replace it in future KFP deployment.

What feature would you like to see?

This new object store solution should have the following nature:

1. It is open sourced and uses license that can be accepted by KFP.
2. Orchestration engine (like Argoworkflow) can interact with this object store.
3. It is compatible with S3.
4. It has fine-grained permission control.
5. Same or similar function set with MinIO.

Exploration

We are currently considering following options, we would like to hear your opinions as well.

• https://www.zenko.io/cloudserver/
• https://longhorn.io/
• https://github.com/openstack/swift
• ceph-rook
• https://github.com/cubeFS/cubefs
• https://github.com/openebs/openebs

cc @chensun @IronPan @james-jwu

Love this idea? Give it a 👍. We prioritize fulfilling features with the most 👍.