github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge pull request #44000 from dcbw/node-readiness-changelog 

Automatic merge from submit-queue

Update CHANGELOG.md to note node readiness after #43474
pull/6/head
Kubernetes Submit Queue 2017-04-03 16:40:16 -07:00 committed by GitHub
parent b8299d010b 75ad7460a2
commit a8e552832d
1 changed files with 9 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
CHANGELOG.md
View File

@ -696,6 +696,15 @@ Anyway, the cluster should get back to the proper size after 10 min.
the new CRI + CNI code path.
* If you are using plugins other than `bridge`, make sure you have
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**:
* 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