Additionally, since the information returned from the discovery APIs may change dynamically, a cache of the results should not be considered authoritative.
ETag support is planned in a future version to facilitate client caching.
([#47977](https://github.com/kubernetes/kubernetes/pull/47977), [#44957](https://github.com/kubernetes/kubernetes/pull/44957))

- The CSINodeInfo feature gate is deprecated and will be removed in a future release. The storage.k8s.io/v1beta1 CSINode object is deprecated and will be removed in a future release. ([#83474](https://github.com/kubernetes/kubernetes/pull/83474), [@msau42](https://github.com/msau42))

  * Caveat: The alpha version no longer supports, and the beta version does not support, the "empty `podAffinityTerm.namespaces` list means all namespaces" behavior....

  will now create a Lease in the `kube-system` namespace. These lease objects can
  be used to identify the number of active API servers in the cluster, and may also
  be used for future features such as the Storage Version API.'
   ([#113629](https://github.com/kubernetes/kubernetes/pull/113629), [@andrewsykim](https://github.com/andrewsykim))
- 'The iptables kube-proxy backend now process service/endpoint changes

- Service session affinity timeout tests are no longer required for Kubernetes network plugin conformance due to variations in existing implementations. New conformance tests will be developed to better express conformance in future releases. ([#112806](https://github.com/kubernetes/kubernetes/pull/112806), [@dcbw](https://github.com/dcbw)) [SIG Architecture, Network and Testing]

## Dependencies

### Added
_Nothing has changed._

To simplify the code base, several [logging flags got marked as deprecated](https://kubernetes.io/docs/concepts/cluster-administration/system-logs/#klog) in Kubernetes 1.23.
The code which implements them will be removed in a future release, so users of those need to start replacing the deprecated flags with some alternative solutions.

### Software Supply Chain SLSA Level 1 Compliance in the Kubernetes Release Process

pkg syscall (darwin-arm64), const MAP_SHARED ideal-int
pkg syscall (darwin-arm64), const MCL_CURRENT = 1
pkg syscall (darwin-arm64), const MCL_CURRENT ideal-int
pkg syscall (darwin-arm64), const MCL_FUTURE = 2
pkg syscall (darwin-arm64), const MCL_FUTURE ideal-int
pkg syscall (darwin-arm64), const MSG_CTRUNC = 32
pkg syscall (darwin-arm64), const MSG_CTRUNC ideal-int
pkg syscall (darwin-arm64), const MSG_DONTROUTE = 4

pkg syscall (netbsd-arm64-cgo), const MCL_CURRENT = 1
pkg syscall (netbsd-arm64-cgo), const MCL_CURRENT ideal-int
pkg syscall (netbsd-arm64-cgo), const MCL_FUTURE = 2
pkg syscall (netbsd-arm64-cgo), const MCL_FUTURE ideal-int
pkg syscall (netbsd-arm64-cgo), const MS_ASYNC = 1
pkg syscall (netbsd-arm64-cgo), const MS_ASYNC ideal-int
pkg syscall (netbsd-arm64-cgo), const MSG_BCAST = 256

- [`KT-56169`](https://youtrack.jetbrains.com/issue/KT-56169) False negative deprecation warning about future inference error with builder inference
- [`KT-56657`](https://youtrack.jetbrains.com/issue/KT-56657) K1/K2: inconsistent behavior in nullability mismatch (Guava hash set/map)

	At most one of the type parameters has a known type argument.
	In this case, the type parameters are <i>joined</i>:
	they both stand for the same type argument.
	If neither type parameter has a known type argument yet,
	a future type argument inferred for one the type parameters
	is simultaneously inferred for both of them.
</li>
<li>
	Both type parameters have a known type argument