periodic sync upstream KF to midstream ODH

.github/workflows/build-image-pr.yml

@@ -41,7 +41,6 @@ jobs:
       - name: Remove AppArmor profile for mysql in KinD on GHA # https://github.com/kubeflow/manifests/issues/2507
         run: |
           set -x
-          sudo apt-get install apparmor-profiles
           sudo apparmor_parser -R /etc/apparmor.d/usr.sbin.mysqld
       - name: Load Local Registry Test Image
         env:

.github/workflows/csi-test.yml

@@ -68,7 +68,6 @@ jobs:
       - name: Remove AppArmor profile for mysql in KinD on GHA # https://github.com/kubeflow/manifests/issues/2507
         run: |
           set -x
-          sudo apt-get install apparmor-profiles
           sudo apparmor_parser -R /etc/apparmor.d/usr.sbin.mysqld
 
       - name: Install kustomize

.github/workflows/first-time-contributor-pr.yml

@@ -0,0 +1,44 @@
+name: Welcome first-time contributors (Beta)
+on:
+  pull_request_target:
+    types:
+      - opened
+permissions:
+  issues: write
+  pull-requests: read
+
+# do NOT: add actions/checkout to this flow, add-third party scripts, or auto-trigger CI jobs
+# goal: this is meant to remind maintainers/approvers to add labels to ensure all tests are executed before merging
+# and avoid merging without realizing that required tests has not been run; complementary to bulletpoint in template: https://github.com/kubeflow/model-registry/blame/de5f225d96a4daeca77506d233082b1c4ea5afa3/.github/pull_request_template.md#L21
+jobs:
+  welcome:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check contributor status
+        uses: actions/github-script@v7
+        with:
+          script: |
+            const { data: pr } = await github.rest.pulls.get({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              pull_number: context.issue.number
+            });
+            const isFirstTimeContributor = pr.user.contributions === 0;
+            console.log(`First-time contributor status: ${isFirstTimeContributor}`);
+            return { isFirstTimeContributor };
+
+      - name: Log contributor status
+        run: echo "First-time contributor status is ${{ steps.check_author.outputs.isFirstTimeContributor }}"
+
+      # - name: Add a comment to the PR if first time contributor
+      #   if: steps.check_author.outputs.isFirstTimeContributor == 'true'
+      #   uses: actions/github-script@v7
+      #   with:
+      #     script: |
+      #       github.rest.issues.createComment({
+      #         issue_number: context.issue.number,
+      #         owner: context.repo.owner,
+      #         repo: context.repo.repo,
+      #         body: "Maintainers: let's ensure the label `ok-to-test` has been maintained and all the tests have been executed before merging.<br/><br/>Thank you for your first Pull Request! 🎉🎉"
+      #       })
+# do NOT: add actions/checkout to this flow, add-third party scripts, or auto-trigger CI jobs

.github/workflows/python-tests.yml

@@ -198,7 +198,6 @@ jobs:
       - name: Remove AppArmor profile for mysql in KinD on GHA # https://github.com/kubeflow/manifests/issues/2507
         run: |
           set -x
-          sudo apt-get install apparmor-profiles
           sudo apparmor_parser -R /etc/apparmor.d/usr.sbin.mysqld
       - name: Load Local Registry Test Image
         env:

.github/workflows/ui-bff-build.yml

@@ -9,7 +9,7 @@ on:
       - "!DOCKERFILE*"
       - "!**.gitignore"
       - "!**.md"
-  
+
   pull_request:
     paths:
       - "clients/ui/**"
@@ -27,16 +27,16 @@ jobs:
       - name: Setup Go
         uses: actions/setup-go@v5
         with:
-          go-version: "1.23.5"
+          go-version: "1.24.3"
 
       - name: Clean
         working-directory: clients/ui/bff
         run: make clean
 
       - name: Lint
-        uses: golangci/golangci-lint-action@v7
+        uses: golangci/golangci-lint-action@v8
         with:
-          version: v2.0.2
+          version: v2.1.0
           working-directory: clients/ui/bff/
 
       - name: Build

ADOPTERS.md

@@ -2,6 +2,11 @@
 
 Below are the adopters of the Model Registry project. If you are using Model Registry, please add your name to the list by submitting a pull request: this will help foster the Kubeflow community. Kindly ensure the list remains in alphabetical order.
 
