v1.27 Kubernetes Major Themes contact

[harshanarayana]

The release notes team will use this issue to track the work on nudging SIGs for entries on major themes for the v1.27 release cycle.

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

Following is a bootstrap template that you can use to reach out to the individual sigs informing them about the Major Themes collection discussion thread.

Hello SIG <sig-name>,

Major themes are an essential part of the Kubernetes release cycle as they provide a birds eye view of major improvements that are coming as part of the upcoming release. 

As part of the effort aimed towards collecting the Major themes for the  v1.27 cycle, release notes team is working towards gathering major themes entries. If you have anything to call out, we would appreciate it if your SIG can submit the content in
[Kubernetes 1.27 Major Themes GitHub discussion](https://github.com/kubernetes/sig-release/discussions/2166)

Ideally, we would like this to be completed by **Tuesday 21st March 2023**.

Thanks!

It would be great if we would propose some Major Themes candidates when nudging SIGs based on tracked enhancements. Please feel free to tag the enhancement owner from each SIG to make sure they want it to be included in Major Themes.

Some SIGs have activities that aren't quite coupled with Kubernetes releases, but it's worth checking anyway in case there are things worth calling out in what they did between the previous release and the current release. One example is Immutable Secrets and ConfigMaps from the 1.21 release or Dockershim removal from 1.24.

We'll try to keep the list below up-to-date, but please double-check in the comments if someone has contacted their channel:

• [ ] API Machinery
• [ ] Apps
• [ ] Architecture
• [ ] Auth
• [ ] Autoscaling
• [ ] CLI
• [ ] Cloud Provider
• [ ] Cluster Lifecycle
• [ ] Contributor Experience
• [ ] Docs
• [ ] Instrumentation
• [ ] Multicluster
• [ ] Network
• [ ] Node
• [ ] Release
• [ ] Scalability
• [ ] Scheduling
• [ ] Security
• [ ] Storage
• [ ] Testing
• [ ] UI
• [ ] Usability
• [ ] Windows
• [ ] K8s Infra

/assign @AnaMMedina21 @harshanarayana @rjsadow @sanchita-07 @yrs147

/milestone v1.27

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

[harshanarayana]

I will reach out to the following SIGs.

• [x] API Machinery
• [x] Apps
• [x] Architecture
• [x] Auth
• [x] Autoscaling

[rjsadow]

I'll reach out to

• [x] CLI
• [x] Cloud Provider
• [x] Cluster Lifecycle
• [x] Node
• [x] Testing

[yrs147]

I'll reach out to the following SIGs:-

• [x] Docs
• [x] Storage
• [x] Scalability
• [x] Network
  • [x] Release

[sanchita-07]

I'll reach out to the following SIGs:-

• [x] Multicluster
• [x] Security
• [x] Scheduling
• [x] Contributor Experience
• [x] K8s Infra

[AnaMMedina21]

I'll reach out to the SIGs left:

• [x] Instrumentation
• [x] UI
• [x] Usability
• [x] Windows

[harshanarayana]

The purpose of this tracking issue is now done. Can be closed.

/close

[k8s-ci-robot]

@harshanarayana: Closing this issue.

In response to [this](https://github.com/kubernetes/sig-release/issues/2167#issuecomment-1502292504): >The purpose of this tracking issue is now done. Can be closed. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.