-
Notifications
You must be signed in to change notification settings - Fork 395
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
Final draft for v1.31 release #2579
Final draft for v1.31 release #2579
Conversation
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.
Hi, I'm KEP-3619 owner. May I add this release note item
- Added Node.Status.Features.SupplementalGroupsPolicy field which is set to true when the feature is implemented in the CRI implementation (KEP-3619) ([#125470](https://github.com/kubernetes/kubernetes/pull/125470), [@everpeace](https://github.com/everpeace)) [SIG API Machinery, Apps, Node and Testing]
next to L.64?
- Support fine-grained supplemental groups policy (KEP-3619), which enables fine-grained control for supplementary groups in the first container processes. You can choose whether to include groups defined in the container image(/etc/groups) for the container's primary uid or not. ([#117842](https://github.com/kubernetes/kubernetes/pull/117842), [@everpeace](https://github.com/everpeace)) [SIG API Machinery, Apps and Node] |
This item is user-facing which is related to KEP-3619. And, this item is actually included in rc.0 release note: https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.31.md?plain=1#L186
Would it be possible to re-generate release note / add it manually from kubernetes/kubernetes#124815? I added release-note field there today. It could be one of the "Urgent Upgrade Notes". Chance that someone has the removed feature gates enabled is very low, but if they do, then they need to remove them from cmdline of all Kubernetes components. I am adding a note to the release blog here: https://github.com/kubernetes/website/pull/47281/files#r1703842605 |
b3f1422
to
cacf61d
Compare
PR needs rebase. 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. |
cacf61d
to
84a8799
Compare
4e7c24b
to
30c9a3c
Compare
30c9a3c
to
96187af
Compare
0fd7467
to
a72675b
Compare
a72675b
to
66025a0
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: neoaggelos, npolshakova 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 |
What type of PR is this:
/kind cleanup
/kind documentation
What this PR does / why we need it:
This PR refactors and fine-tunes all the release-notes for v1.31.0, and does the following:
The major themes link to the upcoming release article will not be included as we are moving away from having major themes being a thing in future releases.