Skip to content

Kubernetes: add proxy_jump.image - #4510

Draft
andweng wants to merge 1 commit into
dstackai:masterfrom
andweng:kubernetes-proxy-jump-image
Draft

andweng wants to merge 1 commit into
dstackai:masterfrom
andweng:kubernetes-proxy-jump-image

Conversation

@andweng

@andweng andweng commented Nov 21, 2026

Copy link
Copy Markdown
Contributor

Closes #4508. A draft for discussing the use case in the issue first, as CONTRIBUTING asks.

The jump pod always runs testcontainers/sshd:1.3.0. proxy_jump.image sets another image, for clusters that only admit images from an internal registry or an approved base, that gate on vulnerability scans, or that need a specific SSH crypto policy on the hop every session goes through. It sits alongside cpu, memory, node_selector and tolerations (following #4451 and #4459).

  • models.py: KubernetesProxyJumpConfig.image. The default, JUMP_POD_DEFAULT_IMAGE, moves here next to the other jump pod defaults. The field's description states what the image must provide: sshd at /usr/sbin/sshd run as root, plus /bin/sh and ssh-keygen.
  • compute.py: _create_jump_pod_service_if_not_exists() takes the image (cluster.proxy_jump.image or JUMP_POD_DEFAULT_IMAGE).
  • compatibility/backends.py: image is excluded from requests when unset, so new clients keep working with older servers.
  • Docs: the jump pod section of concepts/backends.md, plus image in the "new values don't apply to an existing jump pod" warning, with the kubectl set image command.
  • Tests:
    • the ReplicaSet gets the configured image, and the default otherwise (checked in every existing jump pod test);
    • the compatibility exclude.

Checks:

  • ruff check and ruff format are clean.
  • The Kubernetes backend and compatibility tests pass (224).
  • The full suite passes: 5158 passed, 1549 skipped.
  • On a real cluster, with the same change applied as a local patch to 0.22.6: the jump pod ran an Ubuntu 24.04 image with a FIPS-validated OpenSSH, and dstack attach and ssh <run> worked through it. That image's ssh-keygen -A makes only ECDSA and RSA host keys in FIPS mode, which _get_jump_pod_commands() accepts.

🤖 Generated with Claude Code

The jump pod always ran testcontainers/sshd:1.3.0. proxy_jump.image sets
another image, e.g., one built on an approved base, from an internal
registry, or with a mandated SSH crypto policy. It defaults to the
current image and, like the other proxy_jump fields, is excluded from
requests when unset so new clients keep working with older servers.

Closes dstackai#4508
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.

[Feature]: Kubernetes: configurable jump pod image (proxy_jump.image)

1 participant