Is the shared-storage model in Harbor a limitation for CSPs?

[matofeder]

Community,

With this thread, I would like to discuss and get your opinion about the open question:

Is the shared-storage model in Harbor a limitation for CSPs in the case of a single multi-tenant Harbor instance, that is shared between CSP's users?

Use case:
As a CSP I would like to offer a container registry as-a-service solution based on Harbor. I want to
use a single multi-tenant capable Harbor instance which will be shared between users (tenants), i.e. I want to create a dedicated Harbor project (tenant) per user.

Background:
Harbor by design uses a shared storage layer. It means that the storage of container images is shared even when the Harbor instance serves multiple tenants. The same approach is used e.g. by Red Hat Quay.
A different approach is implemented in Keppel. Keppel uses multi-tenant-aware storage drivers instead so that each customer gets their own separate storage backend.

See the Harbor architecture taken from docs:

CSP's opinion on that is highly appreciated (but of course, this discussion is not limited only to CSPs, and any insights/comments are welcomed)