Move cgroup v1 support into maintenance mode

[harche]

Enhancement Description

• One-line enhancement description (can be used as a release note): Moving cgroup v1 support into maintenance mode
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/4569-cgroup-v1-maintenance-mode/README.md
• Discussion Link:
• Primary contact (assignee): @harche
• Responsible SIGs: sig-node
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y):
  • Beta release target (x.y):
  • Stable release target (x.y): 1.31
• Stable
  • KEP (k/enhancements) update PR(s): Move cgroup v1 support into maintenance mode #4572
  • Code (k/k) update PR(s):
    • KEP-4569: Separate cgroup v1 and v2 manager implementations kubernetes#125496
    • [KEP-4569] Add a warning log, an event for cgroup v1 usage and a metric for cgroup version kubernetes#125328
    • KEP-4569: Kubelet option to disable cgroup v1 support kubernetes#126031
  • Docs (k/website) update PR(s):
    • Blog post about cgroup v1 support moving to maintenance mode / KEP-4569 website#47069

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

[harche]

/sig node

[harche]

/assign

[SergeyKanzhelev]

I updated the name of a KEP (this issue title) as per our decision: #4572 (comment).

@harche can you please update it in kep.yaml as well?

[SergeyKanzhelev]

/label lead-opted-in
/milestone v1.31

[tjons]

Hello @harche 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 14th June 2024 / 19:00 PDT Thursday 13th June 2024.

This enhancement is targeting for stage stable for 1.31 (correct me, if otherwise)

Here’s where this enhancement currently stands:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: { 1.31 }. KEPs targeting stable will need to be marked as implemented after code PRs are merged and the feature gates are removed.
• KEP readme has up-to-date graduation criteria.
• KEP has submitted a production readiness review request for approval and has a reviewer assigned.
• KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here).

With all the KEP requirements in place and merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze. 🚀

The status of this enhancement is marked as tracked for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

[sreeram-venkitesh]

/stage alpha

[harche]

@sreeram-venkitesh this feature is going straight for GA. There is no alpha or beta stage for this feature.

[sreeram-venkitesh]

@harche Thanks for clarifying! Would you consider this KEP as of type Deprecation? (See Type column in the enhancements tracking board) Does maintenance mode entail that the feature/KEP is planned to be deprecated? Please also update the issue description.

/stage stable

[harche]

Thanks for clarifying! Would you consider this KEP as of type Deprecation?

This KEP is not going to deprecate cgroup v1 support, hence we would not like to classify it as deprecation.

[sreeram-venkitesh]

Thanks for the quick update!

[hacktivist123]

Hello @harche 👋, 1.31 Docs Shadow here.

Does this enhancement work planned for 1.31 require any new docs or modification to existing docs?
If so, please follows the steps here to open a PR against dev-1.31 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday June 27, 2024 18:00 PDT.

Also, take a look at Documenting for a release to get yourself familiarised with the docs requirement for the release.

Thank you!

[harche]

Hello @harche 👋, 1.31 Docs Shadow here.

Does this enhancement work planned for 1.31 require any new docs or modification to existing docs? If so, please follows the steps here to open a PR against dev-1.31 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday June 27, 2024 18:00 PDT.

Also, take a look at Documenting for a release to get yourself familiarised with the docs requirement for the release.

Thank you!

kubernetes/website#46801

[rashansmith]

Hi @harche,

👋 from the v1.31 Communications Team! We'd love for you to opt in to write a feature blog about your enhancement!
Some reasons why you might want to write a blog for this feature include (but are not limited to) if this introduces breaking changes, is important to our users, or has been in progress for a long time and is graduating.

To opt in, let us know and open a Feature Blog placeholder PR against the website repository by 3rd July, 2024. For more information about writing a blog see the blog contribution guidelines.

Note: In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.

[tjons]

Hello 👋 1.32 Enhancements Lead here,

I'm closing milestone 1.31 now,
If you have more work on this enhancement to complete in v1.32, please follow the instructions here to opt in the enhancement and make sure the lead-opted-in label is set so it can get added to the tracking board and finally add /milestone v1.32. Thanks!

/milestone clear

[tjons]

Hi, enhancements lead here - I inadvertently added this to the 1.32 tracking board 😀. Please readd it if you wish to progress this enhancement in 1.32.

/remove-label lead-opted-in

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[kannon92]

/remove-lifecycle stale

[kannon92]

@harche anything left to do for this feature?

There is no feature gate so can we close this as done?

[harche]

@harche anything left to do for this feature?

There is no feature gate so can we close this as done?

All PRs for this feature have been merged.

/close

[k8s-ci-robot]

@harche: Closing this issue.

In response to this:

@harche anything left to do for this feature?

There is no feature gate so can we close this as done?

All PRs for this feature have been merged.

/close

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.