Skip to content

[Kubernetes] Keep the upstream-supported client bound - #13

Merged
noobHappylife merged 1 commit into
ellm-0.12.0from
fix/kubernetes-client-compatibility
Nov 18, 2026
Merged

noobHappylife merged 1 commit into
ellm-0.12.0from
fix/kubernetes-client-compatibility

Conversation

@noobHappylife

@noobHappylife noobHappylife commented Nov 18, 2026 •

Copy link
Copy Markdown

Summary

Fresh API-server images resolve Kubernetes client 37.0.1. Its generated model type strings use Dict[str, str], which this fork's pod-config validator treats as a model name. Controller provisioning then repeatedly fails before creating a pod:

Invalid pod_config. Details: Validation error in metadata.labels:
No module named 'kubernetes.client.models.Dict[str, str]'

Use the same kubernetes<36.0.0 compatibility bound declared by upstream SkyPilot 0.14.2 and 0.14.3. Keep the existing exclusion of 32.0.0. This avoids changing the validator to accommodate an otherwise unqualified generated-client API.

Test plan

  • Reproduced the failure through the released SDK -> API-server image -> local kind launch path with client 37.0.1. No controller pod was created.
  • With only the client changed to 35.0.0, the same API server/config/task returned a service endpoint and a controller pod running with zero restarts. Used Kubernetes-only configuration, disabled cloud-storage uploads, and zero inference replicas.
  • The earlier native-controller qualification also used client 35.0.0. Its dependency environment differed from the freshly built API-server image; health/status checks alone did not catch that mismatch.
  • YAPF 0.32.0 and git diff --check passed. The unmodified .4 release image passed a fresh SDK -> API -> Kubernetes controller launch, all seven Ray bootstrap patches, controller readiness with zero restarts, and a real Ray remote task returning 3. Its API image resolves client 35.0.0. TokenVisor pins are updated to .4 for the next CI run.

@noobHappylife
noobHappylife merged commit 9a9d4db 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