Refine legend wording related to arm64 node compatibility#31
Merged
nirmalsunny merged 2 commits intomainfrom Jun 30, 2025
Merged
Refine legend wording related to arm64 node compatibility#31nirmalsunny merged 2 commits intomainfrom
nirmalsunny merged 2 commits intomainfrom
Conversation
sm-powell
approved these changes
Jun 30, 2025
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
2 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.
Since we are checking whether an image can run on an arm64 node or not, I believe, "arm64 node compatible" makes more sense. Also "not arm64 node compatible" means that the image won't be scheduled on an arm64 node regardless of whether that image works on arm64 machine or not.