[pod-sweeper] Skip Pending pods that haven't started yet #332
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.
What
Solves issue:
How
Some pods might be in
Pending
status when sweep-pod.sh is runningget_job_pods
In shell session below you can see how statuses and dates may change
Extra condition skips pods that haven't started yet. Pod might be longer in
Pending
state e.g. when it is necessary to spawn new Kubernetes node to run that pod.Recommended reading order
charts/airbyte-pod-sweeper/templates/configmap.yaml
Can this PR be safely reverted and rolled back?