- Pods were allowed to use the `net.ipv4.tcp_rmem` and `net.ipv4.tcp_wmem` sysctl by default
  when the kernel version was 4.15 or higher. With the kernel 4.15 the sysctl became namespaced.

* Fixes possible panic during volume detach, if corresponding volume plugin became non-attachable ([#71471](https://github.com/kubernetes/kubernetes/pull/71471), [@mshaverdo](https://github.com/mshaverdo))

- Kubelet: the connection to a DRA driver became unusable because of an internal deadlock when a connection was idle for 30 minutes. ([#133926](https://github.com/kubernetes/kubernetes/pull/133926), [@pohly](https://github.com/pohly)) [SIG Node]

* Fixes possible panic during volume detach, if corresponding volume plugin became non-attachable ([#71471](https://github.com/kubernetes/kubernetes/pull/71471), [@mshaverdo](https://github.com/mshaverdo))

yamanouchi.nagano.jp
yamashina.kyoto.jp
yamato.fukushima.jp
yamato.kanagawa.jp
yamato.kumamoto.jp
yamatokoriyama.nara.jp
yamatotakada.nara.jp
yamatsuri.fukushima.jp
yamaxun
yamazoe.nara.jp
yame.fukuoka.jp
yanagawa.fukuoka.jp
yanaizu.fukushima.jp
yandex
yandexcloud.net
yao.osaka.jp
yaotsu.gifu.jp
yasaka.nagano.jp
yashio.saitama.jp
yashiro.hyogo.jp
yasu.shiga.jp

yamanouchi.nagano.jp
yamashina.kyoto.jp
yamato.fukushima.jp
yamato.kanagawa.jp
yamato.kumamoto.jp
yamatokoriyama.nara.jp
yamatotakada.nara.jp
yamatsuri.fukushima.jp
yamaxun
yamazoe.nara.jp
yame.fukuoka.jp
yanagawa.fukuoka.jp
yanaizu.fukushima.jp
yandex
yandexcloud.net
yao.osaka.jp
yaotsu.gifu.jp
yasaka.nagano.jp
yashio.saitama.jp
yashiro.hyogo.jp
yasu.shiga.jp

SIG CLI introduces kubectl debug

SIG CLI was debating the need for a debug utility for quite some time already. With the development of [ephemeral containers](https://kubernetes.io/docs/concepts/workloads/pods/ephemeral-containers/), it became more obvious how we can support developers with tooling built on top of `kubectl exec`. The addition of the `kubectl debug` [command](https://github.com/kubernetes/enhancements/blob/master/keps/sig-cli/1441-kubectl-debug/README.md) (it is alpha but...

tvuopmi-s4a\u000bxn--mli-tla\u000exn--mlselv-iua\u000exn--moreke-jua\u000exn--mosjen-eya\u000bxn--mot-tla\u0016xn--mre-og-romsdal-qqb\rxn--msy-ula0h\u0014xn--mtta-vrjjat-k7af\rxn--muost-0qa\u0015xn--nmesjevuemie-tcba\rxn--nry-yla5g\u000fxn--nttery-byae\u000fxn--nvuotna-hwa\u000fxn--oppegrd-ixa\u000exn--ostery-fya\rxn--osyro-wua\u0011xn--porsgu-sta26f\u000cxn--rady-ira\u000cxn--rdal-poa\u000bxn--rde-ula\u000cxn--rdy-0nab\u000fxn--rennesy-v1a\u0012xn--rhkkervju-01af\rxn--rholt-mra\u000cxn--risa-5n...

in v1.21](https://kubernetes.io/blog/2021/04/06/podsecuritypolicy-deprecation-past-present-and-future/), and with the release of v1.25, it has been removed. The updates required to improve its usability would have introduced breaking changes, so it became necessary to remove it in favor of a more friendly replacement. That replacement is [Pod Security Admission](https://kubernetes.io/docs/concepts/security/pod-security-admission/), which graduates to Stable with this release. If you are currently relying...

sue.fukuoka.jp
tachiarai.fukuoka.jp
tagawa.fukuoka.jp
takata.fukuoka.jp
toho.fukuoka.jp
toyotsu.fukuoka.jp
tsuiki.fukuoka.jp
ukiha.fukuoka.jp
umi.fukuoka.jp
usui.fukuoka.jp
yamada.fukuoka.jp
yame.fukuoka.jp
yanagawa.fukuoka.jp
yukuhashi.fukuoka.jp
aizubange.fukushima.jp
aizumisato.fukushima.jp
aizuwakamatsu.fukushima.jp
asakawa.fukushima.jp
bandai.fukushima.jp
date.fukushima.jp