Repository navigation
Kubernetes 1.38 Release Highlights Discussion #3121
Replies: 10 comments 2 replies
|
SIG UI has nothing to highlight |
|
SIG Cluster lifecycle has nothing to highlight |
|
SIG Windows: • KEP-4885: Windows CPU and Memory Affinity graduates from Alpha to Beta in v1.38, with the feature gate enabled by default. This brings topology-aware CPU and memory placement to Windows nodes through the CPU, Memory, and Topology Managers. Administrators must configure the corresponding manager policies to use affinity. |
|
SIG-CLI:
|
|
SIG-Apps:
|
|
SIG-Autoscaling has nothing to report. |
|
SIG Security has nothing to report. Thanks to @naseyro for the followup |
|
SIG-Node <https://kubernetes.slack.com/archives/C0BP8PW9G/p1795106907358889>,
has nothing to highlight
Regards
Urvashi
…On Tue, Oct 13, 2026 at 11:46 AM Arsh Sharma ***@***.***> wrote:
This is a discussion to collect the Release Highlights for the v1.38
release cycle.
Release Highlights are an essential part of the Kubernetes release cycle
as they provide a birds-eye view of improvements, breaking or user-facing
changes that are coming as part of the upcoming release. The release Comms
team is asking for SIGs to comment on this discussion with items that we
should highlight in release communications for v1.38.
For each submission, please include a link to the KEP, the stage the
feature is moving to, and a brief description of the KEP that will be used
as an outline for the blog post content.
The deadline for v1.38 Release Highlights is *Tuesday 24th November 2026*.
Here is the discussion thread
<#3051> from the
last release cycle.
cc @kubernetes/release-team-leads
<https://github.com/orgs/kubernetes/teams/release-team-leads>
cc @Braundo <https://github.com/Braundo> @kirti763
<https://github.com/kirti763> @Urvashi0109
<https://github.com/Urvashi0109> @naseyro <https://github.com/naseyro>
@sayanchowdhury <https://github.com/sayanchowdhury>
—
Reply to this email directly, view it on GitHub
<#3121?email_source=notifications&email_token=AVZS4QDCPU7ZVABQ2NYMTID5TXCDVA5CNFSNUABBM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63RPGEYTAMBWGY4TJJTSMVQXG33OU5WWK3TUNFXW5JLFOZSW45FMMZXW65DFOJPWG3DJMNVQ>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVZS4QBLLDLAPB3Y5NJV7XD5TXCDVAVCNFSNUABHKJSXA33TNF2G64TZHM4TOOBWGAZDGOJ3IRUXGY3VONZWS33OHMYTCMBQGY3DSNFBOYBA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
SIG Network:
|
Uh oh!
There was an error while loading. Please reload this page.
This is a discussion to collect the Release Highlights for the v1.38 release cycle.
Release Highlights are an essential part of the Kubernetes release cycle as they provide a birds-eye view of improvements, breaking or user-facing changes that are coming as part of the upcoming release. The release Comms team is asking for SIGs to comment on this discussion with items that we should highlight in release communications for v1.38.
For each submission, please include a link to the KEP, the stage the feature is moving to, and a brief description of the KEP that will be used as an outline for the blog post content.
The deadline for v1.38 Release Highlights is Tuesday 24th November 2026.
Here is the discussion thread from the last release cycle.
cc @kubernetes/release-team-leads
cc @Braundo @kirti763 @Urvashi0109 @naseyro @sayanchowdhury
All reactions