Add Kubernetes 1.31 release blog #47281
Conversation
k8s-ci-robot
added
the
cncf-cla: yes
k8s-ci-robot
added
area/blog
k8s-ci-robot
added
do-not-merge/work-in-progress
|
We are still collecting content. We will aim to get content added here for review by next Friday August 2nd. /hold |
k8s-ci-robot
added
the
do-not-merge/hold
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
@sftim, its going well. We should still be on track to add the draft content to the PR this friday |
k8s-ci-robot
added
size/L
|
|
||
|
|
||
|
|
||
| ## Release theme and logo |
There was a problem hiding this comment.
@neoaggelos can you send this over when you have the theme and logo ready
|
|
||
| Also see our [Kubernetes Removals and Major Changes In v1.31](https://kubernetes.io/blog/2024/07/19/kubernetes-1-31-upcoming-changes/) blog. | ||
|
|
||
| #### Cgroup v1 enters the maintenance mode |
There was a problem hiding this comment.
There is a blog going out #47069, currently set for 8/15. Should we move the date of that blog to go out the same day as the release? I'd like to make sure we don't create confusion about this topic so i think it would be good if we can link to this blog to give readers more context
There was a problem hiding this comment.
the content as written, currently links to the blog. So we'd have to update that if we dont publish the blogs the same day.
There was a problem hiding this comment.
@harche can you review this content around the cgroup maintenance mode for the release blog?
There was a problem hiding this comment.
@rashansmith what do you think about the publishing date?
There was a problem hiding this comment.
please also see #47069 (comment). I've updated the content here to include more information in the release blog and no longer link to the #47069 post. This way the #47069 can go out on august 14th and we dont have to worry about timestamps. This release blog will be the only blog we publish August 13th and feature blogs will start publishing august 14th.
There was a problem hiding this comment.
We can if we want change #47069, post release. The change I'm imagining would revise this article with a link to the new post.
|
added the draft content we have so far. We are waiting for one more KEP to get back to us with content. Its still in draft b/c i'd like to spend some time editing before the blog reviews spend time on it to hopefully catch small clean up. but anticipate bringing this out of draft for Monday |
k8s-ci-robot
removed
the
do-not-merge/work-in-progress
|
|
||
| Kubernetes support for AppArmor is now GA. Protect your Containers using AppArmor by setting the `appArmorProfile.type` field in the Container's `securityContext`. Note that before Kubernetes v1.30, AppArmor was controlled via annotations; starting in v1.30 it is contorlled using fields. Its recommended that you should migrate away from using annotations and start using the `appArmorProfile.type` field. | ||
|
|
||
| To learn more read the [AppArmor tutorial](/docs/tutorials/security/apparmor/). This work was done as a part of [KEP #24](https://github.com/kubernetes/enhancements/issues/24) lead by [SIG Node](https://github.com/kubernetes/community/tree/master/sig-node). |
There was a problem hiding this comment.
Do we have any other docs for AppArmor yet? Ideally we would.
There was a problem hiding this comment.
as far as i can tell these are the docs we have. There is a PR for adding some more apparmor related docs, but its not merged yet.
There was a problem hiding this comment.
@sftim following up here, dont think there are any other apparmor docs that i can find.
There was a problem hiding this comment.
We could nudge release docs to nudge the SIG about adding some, but it's not directly relevant to this announcement.
| * [Random Pod selection on ReplicaSet downscaling]( https://github.com/kubernetes/enhancements/issues/2185) | ||
|
|
||
|
|
||
| ### Deprecations and Removals |
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
| Announcing the release of Kubernetes v1.31: <THING>, <tagline>! | ||
|
|
||
| Similar to previous releases, the release of Kubernetes v1.31 introduces new | ||
| stable, beta, and alpha features. | ||
| The consistent delivery of high-quality releases underscores the strength of our development cycle and the vibrant support from our community. | ||
| This release consists of 45 enhancements. | ||
| Of those enhancements, 11 have graduated to Stable, 22 are entering Beta, | ||
| and 12 have graduated to Alpha. | ||
|
|
||
| ## Release theme and logo | ||
| <Logo image size is recommended to be no more than 2160px/> |
There was a problem hiding this comment.
Highlighting that we'll need to fill this in.
k8s-ci-robot
added
the
sig/docs
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sftim 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 |
a-mccarthy
force-pushed
the
1-31-release-blog
branch
2 times, most recently
from
707b209 to
5e34930
Compare
| Traffic distribution for Services moves to beta in v1.31 and is enabled by default. | ||
|
|
||
| After several iterations on finding the best user experience and traffic engineering capabilities for Services networking, the SIG Networking implemented the `trafficDistribution` field in the Service specification, that serves as a guideline for the underlying implementation to consider while making routing decisions. | ||
| It supersedes the functionality formerly provided by the `service.kubernetes.io/topology-mode` annotation and its precursor `topologyKeys` field (which has been deprecated since Kubernetes 1.21). |
There was a problem hiding this comment.
| It supersedes the functionality formerly provided by the `service.kubernetes.io/topology-mode` annotation and its precursor `topologyKeys` field (which has been deprecated since Kubernetes 1.21). |
This one line in itself (without additional context about deprecations etc) may end up confusing people about: "Does service.kubernetes.io/topology-mode no longer work?" etc. Let's just include the first sentence? The link for the detailed docs (which you have already included) should help clarify all the other details.
Besides this, LGTM
There was a problem hiding this comment.
thanks for the suggestion, @gauravkghildiyal, i've updated the content to remove this sentence.
| author: > | ||
| [Kubernetes v1.31 Release Team](https://github.com/kubernetes/sig-release/blob/master/releases/release-1.31/release-team.md) | ||
| --- | ||
|
|
There was a problem hiding this comment.
Editors: Matteo Bianchi, Yigit Demirbas, Abigail McCarthy, Edith Puclla, Rashan Smith
Maybe we can add this line like in the 1.30 blog? Just noticed the difference while looking at the draft (ordered by surname but maybe it's not the right one)
a-mccarthy
force-pushed
the
1-31-release-blog
branch
from
e871065 to
ada414d
Compare
adding 1.31 release blog remove some typos removing typos Apply suggestions from review Co-authored-by: Tim Bannister <[email protected]> Co-authored-by: Dmitry Shurupov <[email protected]> minor updates, adding KEP kubernetes#4193 content Apply suggestions from review Co-authored-by: Tim Bannister <[email protected]> small nits from review Apply suggestions from code review Co-authored-by: Dipesh Rawat <[email protected]> Co-authored-by: Tim Bannister <[email protected]> Apply suggestions from code review Co-authored-by: Dmitry Shurupov <[email protected]> Co-authored-by: Tim Bannister <[email protected]> Co-authored-by: Rey Lejano <[email protected]> Co-authored-by: Mengjiao Liu <[email protected]> updating deprecations and removals Apply suggestions from code review Co-authored-by: Tim Bannister <[email protected]> Co-authored-by: Sascha Grunert <[email protected]> updating file name, adding intro, fixing spacing updating cgroup section update bound service account docs update nft tables section update tenses in deprecation section Apply suggestions from code review Co-authored-by: Antonio Ojea <[email protected]> update nft and bound service account sections Apply suggestions from code review Co-authored-by: Dipesh Rawat <[email protected]> add release logo Apply suggestions from code review Co-authored-by: 杨朱 · Kiki <[email protected]> small nits Apply suggestions from code review Co-authored-by: Kat Cosgrove <[email protected]>
a-mccarthy
force-pushed
the
1-31-release-blog
branch
from
44e73aa to
d3f0d98
Compare
|
/lgtm |
k8s-ci-robot
added
the
lgtm
|
LGTM label has been added. Git tree hash: a6faac78588375ba27bc9b4b6b56d91a47087325
|
|
/lgtm |
|
/unhold |
k8s-ci-robot
removed
the
do-not-merge/hold
|
|
||
| [VolumeAttributesClass](/docs/concepts/storage/volume-attributes-classes/) API is moving to beta in v1.31. | ||
| The VolumeAttributesClass provides a generic, | ||
| Kubernetes-native API for modifying dynamically volume parameters like provisioned IO. |
There was a problem hiding this comment.
nit: dynamically volume -> dynamically provisioned volume
Just a nit.
PR for adding the Kubernetes 1.31 release blog.
🛑 Do not unhold or merge until Kubernetes v1.31 is released 🛑
This blog will include the identified Major themes from this discussion: kubernetes/sig-release#2526