4 ms·
Ugh! Was the fix committed upstream?
by ngrilly 7y ago
Ugh! Was the fix committed upstream?
- ypcx 7y agoYes, this one was a systemd detection in runc, which was causing big log flooding and runtime overhead due to runc being executed so frequently. I initially cached the checks, but later the devs removed them altogether. Still, this is not solving the inefficiencies in k8s. https://github.com/kubernetes/kubernetes/issues/76531 https://github.com/kubernetes/kubernetes/issues/76531