Create 2021-04-08-kubernetes-release-1.21.md #27233
Conversation
|
Deploy preview for kubernetes-io-master-staging ready! Built with commit 1add12a https://deploy-preview-27233--kubernetes-io-master-staging.netlify.app |
|
|
||
| # Ecosystem Updates | ||
|
|
||
| Master -> Main default branch migration [(PR#21451)](https://github.com/kubernetes/test-infra/pull/21451) is here! This migration divides tests as main and release branches, removes v1alpha2 tests and adds apidiff test, and fixes naming from master to main. |
There was a problem hiding this comment.
I'd probably omit this, or link to our guidelines on migrating which might also not be appropriate for ecosystem updates. The PR linked is for one repo cluster-api-provider-aws, we have others that have migrated and the alpha etc stuff isn't appropriate to anything but that repo.
There was a problem hiding this comment.
@mrbobbytables : Please could you let me know where the guidelines for migrating would be? I'll link that here instead.
There was a problem hiding this comment.
Also consider using → for arrows rather than ->.
There was a problem hiding this comment.
Our guidelines are at k8s.dev/rename
It's not really an ecosystem update though as all this stuff is in Org and we've had multiple repos go through that process. I'd lean on removing the entry and highlight we can now have the process in place to migrate
There was a problem hiding this comment.
I've reworded this slightly per your suggestions. PTAL & let me know if there are any further changes to be made :)
|
|
||
| # User Highlights | ||
|
|
||
| - CNCF welcomes 47 new organizations across the globe as members to advance Cloud Native technology further at the start of 2021! These [new members](https://www.cncf.io/announcements/2021/02/24/cloud-native-computing-foundation-welcomes-47-new-members-at-the-start-of-2021/) will join CNCF at the upcoming 2021 KubeCon + CloudNativeCon events, including [KubeCon + CloudNativeCom EU – Virtual](https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/) from May 4 – 7, 2021, and [KubeCon + CloudNativeCon NA in Los Angeles](https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/) from October 12 – 15, 2021. |
There was a problem hiding this comment.
KubeCons and general CNCF updates have IIRC been in the ecosystem updates with specific users things being in the user highlight section, it may be more appropriate to put the kubecon note in the events section.
There was a problem hiding this comment.
@mrbobbytables : This is more around the 47 new organizations joining CNCF bit. Do you want me to write up an alternate blurb with contents from this announcement - https://www.cncf.io/announcements/2021/02/24/cloud-native-computing-foundation-welcomes-47-new-members-at-the-start-of-2021/#:~:text=%E2%80%93%20February%2024%2C%202020%20%E2%80%93%20The,driving%20cloud%20native%20technology%20innovation.?
There was a problem hiding this comment.
@mrbobbytables just to clarify would the existing blurb be okay? Or does it require more content from the blog?
| * Follow us on Twitter [@Kubernetesio](https://twitter.com/kubernetesio) for latest updates | ||
| * Join the community discussion on [Discuss](https://discuss.kubernetes.io/) | ||
| * Join the community on [Slack](https://slack.k8s.io/) | ||
| * Share your Kubernetes [story](https://docs.google.com/a/linuxfoundation.org/forms/d/e/1FAIpQLScuI7Ye3VQHQTwBASrgkjQDSS5TP0g3AXfFhwSM9YpHgxRKFA/viewform) |
There was a problem hiding this comment.
@mrbobbytables I haven't seen this form before, if anything I would link https://github.com/cncf/foundation/blob/master/case-study-guidelines.md.
There was a problem hiding this comment.
@mrbobbytables : This has been done. Would you please be able to take a look whenever free and let me know for any changes that need to be made? Thank you!
| https://github.com/kubernetes/enhancements/issues/19 | ||
|
|
||
| ### IPv4/IPv6 dual-stack support | ||
| IP addresses are a consumable resource operators and cluster administrators need to make sure are not exhausted. Having dual-stack support enables native IPv6 routing to pods and services, and it also improves a possible scaling limitation for workloads. |
There was a problem hiding this comment.
| IP addresses are a consumable resource operators and cluster administrators need to make sure are not exhausted. Having dual-stack support enables native IPv6 routing to pods and services, and it also improves a possible scaling limitation for workloads. | |
| IP addresses are a consumable resource that cluster operators and administrators need to make sure are not exhausted. Having dual-stack support enables native IPv6 routing to pods and services, and it also improves a possible scaling limitation for workloads. |
Small suggestion to help readability^^;;;
There was a problem hiding this comment.
BTW, single-stack IPv6 has been stable for a while. Dual-stack lets you use IPv6 in your cluster and also talk to the rest of the internet!
There was a problem hiding this comment.
If we want to, we can link to/docs/concepts/services-networking/dual-stack/
There was a problem hiding this comment.
Done in the latest commit, do let me know if this needs rewording.
There was a problem hiding this comment.
page preview: https://deploy-preview-27233--kubernetes-io-master-staging.netlify.app/blog/2021/04/08/kubernetes-1-21-release-announcement/
I also noticed there are inconsistencies in the word pod where some have lowercase p and some have capital p. I think having a consistent format would be helpful! :)
| ### CronJobs Graduate to Stable! | ||
| CronJobs (previously ScheduledJobs) has been a beta feature since Kubernetes 1.8! With 1.21 we get to finally see this widely used API graduate to stable. | ||
|
|
||
| CronJobs are meant for performing all time-related actions, namely backups, report generation and the like. Each of these tasks should be allowed to run repeatedly (once a day/month, etc.) or once at a given point in time. |
There was a problem hiding this comment.
I feel like the phrasing of and the like here is a bit confusing? Is there a better way to phrase it?
There was a problem hiding this comment.
“and so on” is more widely recognized by non-native English speakers, I think.
There was a problem hiding this comment.
I've modified it to "and so on" in the current commit. Do let me know if the former sounds better in comparison to the one we have right now.
|
/sig release |
| https://github.com/kubernetes/enhancements/issues/19 | ||
|
|
||
| ### IPv4/IPv6 dual-stack support | ||
| IP addresses are a consumable resource operators and cluster administrators need to make sure are not exhausted. Having dual-stack support enables native IPv6 routing to pods and services, and it also improves a possible scaling limitation for workloads. |
There was a problem hiding this comment.
If we want to, we can link to/docs/concepts/services-networking/dual-stack/
| What's next? We're developing a new feature, tentatively called PodIsolationPolicy, that covers the key PodSecurityPolicy use cases with greatly improved ergonomics and maintainability. To learn more, check out the PSP feature blog [here](). | ||
|
|
||
| ### TopologyKeys Deprecation | ||
| The service field topologyKeys is being deprecated and replaced with a new feature called topology-aware hints, which will be released as alpha in Kubernetes 1.21. You can read more details about the proposed changes in the [KEP](https://github.com/kubernetes/enhancements/blob/master/keps/sig-network/2433-topology-aware-hints/README.md) |
There was a problem hiding this comment.
How about:
| The service field topologyKeys is being deprecated and replaced with a new feature called topology-aware hints, which will be released as alpha in Kubernetes 1.21. You can read more details about the proposed changes in the [KEP](https://github.com/kubernetes/enhancements/blob/master/keps/sig-network/2433-topology-aware-hints/README.md) | |
| The Service field `topologyKeys` is now deprecated; all the component features that used this field were previously alpha, and are now also deprecated. | |
| We've replaced `topologyKeys` with a way to implement topology-aware routing, called topology-aware hints. Topology-aware hints are an alpha featuee in Kubernetes 1.21. You can read more details about the replacement feature in [Topology Aware Hints](/docs/concepts/services-networking/topology-aware-hints/); the related [KEP](https://github.com/kubernetes/enhancements/blob/master/keps/sig-network/2433-topology-aware-hints/README.md) explains the context for why we switched. |
There was a problem hiding this comment.
@salaxander : I have made changes to the blurb and committed it, please can you cross-check with the Enhancement owner once?
There was a problem hiding this comment.
@divya-mohan0209 This looks good
|
/hold |
There was a problem hiding this comment.
@divya-mohan0209 👋🏻 A few mechanical changes, otherwise LGTM!
|
|
||
|  | ||
|
|
||
|
|
There was a problem hiding this comment.
Delete extra whitespace
There was a problem hiding this comment.
Just pushed an update to @divya-mohan0209 's branch to address the extra whitespace :)
|
|
||
| In the v1.21 release cycle, which ran for 12 weeks (January 11 to April 8), we saw contributions from [999 companies](https://k8s.devstats.cncf.io/d/9/companies-table?orgId=1&var-period_name=v1.20.0%20-%20now&var-metric=contributions) and [1279 individuals](https://k8s.devstats.cncf.io/d/66/developer-activity-counts-by-companies?orgId=1&var-period_name=v1.20.0%20-%20now&var-metric=contributions&var-repogroup_name=Kubernetes&var-country_name=All&var-companies=All). | ||
|
|
||
|
|
There was a problem hiding this comment.
Delete extra whitespace
| - We now have a process in place for migration of the default branch from master → main. Learn more about the guidelines [here](k8s.dev/rename) | ||
| - CNCF and the Linux Foundation have announced the availability of their new training course, [LFS260 – Kubernetes Security Essentials](https://training.linuxfoundation.org/training/kubernetes-security-essentials-lfs260/). In addition to providing skills and knowledge on a broad range of best practices for securing container-based applications and Kubernetes platforms, the course is also a great way to prepare for the recently launched [Certified Kubernetes Security Specialist](https://training.linuxfoundation.org/certification/certified-kubernetes-security-specialist/) certification exam. | ||
|
|
||
|
|
There was a problem hiding this comment.
Delete extra whitespace
| @@ -0,0 +1,126 @@ | |||
| --- | |||
| layout: blog | |||
| title: 'Kubernetes 1.21: XXXX' | |||
There was a problem hiding this comment.
+1 to @annajung, make sure the actual title's in place before merging.
|
/lgtm Preserving @annajung's explicit hold |
|
LGTM label has been added. Git tree hash: 094d8e164d48f85b91afd5ae2f8a6e4044a5d7e1
|
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: zacharysarah 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 |
|
@mrbobbytables' review looks to have been addressed - is that right? |
Yep. This has been addressed. If there are any suggestions from a content perspective, please do let us know :) |
|
|
||
| **Authors:** [Kubernetes 1.21 Release Team](https://github.com/kubernetes/sig-release/blob/master/releases/release-1.21/release-team.md) | ||
|
|
||
| We’re pleased to announce the release of Kubernetes 1.21, our first release of 2021! This release consists of 51 enhancements: 15 enhancements have graduated to stable, 15 enhancements are moving to beta, 19 enhancements are entering alpha, and 2 features have been deprecated. |
There was a problem hiding this comment.
Sorry! Last min change after going through all the enhancements again, some KEP owner changed their graduation status at the very end and was not reflect correctly in the enhancements sheet.
| We’re pleased to announce the release of Kubernetes 1.21, our first release of 2021! This release consists of 51 enhancements: 15 enhancements have graduated to stable, 15 enhancements are moving to beta, 19 enhancements are entering alpha, and 2 features have been deprecated. | |
| We’re pleased to announce the release of Kubernetes 1.21, our first release of 2021! This release consists of 51 enhancements: 13 enhancements have graduated to stable, 16 enhancements are moving to beta, 20 enhancements are entering alpha, and 2 features have been deprecated. |
There was a problem hiding this comment.
Done! Thanks for raising this.
There was a problem hiding this comment.
@palnabarun You got to this quick! Thanks for pushing the update :)
Co-authored-by: divya-mohan0209 <[email protected]> Co-authored-by: Xander Grzywinski <[email protected]> Co-authored-by: Nabarun Pal <[email protected]> Signed-off-by: Nabarun Pal <[email protected]>
|
title and release logo added |
|
/lgtm
|
|
LGTM label has been added. Git tree hash: b585e0c43b94751505c8b1dcc07ca2f3f055a275
|
|
/hold |
Ah good, I was worried about that. |
|
/hold cancel |
k\website 1.21 release blog draft
Please note the following sections will be added when we have more information around them:
/assign @palnabarun @onlydole
cc: @Pensu @salaxander @rothgar @eve658