- GCE/Windows: When the service cannot be stopped Stackdriver logging processes are now force killed ([#77378](https://github.com/kubernetes/kubernetes/pull/77378), [@yujuhong](https://github.com/yujuhong))

kicks-ass.net
kicks-ass.org
kids
kids.us
kiengiang.vn
kiev.ua
kiho.mie.jp
kihoku.ehime.jp
kijo.miyazaki.jp
kikirara.jp
kikonai.hokkaido.jp
kikuchi.kumamoto.jp
kikugawa.shizuoka.jp
kill.jp
kilo.jp
kim
kim.replit.dev
kimino.wakayama.jp
kimitsu.chiba.jp
kimobetsu.hokkaido.jp
kin.okinawa.jp
kindle
kinghost.net
kinko.kagoshima.jp
kinokawa.wakayama.jp

- Pod will not start when Init container was OOM killed. ([#104650](https://github.com/kubernetes/kubernetes/pull/104650), [@yxxhero](https://github.com/yxxhero)) [SIG Node]

  * Kubernetes now shares a single PID namespace among all containers in a pod when running with docker >= 1.13.1. This means processes can now signal processes in other containers in a pod, but it also means that the `kubectl exec {pod} kill 1` pattern will cause the Pod to be restarted rather than a single container. ([#45236](https://github.com/kubernetes/kubernetes/pull/45236), [@verb](https://github.com/verb))

* Fix API Server potential memory leak issue in processing watch request. ([#85410](https://github.com/kubernetes/kubernetes/pull/85410), [@answer1991](https://github.com/answer1991))
* Verify kubelet & kube-proxy can recover after being killed on Windows nodes ([#84886](https://github.com/kubernetes/kubernetes/pull/84886), [@YangLu1031](https://github.com/YangLu1031))

- Change the calculation of pod UIDs so that static pods get a unique value - will cause all containers to be killed and recreated after in-place upgrade. ([#87461](https://github.com/kubernetes/kubernetes/pull/87461), [@bboreham](https://github.com/bboreham)) [SIG Node]

kicks-ass.net
kicks-ass.org
kids
kids.us
kiengiang.vn
kiev.ua
kiho.mie.jp
kihoku.ehime.jp
kijo.miyazaki.jp
kikirara.jp
kikonai.hokkaido.jp
kikuchi.kumamoto.jp
kikugawa.shizuoka.jp
kill.jp
kilo.jp
kim
kim.replit.dev
kimino.wakayama.jp
kimitsu.chiba.jp
kimobetsu.hokkaido.jp
kin.okinawa.jp
kindle
kinghost.net
kinko.kagoshima.jp
kinokawa.wakayama.jp

- Fix detection of image filesystem, disk metrics for devicemapper, detection of OOM Kills on 5.0+ linux kernels. ([#92919](https://github.com/kubernetes/kubernetes/pull/92919), [@dashpole](https://github.com/dashpole)) [SIG API Machinery, CLI, Cloud Provider, Cluster Lifecycle, Instrumentation and Node]

- The slow initialization of container runtime will not cause System WatchDog to kill kubelet. Device Manager is not considered healthy before it attempted to start listening on the port. ([#135208](https://github.com/kubernetes/kubernetes/pull/135208), [@SergeyKanzhelev](https://github.com/SergeyKanzhelev)) [SIG Node]

girly.jp
gloomy.jp
gonna.jp
greater.jp
hacca.jp
heavy.jp
her.jp
hiho.jp
hippy.jp
holy.jp
hungry.jp
icurus.jp
itigo.jp
jellybean.jp
kikirara.jp
kill.jp
kilo.jp
kuron.jp
littlestar.jp
lolipopmc.jp
lolitapunk.jp
lomo.jp
lovepop.jp
lovesick.jp
main.jp
mods.jp
mond.jp
mongolian.jp
moo.jp
namaste.jp