Skip to content

K
k3s
Commit 75ad7460 authored by Dan Williams's avatar Dan Williams
Browse files
Options

Update CHANGELOG.md to note node readiness after #43474

parent 05c046f6
Hide whitespace changes
Inline Side-by-side
Showing with 9 additions and 0 deletions
CHANGELOG.md
View file @ 75ad7460
...@@ -642,6 +642,15 @@ Anyway, the cluster should get back to the proper size after 10 min. ...@@ -642,6 +642,15 @@ Anyway, the cluster should get back to the proper size after 10 min.
the new CRI + CNI code path. the new CRI + CNI code path.
* If you are using plugins other than `bridge`, make sure you have * If you are using plugins other than `bridge`, make sure you have
updated custom plugins to the latest version that is compatible. updated custom plugins to the latest version that is compatible.
* **CNI plugins now affect node readiness**
* Kubelet will now block node readiness until a CNI configuration file is
present in `/etc/cni/net.d` or a given custom CNI configuration path.
[This change](https://github.com/kubernetes/kubernetes/pull/43474) ensures
kubelet does not start pods that require networking before
[networking is ready](https://github.com/kubernetes/kubernetes/issues/43014).
This change may require changes to clients that gate pod creation and/or
scheduling on the node condition `type` `Ready` `status` being `True` for pods
that need to run prior to the network being ready.
* **Enhance Kubelet QoS**: * **Enhance Kubelet QoS**:
* Pods are placed under a new cgroup hierarchy by default. This feature requires * Pods are placed under a new cgroup hierarchy by default. This feature requires
draining and restarting the node as part of upgrades. To opt-out set draining and restarting the node as part of upgrades. To opt-out set
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment