ci: check k8s scheduling rejection sample#42
Closed
mdheller wants to merge 1 commit into
Closed
Conversation
Member
Author
|
Superseded by current-main replay Merged replacement commit: The replacement preserves the CI-only K8s scheduling sample check on current main. Closing this stale PR to avoid duplicate open work. |
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
1 participant
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.
Summary
Adds explicit runtime CI coverage for the standards-side K8s scheduling rejection sample.
Changed
k8s-shapecheckworkflow jobk8s/tools/check_scheduling.pyagainst the positive KubeEdge toleration fixtureWhy
The standards repo now contains a focused scheduling checker and positive/negative KubeEdge toleration fixtures. Runtime CI should explicitly exercise both sides of that contract.
Scope
CI-only. No command behavior changes.