What you would like to be added?

Add Model Registry Client (https://github.com/kubeflow/model-registry/tree/main/clients/python)

to Kubeflow SDK (unified SDK)

There are two ways to achieve this that follow the guides in the Kubeflow SDK proposal

Approach 1 - Namespace package (PEP 420)

Suggested by @briangallagher
Convert the SDK to a namespace package.
This would mean removing the __init__.py file from kubeflow/python folder.

Any future installed packages that also meet the criteria of the kubeflow namespace are importable, instead of being a regular package (last-in, first-out) in terms of importance.

Approach 2 - Wrapped package

Create a model_registry package within the kubeflow SDK namespace, and then import Model Registry.

I prefer this approach because then in the future, additional KF SDK specific things can be done and can be wrapped around in this fashion. It also will not require Model Registry to change its import statements which could confuse users and possibly break other workflows

Open to other ideas.

Why is this needed?

Start migration process of unified (hybrid) SDK and to meet expectations set in original SDK proposal.

Love this feature?

Give it a 👍 We prioritize the features with most 👍