mirror of
https://github.com/kubernetes/kubernetes.git
synced 2026-05-23 10:29:27 -04:00
f692e4e8f0
In some (all?) CI jobs the initial kubelet instance keeps running, despite command context cancellation. Not reproducible locally, so additional output was necessary to track down the root cause in CI runs: signal propagation via sudo didn't work for kube-proxy and kubelet, but only for those two and only in the CI. The fix is to change the CI jobs so that they disable the usage of sudo. While at it, simplify by replacing atomic.Pointer with atomic.Boole. |
||
|---|---|---|
| .. | ||
| cmd | ||
| compatibility_lifecycle | ||
| conformance | ||
| e2e | ||
| e2e_dra | ||
| e2e_kubeadm | ||
| e2e_node | ||
| fixtures | ||
| fuzz | ||
| images | ||
| instrumentation | ||
| integration | ||
| kubemark | ||
| list | ||
| soak/serve_hostnames | ||
| typecheck | ||
| utils | ||
| OWNERS | ||