Repository navigation
[Kubernetes] Pin temporary bootstrap SkyPilot to 0.14.2 - #10
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
add(1, 2)returned3. Temporary controller and cluster resources were removed afterward.kubernetes.ports: podip.git diff --checkis clean.format.shcould not run becauseyapfis unavailable; this change touches only one Jinja template line. No new test file was added.