Enable model-registry with UI by default

[Raakshass]

Summary of Changes

This change enables the model-registry server and UI components in the default Kubeflow installation (example/kustomization.yaml).

Components added:

• Model Registry Server with PostgreSQL database (overlays/postgres)
• Model Registry UI with Istio networking (options/ui/overlays/istio)

This implementation follows the same pattern used for enabling Spark Operator in PR #3131, ensuring consistency with existing Kubeflow component integrations.

Dependencies

No external dependencies. This PR uses existing upstream manifests from applications/model-registry/ that are already present in the repository.

Related Issues

Closes #3047

This resolves the long-standing request to enable model-registry by default. The Spark Operator portion of the original issue was completed in PR #3131, and this PR completes the model-registry portion.

Contributor Checklist

• I have tested these changes with kustomize. See Installation Prerequisites.
• All commits are signed-off to satisfy the DCO check.
• I have considered adding my company to the adopters page to support Kubeflow and help the community, since I expect help from the community for my issue (see 1. and 2.).

---

Additional Context:

This PR adds only 5 lines to example/kustomization.yaml (plus comments), making it a minimal and focused change. The selected overlays (postgres for the server and istio for the UI) are specifically designed for Kubeflow deployments and include proper Istio integration for authentication and networking.

---

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.

[google-oss-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign kimwnasptd for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[github-actions]

Welcome to the Kubeflow Manifests Repository

Thanks for opening your first PR. Your contribution means a lot to the Kubeflow community.

Before making more PRs:
Please ensure your PR follows our Contributing Guide.
Please also be aware that many components are synchronizes from upstream via the scripts in /scripts.
So in some cases you have to fix the problem in the upstream repositories first, but you can use a PR against kubeflow/manifests to test the platform integration.

Community Resources:

• CNCF Slack channels: https://www.kubeflow.org/docs/about/community/#kubeflow-slack-channels
• Community meetings: https://www.kubeflow.org/docs/about/community/

Thanks again for helping to improve Kubeflow.

[Raakshass]

hey @juliusvonkohout can you just review this pr.
Thank you

[juliusvonkohout]

hey @juliusvonkohout can you just review this pr. Thank you

I am still on vacation, but maybe @tarilabs can help sooner.

Are you sure that the catalog and everything is properly exposed in the dashboard UI @Raakshass? Do you mind sharing screenshots? Think of how we expose Kserve models web application in the dashboard.

[juliusvonkohout]

@Raakshass are you sure that it is properly exposed similar to the kserve models web application (endpoints) in the dashboard UI? I would like to see screenshots of the dashboard and the actual UI changes you made. Please check the original issue and related ones in the Model-Registry git repository. I think you are missing 80% of the work.

[tarilabs]

could you kindly share screenshot with @ederign as Julius suggested please on this thread?

[juliusvonkohout]

That is the upstream folder that will be automatically overwritten. Please use an overlay such as https://github.com/kubeflow/manifests/blob/7f88e4f9ffac06d897916644f63d5ad24924b123/applications/centraldashboard/overlays/oauth2-proxy/kustomization.yaml

[Raakshass]

sure julius!

[sameerdattav]

Hey @ederign @juliusvonkohout @tarilabs,

I’ve been following this PR and the related issue for a few days and thought I could jump in to help move things forward.
So I went ahead and opened a fresh PR that includes all the required changes along with validation screenshots:

#3323

I’d really appreciate a review when you get a chance. Thanks!

[ederign]

I've commented on #3323

[Raakshass]

Hi @juliusvonkohout @tarilabs — addressing the feedback about showing the actual dashboard/UI change.

What changed in this update

• Added a Central Dashboard overlay: applications/centraldashboard/overlays/model-registry/
• Added a JSON6902 patch that appends a new dashboard menu entry pointing to /model-registry/
  • Value added: {"text": "Model Registry", "link": "/model-registry/"}

Why this change

Kubeflow’s documentation for Model Registry installation and dashboard customization indicates the Model Registry entry should be added to the Central Dashboard configuration so it appears in the sidebar menu.

Verification status

• This PR is focused on manifests wiring (dashboard link + overlays).
• Local end-to-end screenshots are still pending; will follow up with real deployment verification + screenshots once the deployment environment is ready.

If you’d like the menu item to also include type/icon fields (as in the docs examples), please confirm the preferred values and I can update it accordingly.

[juliusvonkohout]

I think you can use a general named one called applications/centraldashboard/overlays/kustomization.yaml

We should also merge https://github.com/kubeflow/manifests/blob/master/applications/centraldashboard/overlays/oauth2-proxy/kustomization.yaml into that because oauth2-proxy is anyway mandatory.

[Raakshass]

@juliusvonkohout Refactor complete!
I've consolidated the oauth2-proxy and model-registry overlays into a single applications/centraldashboard/overlays/kustomization.yaml as requested. Also switched to a Strategic Merge Patch to fix the JSON syntax error.

Dashboard link is verified locally (screenshot attached).