Add blog on shifting to cgroup v2 after cgroup v1 deprecation in v1.35 - #56945
Add blog on shifting to cgroup v2 after cgroup v1 deprecation in v1.35#56945pacoxu wants to merge 6 commits into
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
/cc @kannon92 @neolit123 @sohankunkerkar @KentaTada Sorry for the delay. Since you reviewed the original PR #47342 two years ago, would you mind giving it another quick look when you get a chance? |
|
@pacoxu: GitHub didn't allow me to request PR reviews from the following users: KentaTada. Note that only kubernetes members and repo collaborators can review this PR, and authors cannot review their own PRs. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
8e31cce to
8d3ede4
Compare
| --- | ||
| layout: blog | ||
| title: 'The Shift to cgroup v2 in Kubernetes: What You Need to Know' | ||
| draft: true |
There was a problem hiding this comment.
update draft=false, once the blog is ready and publish date is confirmed.
neolit123
left a comment
There was a problem hiding this comment.
LGTM, just one inline comment.
also a question - should we mention that we now have strict validation for cgroups v2 from the system-validators lib?
| memory requests and limits for containers that perform intensive I/O, after measuring an appropriate | ||
| value. | ||
|
|
||
| ### Memory QoS updates in Kubernetes v1.36 |
There was a problem hiding this comment.
i recommend adding a note how memoryqos relates to cgroups v2.
There was a problem hiding this comment.
Add a simple intro for kubeadm/system-validators check and why memory QoS needs cgroup v2 as a note.
Description
Preview: https://deploy-preview-56945--kubernetes-io-main-staging.netlify.app/blog/2026/08/20/kubernetes-cgroups-v2-shift/
This PR is based on #47342.
I will update according to latest changes around cgroup v2/v1.
Issue
Closes: None
Table of contents
active_filememory handling