Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
The new pod is stuck in CrashLoopBackOff #82512
It happened usually on static pods.
we found these clues.
For the general pods (not static pods), we did the same test. After the container 73c5497c78028 was running, kubelet got the second chance to update the pods (do syncPod)
So I think there is a race condition for the container creating, especially when the container is not started too quickly.
How about the following change ?
We try to find ContainerStatus whose state is not Exited.
@tedyu from the codes you change, i think the return parameter of function FindContainerStatusByName is
By the way, i think we have multiple ways to avoid this.
We need to determine which one is better