-| Organization | Contact (GitHub User Name) | Environment | Description of Use |
-| ------------- | ------------- | ------------- | ------------- |
-| <company name here> | <your github handle here> | Production/Testing/Experimenting/etc | <any notes you'd like to share> |
+| Organization                  | Contact (GitHub User Name)                 | Environment                                | Description of Use                                                    |
+|-------------------------------|--------------------------------------------|--------------------------------------------|-----------------------------------------------------------------------|
+| [Pepsico](https://www.pepsico.com/) | [@milosjava](https://github.com/milosjava) | Experimenting  | Evaluating a transition from Azure Model Registry to Kubeflow Model Registry |
+| [Red Hat](https://www.redhat.com)          | [@rareddy](https://github.com/rareddy)| Production       |   Kubeflow Model Registry is part of [OpenShift AI](https://www.redhat.com/en/products/ai/openshift-ai) |
+| [INFN (National Institute for Nuclear Physics)](https://www.infn.it/en/) | [@mginfn](https://github.com/mginfn) | Experimenting  | Building a platform for running ML workflows |
+| [YIQISOFT](https://www.yiqisoft.com) | [@jiekechoo](https://github.com/jiekechoo) | Production | Model Registry is part of [YiAI](https://www.yiqisoft.cn/products/)|
+| [VMware](https://www.vmware.com) | [@tiansiyuan](https://github.com/tiansiyuan) | Testing | Model Registry is important for LLMs |
+| < company name here>           | < your github handle here >                  | <Production/Testing/Experimenting/etc>       | <any notes you'd like to share>                                       |

CONTRIBUTING.md

@@ -1,20 +1,26 @@
 # Kubeflow Contributor Guide
 
-Welcome to the Kubeflow project! We'd love to accept your patches and 
+Welcome to the Kubeflow Model Registry project! We'd love to accept your patches and 
 contributions to this project. Please read the 
 [contributor's guide in our docs](https://www.kubeflow.org/docs/about/contributing/).
 
-The contributor's guide
+The contributor's guide:
 
-* shows you where to find the Contributor License Agreement (CLA) that you need 
-  to sign,
-* helps you get started with your first contribution to Kubeflow,
-* and describes the pull request and review workflow in detail, including the
-  OWNERS files and automated workflow tool.
+* explains how to use the Developer Certificate of Origin (DCO) with git commit system
+  * like explained in [this guide](https://wiki.linuxfoundation.org/dco), or [this example](https://github.com/kubeflow/community/tree/master/dco-signoff-hook#signing-off-commits)
+* references the [Code of Conduct](https://www.kubeflow.org/docs/about/contributing/#follow-the-code-of-conduct)
+* helps you get started with your first contribution to Kubeflow
+  * like how to identify [good-first-issue](https://github.com/kubeflow/model-registry/labels/good%20first%20issue) tickets
+* and [describes](https://www.kubeflow.org/docs/about/contributing/#owners-files-and-pr-workflow) the pull request and review workflow in detail, including the
+  OWNERS files and automated workflow tool
+
+The [Kubeflow Community calendar](https://www.kubeflow.org/docs/about/community/#kubeflow-community-calendar) provides an overview of the community calls and specifically the bi-weekly Kubeflow Model Registry meeting.
 
 <hr/>
 
-This document focus on technical aspects while contributing to the Model Registry project
+The remainder of this document focuses on technical aspects while contributing to the Model Registry project specifically.
+
+The [Model Registry documentation](https://github.com/kubeflow/model-registry?tab=readme-ov-file#documentation-links) provides details about: what is a Model Registry, how to Install, logical model Concepts, how the MR python client works, Tutorials, FAQs and most importantly the [Technical References](https://github.com/kubeflow/model-registry?tab=readme-ov-file#documentation-links:~:text=FAQs-,Development,-introduction%20to%20local)!
 
 # Contributing to Model Registry using Apple-silicon/ARM-based computers
 

README.md

@@ -20,6 +20,7 @@ Model registry provides a central repository for model developers to store and m
 1. Introduction
  - [What is Kubeflow Model Registry](https://www.kubeflow.org/docs/components/model-registry/overview/)
  - [Blog KF 1.9 introducing Model Registry](https://blog.kubeflow.org/kubeflow-1.9-release/#model-registry)
+ - [Blog KF 1.10 introducing UI for Model Registry, CSI, and other features](https://blog.kubeflow.org/kubeflow-1.10-release/#model-registry)
 2. Installation
  - [installing Model Registry standalone](https://www.kubeflow.org/docs/components/model-registry/installation/#standalone-installation)
  - [installing Model Registry with Kubeflow manifests](https://github.com/kubeflow/manifests/tree/master/apps/model-registry/upstream#readme)

RELEASE.md

@@ -17,10 +17,10 @@ The Kubeflow Model Registry per governance of the Kubeflow Community, Kubeflow P
 
 The Release of the Kubeflow Model Registry provides:
 - a container image for the Backend; known as the "KF MR Go REST server"
-- a Python client to be used in Jupyter notebook, programmatically, or that can be integrated in the Kubeflow SDK; known as the "MR py client"
+- a Python client to be used in a Jupyter notebook, programmatically, or that can be integrated in the Kubeflow SDK; known as the "MR py client"
 - an optional Model Registry Custom Storage Initializer container image for KServe; the "Model Registry CSI"
-- a collection of Kubernetes Manifest, which get synchronized to the `kubeflow/manifests` repository
-- an update the the Kubeflow website
+- a collection of Kubernetes Manifests, which get synchronized to the `kubeflow/manifests` repository
+- an update to the Kubeflow website
 
 # Instructions
 

ROADMAP.md

@@ -0,0 +1,23 @@
+# Kubeflow Model Registry Roadmap
+
+## Overview
+
+The Kubeflow Model Registry project roadmap is tracked using [GitHub Milestones](https://github.com/kubeflow/model-registry/milestones), following the Kubeflow Release Team's request: this approach has been recommended in order to maintain a detailed view of all the items intended for upcoming Kubeflow releases, organized by "themes". The roadmap is continuously updated as we make progress towards a Kubeflow Release.
+
+## Current Roadmap
+
+The current roadmap and upcoming features are tracked in our [GitHub Milestones](https://github.com/kubeflow/model-registry/milestones). Each milestone tracks specific or future Kubeflow release and contains the planned features, enhancements, and bug fixes. For each milestone, a GitHub Issue is typically attached serving as a Tracker record to provide additional details.
+
+## Past Roadmaps
+
+- Model Registry in Kubeflow 1.10
+    - [Milestone](https://github.com/kubeflow/model-registry/milestone/1)
+    - [Tracker for details](https://github.com/kubeflow/model-registry/issues/175)
+- Model Registry in Kubeflow 1.9
+    - [Tracker for details](https://github.com/kubeflow/model-registry/issues/3)
+
+## See also
+
+For more information about contributing to this project including the roadmap, refer to our [CONTRIBUTING.md](./CONTRIBUTING.md) file.
+
+For more information about the release process, refer to our [RELEASE.md](./RELEASE.md) file.