Dashboard Components Transfer

[milinddethe15]

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

I have created a new branch in my fork (https://github.com/milinddethe15/dashboard/tree/only-components) to isolate the dashboard components.
It contains only the following directories under /components:

• access-management
• admission-webhook
• centraldashboard
• centraldashboard-angular
• profile-controller

Steps to Reproduce

1. Using git-filter-repo I have kept only the specified components:

git-filter-repo \
  --path components/access-management \
  --path components/admission-webhook \
  --path components/centraldashboard \
  --path components/centraldashboard-angular \
  --path components/profile-controller \
  --force

2. The commit PR (#xxx) suffix in the new repo should be rewritten as (kubeflow/kubeflow#xxx) so we don't break the links

To re write the commit msg:

git filter-repo --message-callback 'import re; return re.sub(rb"\(#(\d+)\)", rb"(kubeflow/kubeflow#\1)", message)'

Screenshots or Videos (Optional)

No response

[milinddethe15]

Any updates on this?
@thesuperzapper @juliusvonkohout

[thesuperzapper]

I have moved the commits (including some newer ones from the 1.10 release) to kubeflow/dashboard under a commit called "Move commits from kubeflow/kubeflow".

Next Steps:

1. Set up the release process on the kubeflow/dashboard repo:
   • including a modified releasing/ script folder, along with any .github/workflows/ for the now migrated components from the old kubeflow/kubeflow repo
   • Note, we will push to the same ghcr.io container registries even from the new kubeflow/dashboard repo.
   • Since we don't want to actually do a release of 1.11 right now (and any 1.10 releases will be done from kubeflow/kubeflow), we should verify our workflows on a fork.
2. Once we are happy that it's possible to cut 1.11 (when the time comes) we can raise a PR to remove the dashboard workflows and code from the kubeflow/kubeflow.
3. We need to re-raise any important dashboard-related PRs from kubeflow/kubeflow, either by asking their authors, or making new ones.

I know that @milinddethe15 @ederign @Al-Pragliola @andyatmiami mentioned they wanted to help with this effort, we should discuss who will do what so we don't duplicate effort.

fyi @andreyvelich @juliusvonkohout

[milinddethe15]

List of Dashboard related github workflows from kubeflow/kubeflow:

• centraldashboard-angular
  • .github/workflows/centraldb_angular_backend_test.yaml
  • .github/workflows/centraldb_angular_docker_publish.yaml
  • .github/workflows/centraldb_angular_frontend_test.yaml
  • .github/workflows/centraldb_angular_intergration_test.yaml
• centraldashboard
  • .github/workflows/centraldb_docker_publish.yaml
  • .github/workflows/centraldb_frontend_tests.yaml
  • .github/workflows/centraldb_intergration_test.yaml
  • .github/workflows/centraldb_multi_arch_test.yaml
• access-management
  • .github/workflows/kfam_docker_publish.yaml
  • .github/workflows/kfam_multi_arch_test.yaml
• admission-webhook
  • .github/workflows/poddefaults_docker_publish.yaml
  • .github/workflows/poddefaults_intergration_test.yaml
  • .github/workflows/poddefaults_multi_arch_test.yaml
  • .github/workflows/poddefaults_unit_test.yaml
• profile-controller
  • .github/workflows/prof_controller_docker_publish.yaml
  • .github/workflows/prof_controller_multi_arch_test.yaml
  • .github/workflows/prof_controller_unit_test.yaml
  • .github/workflows/profiles_kfam_intergration_test.yaml

Dependency: components/testing/gh-actions

[andreyvelich]

Thanks for enumerating this @milinddethe15 !
Shall we distribute the work for every project between contributors @milinddethe15 @ederign @Al-Pragliola @andyatmiami ?

[milinddethe15]

There is already an ongoing discussion: https://cloud-native.slack.com/archives/C073W562HFY/p1744583750155469