synchronize kubeflow workspaces manifests v2.0.0 alpha.1

[christian-heusel]

Pull Request Template for Kubeflow Manifests

✏️ Summary of Changes

Do the initial sync for the experimental notebooks v2 manifests.

• Update kubeflow/notebooks manifests from v2.0.0-alpha.0
• chore: Setup plumbing needed for notebooks-v2
• chore: Add sidebar link for notebooks-v2
• Update kubeflow/notebooks manifests from v2.0.0-alpha.1

📦 Dependencies

none

🐛 Related Issues

none

✅ 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.).

cc @andyatmiami @thesuperzapper

[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

[Copilot]

Pull request overview

This PR introduces the initial synchronization of experimental Kubernetes Notebook v2 manifests from the upstream kubeflow/notebooks repository at version v2.0.0-alpha.0. The PR includes a synchronization script, comprehensive controller/backend/frontend manifests with Istio integration, sample configurations, and a patch to add a notebooks-v2 entry to the central dashboard sidebar (currently commented out with a pre-GA warning).

Changes:

• Created a synchronization script (scripts/synchronize-notebooks-v2-manifests.sh) to automate future manifest updates
• Added complete experimental notebooks-v2 manifests (backend, frontend, controller) with Istio networking integration
• Included sample WorkspaceKind and Workspace resources demonstrating usage
• Added centraldashboard configuration patch to expose notebooks-v2 in the UI
• Updated example kustomization to document notebooks-v2 availability (with pre-GA warnings and commented out)

Reviewed changes

Copilot reviewed 76 out of 77 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
scripts/synchronize-notebooks-v2-manifests.sh	Script to automate synchronization of upstream notebooks-v2 manifests
experimental/notebooks-v2/kustomization.yaml	Root kustomization composing backend, controller, and frontend with image tag fixes
experimental/notebooks-v2/backend/	Backend service manifests with Istio overlay and RBAC configuration
experimental/notebooks-v2/controller/	Workspaces controller with CRDs, webhooks, and cert-manager integration
experimental/notebooks-v2/frontend/	Frontend UI deployment with Istio ingress routing
experimental/notebooks-v2/centraldashboard/	ConfigMap patch adding notebooks-v2 menu items to central dashboard
example/kustomization.yaml	Documentation comments for optional notebooks-v2 deployment

[thesuperzapper]

@christian-heusel I think the best structure is to keep everything under applications, in a folder called workspaces.

Structure should be:

applications:
  - workspaces:
       - upstream:
           - controller:
               - base, overlays, components, etc
           - backend:
               - base, overlays, components, etc
           - frontend:
               - base, overlays, components, etc
      - overlays:
           - istio:
               - xyz_patch.yaml (if needed can be included).
               - kustomization.yaml (points to the `overlays/istio` of each upstream)

Then we have a single sync target under upstream.

[christian-heusel]

/hold

[juliusvonkohout]

@christian-heusel please add a basic integration test, similar to 1. https://github.com/kubeflow/manifests/blob/master/.github/workflows/pipeline_run_from_notebook.yaml 2. https://github.com/kubeflow/manifests/blob/master/.github/workflows/notebook_controller_test.yaml 3. https://github.com/kubeflow/manifests/blob/master/.github/workflows/jupyter_web_application_test.yaml

[juliusvonkohout]

if you want you can also kill the notebooks v1 helm charts in this PR. Since we will kill v1 there is no potential to upstream them in the future.

[juliusvonkohout]

/retest
Maybe also @danish9039 can help.

[danish9039]

@christian-heusel failures here are a combination of the prerelease image-tag mismatch (v2.0.0-alpha.1 in manifests https://github.com/kubeflow/manifests/pull/3430/changes#diff-2145495ad76e99d7bebb590b3ab3c4fb6dec9b87f0092b3ff4c7adf9cd36311dR20 vs 2.0.0-alpha.1 in GHCR) plus stale workflow assumptions in the new tests

global all-namespaces pod wait that times out on unrelated KinD dependencies https://github.com/kubeflow/manifests/pull/3430/changes#diff-8b3cd760feec7fb87c30efb305a6f3031f13ede999a21dcf1aa2c7bc5a88e8acR51

should wait first for cert-manager pods and then for pods in the only in kubeflow-workspaces namespace

kubectl wait --for=condition=Ready pods -n cert-manager --all --timeout=120s
        kubectl wait --for=condition=Ready pods \
          -n kubeflow-workspaces --all \
          --timeout=600s

controller test hitting the old /workspaces/api/v1/namespaces/{ns}/workspaces route https://github.com/kubeflow/manifests/pull/3430/changes#diff-8b3cd760feec7fb87c30efb305a6f3031f13ede999a21dcf1aa2c7bc5a88e8acR76 instead of /workspaces/api/v1/workspaces/{ns}

pipeline test assuming the workspace pod is always named test-0 even though the controller now generates that name dynamically .https://github.com/kubeflow/manifests/pull/3430/changes#diff-0dbda89ab22f251a228374464802a7f6b04345db1a5292dcbbb8b264b876f255R84

i have fixed and validated the changes required ( see commits on my fork danish9039@d76d396 )