Kubernetes v1.34 Release Highlights contact

[aibarbetta]

Overview

The Release Comms team will use this issue to track the work on nudging SIGs for entries on release highlights for the release cycle.

Release Highlights discussion for v1.34: #2806
Release Highlights deadline: Tuesday 29th July 2025.

Release Highlights are collected during each release cycle for every SIG to see what should be highlighted in the release blog, webinar, and other communications. Different SIGs have a different number of tracked enhancements. Some SIGs have activities that aren't quite coupled with Kubernetes releases, and it's worth checking with them in case there are things worth calling out in what they did between the previous release and the current release. One example is the Dockershim removal from v1.24 or Immutable Secrets and ConfigMaps from the v1.21 release, as well the cgroup v2 change in v1.31.

What do I need to do?

1. Pick a group of SIGs to reach out to (listed below), and comment your selection on this issue
2. Reach out to the SIGs in Slack to ask for Release Highlights feedback and directing them to the github discussion using the template below
3. Comment here when you've completed reaching out to the SIGs

Depending on the responses we get, we may need to send out a reminder in Slack later in the release cycle to each SIG to get more feedback on Release Highlights Themes.

How do I find a SIG's slack channel?

The Slack channel for each SIG is usually #sig-, but accurate links are available in k/community under sig-list.md. The plan is to ask for responses on the public Slack channel (non-disruptively).

What should I say?

There is a template that you can use to reach out to the individual SIGs informing them about the discussion thread. This template includes the important information to convey to the SIG, but you are free to personalise the message if you'd like to.

A template message can be found here (note how there are some placeholders that need to be adjusted).

Following that message, it is advisable to ping the SIGs every 2 weeks to remind them about the release highlights if they haven't responded.

SIG groups

The following are groups of SIGs we need to reach out to. The SIGs are grouped together in a mix of those that have tracked enhancements for this release and those that do not. Please comment below with the group you'd like to reach out to.

Group 1 - @aibarbetta

• Node
• Cloud Provider
• Architecture (answered no highlights)
• Testing (answered with no highlights)

Group 2 - @88abb

• Auth
• CLI
• K8s Infra (answered no highlights)
• Multicluster (answered no highlights)

Group 3 - @graz-dev

• API Machinery
• Scheduling
• Autoscaling
• Security

Group 4 - @dipesh-rawat

• Network
• Instrumentation
• Cluster Lifecycle (answered no highlights)
• Scalability

Group 5 - @cloudmelon

• Storage
• Apps
• Windows
• UI

Extras - @aibarbetta

• Release
• Docs (answered no highlights)
• Contributor Experience (answered no highlights)
• etcd

We'll try to keep the list up-to-date, but please double-check in the comments if someone has contacted their assigned channels. We can debate more details in Slack.

/milestone v1.34

xref: #2735

[aibarbetta]

/priority important-soon
/kind documentation

[aibarbetta]

/assign @aibarbetta @dipesh-rawat @graz-dev @cloudmelon @88abb

[k8s-ci-robot]

@aibarbetta: GitHub didn't allow me to assign the following users: 88abb.

Note that only kubernetes members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @aibarbetta @dipesh-rawat @graz-dev @cloudmelon @88abb

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.

[aibarbetta]

/assign @88abb