Repository navigation
Schedule parallel catchup infra pods ahead of the workers - #448
Merged
dmkozh merged 3 commits intoOct 26, 2026
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
dmkozh
approved these changes
Oct 26, 2026
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Sets
priorityClassName: catchup-infraon the redis, preload and job monitor pods so the scheduler places them before the 1024 workers./statustimeout fired at 15:38:07preemptionPolicy: Never) comes from stellar/kube#5671. Merge that first and confirm it exists on ssc-eks and ssc-test, or every pod using it is rejectedTesting:
helm template: the 3 infra pods getcatchup-infra, workers noneNever, workers 0, all scheduled🤖 Generated with Claude Code