Skip to content

[Kubernetes] Pin temporary bootstrap SkyPilot to 0.14.2 - #10

Merged
noobHappylife merged 1 commit into
ellm-0.12.0from
fix/k8s-bootstrap-skypilot-pin
Nov 18, 2026
Merged

noobHappylife merged 1 commit into
ellm-0.12.0from
fix/k8s-bootstrap-skypilot-pin

Conversation

@noobHappylife

Copy link
Copy Markdown

Summary

Pin the temporary Kubernetes bootstrap install to skypilot[kubernetes,remote]==0.14.2. The unpinned install now selects 0.14.3, whose Ray patches target 2.56.1 and fail against this fork’s Ray 2.9.3 before the uploaded fork wheel can be installed.

0.14.2 retains compatible patches. The normal fork-wheel installation still follows bootstrap. No Ray upgrade or release artifact change is included.

Refs #9.

Test plan

  • Qualified a fresh CPU-only SkyServe controller on local kind using pod-IP port mode and zero inference replicas. The native server up/status calls completed; the controller pod was ready with zero restarts.
  • Confirmed all seven bootstrap Ray patches applied, the source-built fork wheel installed afterward, and Ray remained 2.9.3. The installed template matched the modified source by SHA-256.
  • A real Ray remote add(1, 2) returned 3. Temporary controller and cluster resources were removed afterward.
  • To repeat: launch a fresh Kubernetes SkyServe controller from this branch, check its bootstrap logs and installed Ray version, then tear it down. For kind without an external LoadBalancer, set kubernetes.ports: podip.
  • git diff --check is clean. format.sh could not run because yapf is unavailable; this change touches only one Jinja template line. No new test file was added.

@noobHappylife
noobHappylife merged commit 6393c64 into ellm-0.12.0 Nov 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant