[teraslice] fix serial job starts in kubernetesV2 #3867
Merged
Conversation
This file contains 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
bump: (patch) @terascope/[email protected], @terascope/[email protected] bump: (patch) @terascope/[email protected], [email protected] bump: (patch) @terascope/[email protected], [email protected] bump: (patch) @terascope/[email protected], @terascope/[email protected] bump: (patch) @terascope/[email protected], [email protected] bump: (patch) [email protected], [email protected]
busma13
force-pushed
the
k8sV2-fix-serial-job-starts
branch
from
444b3bf to
6d48aec
Compare
godber
approved these changes
Dec 10, 2024
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.
This PR makes the following changes:
k8s.waitForSelectedPod()inallocateWorkers(), which was waiting for the executionController readiness probe to be ready before creating a worker deployment.podIPfromallocateSlicer()as it is not needed since we now connect to the executionController using a kubernetes service.ref: #3868