sig-release icon indicating copy to clipboard operation
sig-release copied to clipboard

Kubernetes v1.35 Release Highlights contact

Open graz-dev opened this issue 1 month ago • 22 comments

Overview

The release comms team will use this issue to track the work on nudging SIGs for entries on release highlights for the v1.35 release cycle.

Release Highlights discussion for v1.35: https://github.com/kubernetes/sig-release/discussions/2903 Release Highlights deadline: Friday 28th November.

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 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?

  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?

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 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 - @arujjval

  • [x] Node
    • https://github.com/kubernetes/sig-release/discussions/2903#discussioncomment-14902845
  • [x] Cloud Provider
    • https://github.com/kubernetes/sig-release/discussions/2903#discussioncomment-15015769
  • [x] Architecture
    • nothing to share: https://kubernetes.slack.com/archives/C5P3FE08M/p1764164407606549?thread_ts=1764163903.678629&cid=C5P3FE08M
  • [x] Testing
    • nothing to share: https://kubernetes.slack.com/archives/C09QZ4DQB/p1764809286263029?thread_ts=1763564691.000849&cid=C09QZ4DQB

Group 2 - @aakankshabhende

  • [ ] Auth
  • [x] CLI
    • https://github.com/kubernetes/sig-release/discussions/2903#discussioncomment-15087951
  • [x] K8s Infra
    • nothing to share: https://kubernetes.slack.com/archives/CCK68P2Q2/p1762532245072299?thread_ts=1762525565.326399&cid=CCK68P2Q2
  • [x] Multicluster
    • nothing to share: https://kubernetes.slack.com/archives/C09R1PJR3/p1764316773101659?thread_ts=1763558746.481859&cid=C09R1PJR3

Group 3 - @chadmcrowell

  • [x] API Machinery
    • https://github.com/kubernetes/sig-release/discussions/2903#discussioncomment-15015559
  • [x] Scheduling
    • https://github.com/kubernetes/sig-release/discussions/2903#discussioncomment-15058949
  • [x] Autoscaling
    • https://github.com/kubernetes/sig-release/discussions/2903#discussioncomment-15089289
  • [x] Security
    • nothing to share https://kubernetes.slack.com/archives/C019LFTGNQ3/p1764809470907689?thread_ts=1763559993.102309&cid=C019LFTGNQ3

Group 4 - @graz-dev

  • [x] Network
    • https://github.com/kubernetes/sig-release/discussions/2903#discussioncomment-15063827
  • [x] Instrumentation
    • https://github.com/kubernetes/sig-release/discussions/2903#discussioncomment-14907025
  • [x] Cluster Lifecycle
    • https://github.com/kubernetes/sig-release/discussions/2903#discussioncomment-14902026
  • [x] Scalability
    • nothing to share: https://kubernetes.slack.com/archives/C09QZTRH7/p1764982309898349?thread_ts=1763542531.386279&cid=C09QZTRH7

Group 5 - @SwathiR03

  • [x] Storage
    • https://github.com/kubernetes/sig-release/discussions/2903#discussioncomment-15029328
  • [x] Apps
    • https://github.com/kubernetes/sig-release/discussions/2903#discussioncomment-15087890
  • [x] Windows
    • nothing to share: https://kubernetes.slack.com/archives/C0SJ4AFB7/p1764178177170299?thread_ts=1763553491.533159&cid=C0SJ4AFB7
  • [x] UI
    • nothing to share: https://kubernetes.slack.com/archives/C09R1JVU6/p1764176850329069?thread_ts=1763553510.321909&cid=C09R1JVU6

Extras - @graz-dev

  • [ ] Release
  • [x] Docs
    • no updates: https://kubernetes.slack.com/archives/C1J0BPD2M/p1763676554959649?thread_ts=1763675883.693369&cid=C1J0BPD2M
  • [ ] Contributor Experience
  • [ ] 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.35

xref: https://github.com/kubernetes/sig-release/issues/2805

graz-dev avatar Nov 04 '25 14:11 graz-dev

@graz-dev: The provided milestone is not valid for this repository. Milestones in this repository: [next, v.1.25, v1.16, v1.17, v1.18, v1.19, v1.20, v1.21, v1.22, v1.23, v1.24, v1.25, v1.26, v1.27, v1.28, v1.29, v1.30, v1.31, v1.32, v1.33, v1.34, v1.35]

Use /milestone clear to clear the milestone.

In response to this:

Overview

The release comms team will use this issue to track the work on nudging SIGs for entries on release highlights for the v1.35 release cycle.

Release Highlights discussion for v1.35: https://github.com/kubernetes/sig-release/discussions/2903 Release Highlights deadline: Friday 28th November.

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 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?

  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?

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 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

  • [ ] Node
  • [ ] Cloud Provider
  • [ ] Architecture
  • [ ] Testing

Group 2

  • [ ] Auth
  • [ ] CLI
  • [ ] K8s Infra
  • [ ] Multicluster

Group 3

  • [ ] API Machinery
  • [ ] Scheduling
  • [ ] Autoscaling
  • [ ] Security

Group 4

  • [ ] Network
  • [ ] Instrumentation
  • [ ] Cluster Lifecycle
  • [ ] Scalability

Group 5

  • [ ] Storage
  • [ ] Apps
  • [ ] Windows
  • [ ] UI

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

xref: #old-issue

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.

k8s-ci-robot avatar Nov 04 '25 14:11 k8s-ci-robot

/milestone v1.35

graz-dev avatar Nov 04 '25 14:11 graz-dev

/priority important-soon /kind documentation

graz-dev avatar Nov 04 '25 14:11 graz-dev

/assign @graz-dev @aakankshabhende @arujjval @SwathiR03 @chadmcrowell

graz-dev avatar Nov 04 '25 14:11 graz-dev

@graz-dev, I would like to take Group 1.

Group 1

  • [ ] Node
  • [ ] Cloud Provider
  • [ ] Architecture
  • [ ] Testing

arujjval avatar Nov 05 '25 05:11 arujjval

@graz-dev I'll take Group 2

Group 2

  • [ ] Auth
  • [ ] CLI
  • [ ] K8s Infra
  • [ ] Multicluster

aakankshabhende avatar Nov 05 '25 05:11 aakankshabhende

@graz-dev, I would like to take up Group 5.

Group 5

  • [ ] Storage
  • [ ] Apps
  • [ ] Windows
  • [ ] UI

SwathiR03 avatar Nov 05 '25 07:11 SwathiR03

@graz-dev, I would like to take Group 3

Group 3

  • [ ] API Machinery
  • [ ] Scheduling
  • [ ] Autoscaling
  • [ ] Security

chadmcrowell avatar Nov 05 '25 11:11 chadmcrowell

All groups were assigned in the issue’s description, we can now start reaching out to SIGs! Please post the link to your messages in this issue for tracking.

graz-dev avatar Nov 07 '25 09:11 graz-dev

Initial outreach for group 4 done:

  • SIG Network: https://kubernetes.slack.com/archives/C09QYUH5W/p1762507911339239
  • SIG Instrumentation: https://kubernetes.slack.com/archives/C20HH14P7/p1762508026608539
  • SIG Cluster Lifecycle: https://kubernetes.slack.com/archives/C13J86Z63/p1762508183279989
  • SIG Scalability: https://kubernetes.slack.com/archives/C09QZTRH7/p1762508269888549

graz-dev avatar Nov 07 '25 09:11 graz-dev

Initial outreach for group 1 done:

  • SIG Node: https://kubernetes.slack.com/archives/C0BP8PW9G/p1762514636718999
  • SIG Cloud Provider: https://kubernetes.slack.com/archives/C718BPBQ8/p1762514428751499
  • SIG Architecture: https://kubernetes.slack.com/archives/C5P3FE08M/p1762514530429019
  • SIG Testing: https://kubernetes.slack.com/archives/C09QZ4DQB/p1762514582651749

arujjval avatar Nov 07 '25 11:11 arujjval

Initial outreach for group 2 done:

  • SIG Auth: https://kubernetes.slack.com/archives/C0EN96KUY/p1762525445534249

  • SIG CLI: https://kubernetes.slack.com/archives/C2GL57FJ4/p1762525502867649

  • SIG K8s Infra: https://kubernetes.slack.com/archives/CCK68P2Q2/p1762525565326399

  • SIG Multicluster: https://kubernetes.slack.com/archives/C09R1PJR3/p1762525626782139

aakankshabhende avatar Nov 07 '25 14:11 aakankshabhende

Initial Outreach for Group 5 done:

  • SIG Storage: https://kubernetes.slack.com/archives/C09QZFCE5/p1762580525468159
  • SIG Apps: https://kubernetes.slack.com/archives/C18NZM5K9/p1762580614368139
  • SIG Windows: https://kubernetes.slack.com/archives/C0SJ4AFB7/p1762580733498619
  • SIG UI: https://kubernetes.slack.com/archives/C09R1JVU6/p1762580791946459

SwathiR03 avatar Nov 08 '25 05:11 SwathiR03

Initial Outreach for Group 3 done:

  • SIG API Machinery: https://kubernetes.slack.com/archives/C0EG7JC6T/p1763131705282779
  • SIG Scheduling: https://kubernetes.slack.com/archives/C09TP78DV/p1763131875487859
  • SIG Autoscaling: https://kubernetes.slack.com/archives/C09R1LV8S/p1763131938863059
  • SIG Security: https://kubernetes.slack.com/archives/C019LFTGNQ3/p1763131973589899

chadmcrowell avatar Nov 14 '25 14:11 chadmcrowell

Second outreach for group 4 done:

  • SIG Network: https://kubernetes.slack.com/archives/C09QYUH5W/p1763542295578959
  • SIG Instrumentation: https://kubernetes.slack.com/archives/C20HH14P7/p1763542412547099
  • SIG Cluster Lifecycle: https://kubernetes.slack.com/archives/C13J86Z63/p1763542476489359
  • SIG Scalability: https://kubernetes.slack.com/archives/C09QZTRH7/p1763542531386279

graz-dev avatar Nov 19 '25 08:11 graz-dev

Second Outreach for Group 5 done:

SIG Storage: https://kubernetes.slack.com/archives/C09QZFCE5/p1763553374900169 SIG Apps: https://kubernetes.slack.com/archives/C18NZM5K9/p1763553420275369 SIG Windows: https://kubernetes.slack.com/archives/C0SJ4AFB7/p1763553491533159 SIG UI: https://kubernetes.slack.com/archives/C09R1JVU6/p1763553510321909

SwathiR03 avatar Nov 19 '25 12:11 SwathiR03

Second Outreach for Group 3 done:

  • SIG API Machinery: https://kubernetes.slack.com/archives/C0EG7JC6T/p1763559729309109
  • SIG Scheduling: https://kubernetes.slack.com/archives/C09TP78DV/p1763559810865059
  • SIG Autoscaling: https://kubernetes.slack.com/archives/C09R1LV8S/p1763559898061579
  • SIG Security: https://kubernetes.slack.com/archives/C019LFTGNQ3/p1763559993102309

chadmcrowell avatar Nov 19 '25 13:11 chadmcrowell

Second outreach for group 1 done:

  • SIG Node: https://kubernetes.slack.com/archives/C0BP8PW9G/p1763564525389329
  • SIG Cloud Provider: https://kubernetes.slack.com/archives/C718BPBQ8/p1763564609739469
  • SIG Architecture: https://kubernetes.slack.com/archives/C5P3FE08M/p1763564655710019
  • SIG Testing: https://kubernetes.slack.com/archives/C09QZ4DQB/p1763564691000849

arujjval avatar Nov 19 '25 15:11 arujjval

Second outreach for group 2 done:

  • SIG Auth: https://kubernetes.slack.com/archives/C0EN96KUY/p1763558677054299

  • SIG CLI: https://kubernetes.slack.com/archives/C2GL57FJ4/p1763565242740209

  • SIG K8s Infra: Opted Out as they don't have anything to highlight according to the slack thread

https://kubernetes.slack.com/archives/CCK68P2Q2/p1762532245072299?thread_ts=1762525565.326399&channel=CCK68P2Q2&message_ts=1762532245.072299

  • SIG Multicluster: https://kubernetes.slack.com/archives/C09R1PJR3/p1763558746481859

aakankshabhende avatar Nov 19 '25 15:11 aakankshabhende

Outreach for extras done:

  • SIG Release: https://kubernetes.slack.com/archives/C2C40FMNF/p1763675758447099
  • SIG Docs: https://kubernetes.slack.com/archives/C1J0BPD2M/p1763675883693369
  • SIG Contributor Experience: https://kubernetes.slack.com/archives/C1TU9EB9S/p1763675955586509
  • SIG etcd: https://kubernetes.slack.com/archives/C3HD8ARJ5/p1763675992887899

graz-dev avatar Nov 20 '25 22:11 graz-dev

Last call (tagging chairs) for missing SIGs:

  • SIG Auth: https://kubernetes.slack.com/archives/C0EN96KUY/p1764164210201299
  • SIG Architecture: https://kubernetes.slack.com/archives/C5P3FE08M/p1764163903678629
  • SIC Cli: https://kubernetes.slack.com/archives/C2GL57FJ4/p1764164526733329?thread_ts=1763565242.740209&cid=C2GL57FJ4
  • SIG Multicluster: https://kubernetes.slack.com/archives/C09R1PJR3/p1764164921403359?thread_ts=1763558746.481859&cid=C09R1PJR3
  • SIG Autoscaling: https://kubernetes.slack.com/archives/C09R1LV8S/p1764165057968699?thread_ts=1763559898.061579&cid=C09R1LV8S
  • SIG Security: https://kubernetes.slack.com/archives/C019LFTGNQ3/p1764165239703829?thread_ts=1763559993.102309&cid=C019LFTGNQ3
  • SIG Scalability: https://kubernetes.slack.com/archives/C09QZTRH7/p1764168652691329?thread_ts=1763542531.386279&cid=C09QZTRH7
  • SIG Apps: https://kubernetes.slack.com/archives/C18NZM5K9/p1764168802055429?thread_ts=1763553420.275369&cid=C18NZM5K9
  • SIG Window: https://kubernetes.slack.com/archives/C0SJ4AFB7/p1764168926758879?thread_ts=1763553491.533159&cid=C0SJ4AFB7
  • SIG UI: https://kubernetes.slack.com/archives/C09R1JVU6/p1764169052968419?thread_ts=1763553510.321909&cid=C09R1JVU6

graz-dev avatar Nov 26 '25 14:11 graz-dev

SIG Security confirmed nothing to share

https://kubernetes.slack.com/archives/C019LFTGNQ3/p1764809470907689?thread_ts=1763559993.102309&cid=C019LFTGNQ3

I've updated this issue description.

I've also reached out to the following SIGs, which are all overdue:

  • SIG Testing - https://kubernetes.slack.com/archives/C09QZ4DQB/p1764809286263029?thread_ts=1763564691.000849&cid=C09QZ4DQB
  • SIG Scalability - https://kubernetes.slack.com/archives/C09QZTRH7/p1764809086001219?thread_ts=1763542531.386279&cid=C09QZTRH7
  • SIG Auth - https://kubernetes.slack.com/archives/C0EN96KUY/p1764804018375909?thread_ts=1764164210.201299&cid=C0EN96KUY

drewhagen avatar Dec 04 '25 00:12 drewhagen