mirror of https://github.com/k3s-io/k3s
Merge pull request #53436 from liggitt/kubeadm-init
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>. Add /var/lib/kubelet error to known issues Document https://github.com/kubernetes/kubernetes/issues/53356 in known issues for 1.8.0pull/6/head
commit
7b61fb37ef
|
@ -691,6 +691,10 @@ This section contains a list of known issues reported in Kubernetes 1.8 release.
|
|||
|
||||
For more information, see [#53288](https://issue.k8s.io/53288).
|
||||
|
||||
* `kubeadm init` and `kubeadm join` invocations on newly installed systems can encounter a `/var/lib/kubelet is not empty` message during pre-flight checks that prevents setup. If this is the only pre-flight failure, it can be safely ignored with `--skip-preflight-checks`.
|
||||
|
||||
For more information, see [#53356](https://issue.k8s.io/53356#issuecomment-333748618).
|
||||
|
||||
* A performance issue was identified in large-scale clusters when deleting thousands of pods simultaneously across hundreds of nodes. Kubelets in this scenario can encounter temporarily increased latency of `delete pod` API calls -- above the target service level objective of 1 second. If you run clusters with this usage pattern and if pod deletion latency could be an issue for you, you might want to wait until the issue is resolved before you upgrade.
|
||||
|
||||
For more information and for updates on resolution of this issue, see [[#51899](https://github.com/kubernetes/kubernetes/pull/51899)](https://issue.k8s.io/51899).
|
||||
|
|
Loading…
Reference in New Issue