-
Notifications
You must be signed in to change notification settings - Fork 14.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
setup/cri: add a section about cgroup drivers #12638
Conversation
/priority important-soon |
/assign @chenopis |
Deploy preview for kubernetes-io-master-staging ready! Built with commit 2967c4f https://deploy-preview-12638--kubernetes-io-master-staging.netlify.com |
/lgtm |
content/en/docs/setup/cri.md
Outdated
for the rest can become unstable under resource pressure. | ||
|
||
Changing the settings such that your container runtime and kubelet use `systemd` as the cgroup driver | ||
stabilized the system. Pleas note the `native.cgroupdriver=systemd` option in the Docker setup below. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From what I can tell the containerd section will also need to be updated for this as well: https://github.com/containerd/cri/blob/master/docs/config.md
That said, that section also needs to be updated for containerd v1.2.x and for CVE-2019-5736 as well. If needed I can create a followup PR to address that section.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, please send a follow up.
CRI-O also has the option:
https://github.com/kubernetes-sigs/cri-o/blob/master/docs/crio.conf.5.md
the problem with containerd and CRI-O is if we set it on setup, kubeadm cannot detect it and it will fail if set to systemd
, until the users also adds --cgroup-driver=systemd
in KUBELET_EXTRA_FLAGS
: https://kubernetes.io/docs/setup/independent/kubelet-integration/
hopefully this is known by the users at this point.
/lgtm |
/lgtm |
56e7472
to
daff877
Compare
fixed typo |
daff877
to
84adda9
Compare
A cgroup driver is an important setting for the CRI and the kubelet. Add a section that explains why "systemd" is the suggested value for a driver when installing a CRI. In the case of Docker the kubelet will receive this value automatically. For the other CRIs, the users should tackle this manually.
84adda9
to
d192599
Compare
/lgtm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Thanks.
@neolit123 did a quick revision for style/grammar. Please let me know if it's still technically correct. |
thanks, the changes seem good. |
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: zparnold The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
* setup/cri: add a section about cgroup drivers A cgroup driver is an important setting for the CRI and the kubelet. Add a section that explains why "systemd" is the suggested value for a driver when installing a CRI. In the case of Docker the kubelet will receive this value automatically. For the other CRIs, the users should tackle this manually. * Update cri.md
* setup/cri: add a section about cgroup drivers A cgroup driver is an important setting for the CRI and the kubelet. Add a section that explains why "systemd" is the suggested value for a driver when installing a CRI. In the case of Docker the kubelet will receive this value automatically. For the other CRIs, the users should tackle this manually. * Update cri.md
* setup/cri: add a section about cgroup drivers A cgroup driver is an important setting for the CRI and the kubelet. Add a section that explains why "systemd" is the suggested value for a driver when installing a CRI. In the case of Docker the kubelet will receive this value automatically. For the other CRIs, the users should tackle this manually. * Update cri.md
A cgroup driver is an important setting for the CRI and the kubelet.
Add a section that explains why "systemd" is the suggested value
for a driver when installing a CRI.
In the case of Docker the kubelet will receive this value automatically.
For the other CRIs, the users should tackle this manually.
Also default the value to
systemd
on Debian installs for Docker.this is not a new feature so i'm sending against master.
original text by @mauilion
cc @timothysc @kubernetes/sig-cluster-lifecycle-pr-reviews
/sig cluster-lifecycle
fixes kubernetes/kubeadm#1394