added fix for early exit if pod is restarted #4254
Open
+58
−10
Conversation
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
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
musab-mah-7
requested changes
Jan 23, 2026
jac-scale/jac_scale/targets/kubernetes/utils/kubernetes_utils.impl.jac
Outdated
Show resolved
Hide resolved
Collaborator
Author
|
@musab-mah-7 check_pods_restarted is implemented as utils function |
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
juzailmlwork
force-pushed
the
early-exit-if-container-is-restarted
branch
from
1e6010a to
a91a8f6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Description
previously deployment status was checked by check_deployment_status function which used to connect /docs multiple times till limit is reached.But this get stuck for 7.5 mins before mentioning error in deployment but now we can detect failure of deployment by identifying restarting of containers and throw error message (within 1.5 min)
this will fasten up the development and more robust in pipeline