Skip to content

fix(tracker/pod): report unschedulable pods instead of hanging - #402

Draft
ljluestc wants to merge 1 commit into
werf:mainfrom
ljluestc:fix/288-pod-unschedulable
Draft

ljluestc wants to merge 1 commit into
werf:mainfrom
ljluestc:fix/288-pod-unschedulable

Conversation

@ljluestc

Copy link
Copy Markdown

When a pod can't be scheduled (e.g. "0/1 nodes are available: 1 Insufficient memory."), its containers never start and the pod tracker waited silently until the timeout. Report the Unschedulable PodScheduled condition as a pod error, the same way ImagePullBackOff and CrashLoopBackOff are reported, so it is shown to the user and counted against the allowed failures.

Fixes #288

When a pod can't be scheduled (e.g. "0/1 nodes are available: 1
Insufficient memory."), its containers never start and the pod tracker
waited silently until the timeout. Report the Unschedulable PodScheduled
condition as a pod error, the same way ImagePullBackOff and
CrashLoopBackOff are reported, so it is shown to the user and counted
against the allowed failures.

Fixes werf#288
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Pod tracker hangs when there are problems with pod scheduling

1 participant