docs/executors: remove outdated k8s-native same-node requirement#1820
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
burmudar
approved these changes
Jul 21, 2026
devdinu
approved these changes
Jul 21, 2026
Native Kubernetes executor Job pods no longer must be co-located on the same node as the Executor pod. That requirement was removed when the single-job-pod runtime (emptyDir workspaces) became the default, so Job pods now schedule across any node in the cluster. Remove the stale same-node scheduling guidance and the 110-pods-per-node note it implied. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
michaellzc
force-pushed
the
michaellzc/fix-docs
branch
from
July 21, 2026 17:01
06c855e to
fa80ed6
Compare
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
3 participants
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.
Native Kubernetes executor Job pods no longer need to be co-located on the same node as the Executor pod — that requirement was removed when the single-job-pod runtime (with
emptyDirworkspaces) became the default, so Job pods now schedule across any node in the cluster. This removes the stale same-node scheduling guidance (including thespec.nodeNameDownward API co-location example) from the deployment guide and the troubleshooting page, and drops the 110-pods-per-node note that only applied under the old co-location constraint. TheEXECUTOR_KUBERNETES_NODE_*env vars are now framed as optional scheduling constraints rather than a co-location requirement.🤖 Generated with Claude Code