Fix podstatus issue caused by docker's resource temporarily unavailable issue #4376
+20
−12
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.
Fix #4188. I tested this PR by pushing it to a running cluster with heavy load (300 pods on 4 nodes)
$ ./cluster/kubectl.sh get pods -l app=hostnames | awk '{print $(NF-2)}' | sort | uniq -c
Project: golden-system-455
Zone: us-central1-b
Running: ./cluster/../cluster/gce/../../_output/dockerized/bin/linux/amd64/kubectl get pods -l app=hostnames
1 HOST
110 kubernetes-minion-1.c.golden-system-455.internal/130.211.172.228
113 kubernetes-minion-2.c.golden-system-455.internal/104.154.62.162
62 kubernetes-minion-3.c.golden-system-455.internal/104.154.62.20
15 kubernetes-minion-4.c.golden-system-455.internal/104.154.55.124
And periodically checking podstatus of all pods for a couple of hours, and there is no flaps among Running, Pending and Unknown anymore: