You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 v1.37 Release Tracking (view). 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 1.24 or Immutable Secrets and ConfigMaps from the 1.21 release, as well the cgroup v2 change in 1.31.
What do I need to do?
Pick a group of SIGs to reach out to (listed below), and comment your selection on this issue
Reach out to the SIGs in slack to ask for Release Highlights feedback and directing them to the github discussion using the template below
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?
Following is a bootstrap 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 add your own personalization to the message if you'd like to.
Following that message, it is advised to ping the SIGs every 2 weeks to remind them about the release highlights.
SIG groups
The following are groups of SIGs we need to reach out to. The SIGs are grouped into a mix of those that have tracked enhancements for this release and those that have not. Please comment below with the group you'd like to reach out to.
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.
Overview
The release comms team will use this issue to track the work on nudging SIGs for entries on release highlights for the v1.37 release cycle.
Release Highlights discussion for v1.37: #3051 Release Highlights deadline: Tuesday 28th July, 2026.
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 v1.37 Release Tracking (view). 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 1.24 or Immutable Secrets and ConfigMaps from the 1.21 release, as well the cgroup v2 change in 1.31.
What do I need to do?
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?
Following is a bootstrap 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 add your own personalization to the message if you'd like to.
A template message can be found here
Following that message, it is advised to ping the SIGs every 2 weeks to remind them about the release highlights.
SIG groups
The following are groups of SIGs we need to reach out to. The SIGs are grouped into a mix of those that have tracked enhancements for this release and those that have not. Please comment below with the group you'd like to reach out to.
Group 1 - @TineoC
Group 2 - @RinkiyaKeDad
Group 3 - @SwathiR03
Group 4 - @SophiaUgo
Group 5 - @kirti763
Group 6 - @troy0820
Extras:
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 1.37
Ref to comms lead progress issue: #3027
Previous Release: #2963