spark-operator: Update Notebooks integration to use Enterprise Gateway 3.3.0 defaults

[Ramneek-kalra]

Summary

Updates the Integration with Kubeflow Notebooks guide so the Jupyter Enterprise Gateway install matches current chart defaults and the latest release.

Fixes: #

Motivation

The current docs pin Jupyter Enterprise Gateway to 3.2.3 and ask readers to deploy with a custom values.yaml. That custom config, plus the PVC / hostPath kernelspecs mount path, caused real install friction: mounted kernelspecs were not detected reliably.

The Enterprise Gateway Helm chart already:

• Ships elyra/enterprise-gateway:3.3.0 and elyra/kernel-image-puller:3.3.0
• Includes spark_python_operator in kernel.allowedKernels
• Keeps kernelspecsPvc.enabled: false by default

So the docs should install with chart defaults and avoid recommending PVC-mounted kernelspecs for the common path.

Changes

• Bump Helm chart / image references from 3.2.3 → 3.3.0
• Replace the custom enterprise-gateway-helm.yaml install with the default chart install (no --values override)
• Optionally note --set kernel.defaultKernelName=spark_python_operator if readers want that kernel as default
• Remove (or clearly de-emphasize) the PVC / hostPath kernelspecs customization steps
• Point advanced customization to the upstream Jupyter Enterprise Gateway docs
• Correct the kernel name in the “what happens next” steps to spark_python_operator (was pyspark)

Test plan

• Preview the page locally (or via Netlify/preview if available) and confirm Step 1 shows only the default Helm install for v3.3.0
• Confirm there is no custom values YAML required for the happy path
• Confirm the PVC kernelspecs section is removed or marked as not recommended
• Confirm remaining download/image URLs use 3.3.0
• Confirm “select kernel” text uses spark_python_operator
• Manually verified Helm install against a cluster using chart defaults (optional but recommended):

helm upgrade --install enterprise-gateway \
  https://github.com/jupyter-server/enterprise_gateway/releases/download/v3.3.0/jupyter_enterprise_gateway_helm-3.3.0.tar.gz \
  --namespace enterprise-gateway \
  --create-namespace \
  --wait

[google-oss-prow]

Hi @Ramneek-kalra. Thanks for your PR.

I'm waiting for a kubeflow member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[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 yuchaoran2011 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:

• content/en/docs/components/spark-operator/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]

🚫 This command cannot be processed. Only organization members or owners can use the commands.

[Ramneek-kalra]

Hi @yuchaoran2011 — could you take a look when you have a chance, and /ok-to-test if this looks reasonable?

[github-actions]

🚫 This command cannot be processed. Only organization members or owners can use the commands.

[Arhell]

/ok-to-test