mirror of
https://github.com/kubernetes/kubernetes.git
synced 2026-05-14 18:09:28 -04:00
a138a4825e
The test starts the kubelet with a non-default setting for idsPerPod, runs a pod, deletes it, and then restarts the kubelet. The issue is that the kubelet guarantees that no two pods userns mappings overlap (for security reasons). But we are not waiting for the pod to be removed, the deleteSync() call only waits for the API server to remove the pod. So, the pod is on disk (and maybe even running!) when we restart the kubelet. As the previous configuration is incompatible with the new one after restart if pods are running, the kubelet failing is the right thing. We should just wait for the pod to be deleted from the kubelet too, before restarting it with an incompatible configuration. So, this commit just changes the pod deleteion (before done in e2eoutput.TestContainerOutput() just waiting for the API server) to wait for the kubelet to delete the pod. Signed-off-by: Rodrigo Campos <rodrigo@amutable.com> |
||
|---|---|---|
| .. | ||
| cmd | ||
| compatibility_lifecycle | ||
| conformance | ||
| e2e | ||
| e2e_dra | ||
| e2e_kubeadm | ||
| e2e_node | ||
| fixtures | ||
| fuzz | ||
| images | ||
| instrumentation | ||
| integration | ||
| kubemark | ||
| list | ||
| soak/serve_hostnames | ||
| typecheck | ||
| utils | ||
| OWNERS | ||