Enable model-registry with UI by default

[juliusvonkohout]

Validation Checklist

• I confirm that this is a Kubeflow-related issue.
• I am reporting this in the appropriate repository.
• I have followed the Kubeflow installation guidelines.
• The issue report is detailed and includes version numbers where applicable.
• This issue pertains to Kubeflow development.
• I am available to work on this issue.
• You can join the CNCF Slack and access our meetings at the Kubeflow Community website. Our channel on the CNCF Slack is here #kubeflow-platform.

Version

master

Detailed Description

@tarilabs @lucferbux

Steps to Reproduce

Install Kubeflow

Screenshots or Videos (Optional)

No response

[madmecodes]

Made the required PR for the same #3048

[juliusvonkohout]

I think spark i still missing from https://github.com/kubeflow/manifests#kubeflow-components-versions and https://github.com/kubeflow/manifests/blob/master/example/kustomization.yaml. That might be something for @kunal-511

[juliusvonkohout]

Model registry depends on @tarilabs. Is there any way we can help you with the UI?
@kunal-511 but you can enable the model-registry backend already in a new PR.

[juliusvonkohout]

see also kubeflow/hub#863 (comment)
"I think we've had some consensus on kubeflow/hub#863 (comment), but the teams are currently busy on other fronts. We could sync on it at the biweekly meeting."

[juliusvonkohout]

Spark operator is there by default, model registry is missing

[Raakshass]

Hi @juliusvonkohout, thanks for raising this.

I’d like to work on enabling model-registry (including the UI) by default in kubeflow/manifests.
Plan:

1. Identify the existing model-registry manifests/overlays in this repo and the current default install entrypoint (example/).
2. Make the minimal kustomize change to include model-registry in the default “example” install flow.
3. Validate on a local Kind cluster and document any required prerequisites/notes.

If this direction looks correct, could you please confirm this is the preferred approach (and optionally assign/mark me as working on it) so we avoid duplicate efforts?

[juliusvonkohout]

Hi @juliusvonkohout, thanks for raising this.

I’d like to work on enabling model-registry (including the UI) by default in kubeflow/manifests. Plan:

1. Identify the existing model-registry manifests/overlays in this repo and the current default install entrypoint (example/).

2. Make the minimal kustomize change to include model-registry in the default “example” install flow.

3. Validate on a local Kind cluster and document any required prerequisites/notes.

If this direction looks correct, could you please confirm this is the preferred approach (and optionally assign/mark me as working on it) so we avoid duplicate efforts?

Please check all the issues linked here, which also point to the model registry repository to understand the full picture. You can also align on Slack in the model registry channel. But yes, feel free to raise a PR and explore.