### SIG Scheduling

### SIG Cluster Lifecycle

  - apiserver_flowcontrol_latest_s: S(the request last dispatched) = R(when that request starts executing in the virtual world)
  - apiserver_flowcontrol_next_s_bounds: min and max next S among non-empty queues

pkg syscall (netbsd-arm64-cgo), const IPV6_MULTICAST_IF = 9
pkg syscall (netbsd-arm64-cgo), const IPV6_MULTICAST_LOOP = 11
pkg syscall (netbsd-arm64-cgo), const IPV6_NEXTHOP = 48
pkg syscall (netbsd-arm64-cgo), const IPV6_NEXTHOP ideal-int
pkg syscall (netbsd-arm64-cgo), const IPV6_PATHMTU = 44
pkg syscall (netbsd-arm64-cgo), const IPV6_PATHMTU ideal-int
pkg syscall (netbsd-arm64-cgo), const IPV6_PKTINFO = 46

- The metadata.clusterName field is deprecated. This field has always been unwritable and always blank, but its presence is confusing, so we will remove it next release. Out of an abundance of caution, this release we have merely changed the name in the go struct to ensure any accidental client uses are found before complete removal. ([#108717](https://github.com/kubernetes/kubernetes/pull/108717), [@lava...

Kubernetes releases are now generating provenance attestation files describing the staging and release phases of the release process and artifacts are verified as they are handed over from one phase to the next.
This final piece completes the work needed to comply with Level 1 of the [SLSA security framework](https://slsa.dev/) (Supply-chain Levels for Software Artifacts).

### IPv4/IPv6 Dual-stack Networking graduates to GA

    * Use feature gate `EnableAggregatedDiscoveryTimeout=false` if you *must* remove this check, but that feature gate will be removed next release.
* Graduating Windows GMSA support from alpha to beta ([#82110](https://github.com/kubernetes/kubernetes/pull/82110), [@wk8](https://github.com/wk8))

## 0.70.1

There's nothing interesting in this particular FastAPI release. It is mainly to enable/unblock the release of the next version of Pydantic that comes packed with features and improvements. 🤩

### Fixes

ster/cpu-management-policies/), which allows users to request exclusive CPU cores.  This helps performance in a variety of use-cases, including network latency sensitive applications, as well as applications that benefit from CPU cache residency.  Next, [Huge Pages](https://kubernetes.io/docs/tasks/manage-hugepages/scheduling-hugepages/), which allows pods to consume either 2Mi or 1Gi Huge Pages.  This benefits applications that consume large amounts of memory.  Use of Huge Pages is a common tuning...

- The mount-utils mounter now provides an option to limit the number of concurrent format operations....