[TASK] Migrate kubeflow/kubeflow pvcviewer_controller_docker_publish.yaml GitHub Action to kubeflow/notebooks - notebooks-v1 branch

[liavweiss]

Certification

• I certify I am an Epic Owner for Kubeflow Notebooks 2.0 and expected to create planning-related issues.

Description

Context:
kubeflow/notebooks was "split out" from the legacy kubeflow/kubeflow repository. The migration to kubeflow/notebooks is only partially complete - as the GitHub Actions to publish relevant components has not been migrated yet.

Details:

• Copy the workflow file pvcviewer_controller_docker_publish.yaml from the kubeflow/kubeflow/.github/workflows directory into the kubeflow/notebooks/.github/workflows directory.
• Update iamge names within the workflow (e.g., ghcr.io/kubeflow/kubeflow → ghcr.io/kubeflow/notebooks) to ensure publishing actions target the correct repo.
• Verify that paths, Docker image names, and triggers align with the new repo’s structure and CI/CD conventions.
• Test the migrated workflow by triggering it in a PR to kubeflow/notebooks.
  • developer should have a fork of kubeflow/notebooks that demonstrates the GitHub Action operates as intended
  • note that to successfully verify the publish functionality from a fork - some custom modifications will need to be made that should NOT appear in the PR opened against the upstream. publish-from-fork.pdf

Acceptance Criteria

• Workflow runs successfully in kubeflow/notebooks.
• Repository references and image publishing targets are correct

[liavweiss]

/area v1

[noalimoy]

/assign