Add NUMA-aware scheduling in GKE clusters (enabled for G4)#4760
Merged
kadupoornima merged 1 commit intoOct 14, 2025
Conversation
Contributor
Author
|
Triggered tests with the babysit tool. |
SwarnaBharathiMantena
approved these changes
Oct 14, 2025
SwarnaBharathiMantena
left a comment
Contributor
There was a problem hiding this comment.
LGTM. Please re-run the failed tests.
f4bef28
into
GoogleCloudPlatform:develop
23 of 63 checks passed
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.
Added support for enabling NUMA-aware scheduling in GKE clusters. Currently required and added for G4 NPI.
Reference: https://cloud.google.com/kubernetes-engine/distributed-cloud/bare-metal/docs/vm-runtime/numa#numa_nodes
TF support for this has been provided from 7.2 onwards, so provider versions have been updated in a previous PR accordingly.
make tests pass. Tested for G4 GKE, manual cluster creation successful. kubelet config for node shows correct options set.