Repository navigation
Conversation
The jump pod could land on any node. On some clusters, e.g., Nebius, a NodePort is reachable only on the node that runs the pod, so the jump pod is unreachable if that node has no ExternalIP. Users may also want to keep the jump pod off GPU nodes. * proxy_jump.node_selector restricts the jump pod to labeled nodes. Items are key=value, key= (an empty value), or key (any value). As nodeSelector can't match any value, all items go into a single required node affinity term. * proxy_jump.tolerations items are key[=value][:effect], the kubectl taint format with an optional effect. Without a value, any value is tolerated; without an effect, any effect. An empty key, which would tolerate all taints, is rejected. * If tolerations is not set, GPU node taints are autodetected as before, unless node_selector is set, since autodetection considers all nodes, not only the selected ones. tolerations: [] turns autodetection off. Notes: * New values don't apply to an existing jump pod. The docs describe how to apply them with kubectl. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
The jump pod could land on any node. On some clusters, e.g., Nebius, a NodePort is reachable only on the node that runs the pod, so the jump pod is unreachable if that node has no ExternalIP. Users may also want to keep the jump pod off GPU nodes.
Notes: