Skip to content

fix: harden testing/ and developing scripts - #1285

Open
andyatmiami wants to merge 2 commits into
kubeflow:notebooks-v2from
andyatmiami:fix/sanity-check-wsk-samples
Open

fix: harden testing/ and developing scripts#1285
andyatmiami wants to merge 2 commits into
kubeflow:notebooks-v2from
andyatmiami:fix/sanity-check-wsk-samples

Conversation

@andyatmiami

@andyatmiami andyatmiami commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

ℹ️ NO GH ISSUE

Ran into a couple minor annoyances during PR reviews that would be nice to fix.

(1) When enabling PROMETHEUS in tilt - I got an error (likely a race condition) that kubectl wait ... pods failed because the pods hadn't been created yet... waiting on Prometheus CR to be Available seems the obvious hardening choice here.

(2) In reviewing #1263 - i had a typo in the PR "suggestion" I offered.. which lead to an extra whitespace and invalid YAML for our codeserver WSK that got carried into the author's fixes... and to make matters worse - all our GHA checks passed... Added a small/idempotent/trivial addition to sanity-check.sh that will reasonably catch regressions in our sample files - which seems aligned with the purpose of sanity-check.sh

The sanity-check script validates that all components are deployed and
responsive, but never validated the sample WorkspaceKind manifests.
This meant broken YAML or CRD schema regressions in sample files went
undetected by CI.

Add a new section that runs server-side dry-run validation against all
sample WorkspaceKind YAMLs, catching parse errors, schema violations,
and webhook rejections without creating any resources.

Signed-off-by: Andy Stoneberg <astonebe@redhat.com>
The pod readiness wait could fail with "no resources found" if the
Prometheus operator hadn't reconciled and created the pods yet. Add an
explicit wait for the Prometheus CR to reach Available before checking
pod readiness, giving the operator time to spawn the pods.

Signed-off-by: Andy Stoneberg <astonebe@redhat.com>
@github-project-automation github-project-automation Bot moved this to Needs Triage in Kubeflow Notebooks Jul 30, 2026
@google-oss-prow google-oss-prow Bot added the area/ci area - related to ci label Jul 30, 2026
@google-oss-prow

Copy link
Copy Markdown

[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 ask for approval from andyatmiami. 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:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@google-oss-prow google-oss-prow Bot added area/v2 area - version - kubeflow notebooks v2 size/S labels Jul 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/ci area - related to ci area/v2 area - version - kubeflow notebooks v2 lgtm size/S

Projects

Status: Needs Triage

Development

Successfully merging this pull request may close these issues.

2 participants