<!-- BEGIN MUNGE: GENERATED_TOC -->
- [v1.11.10](#v11110)
  - [Downloads for v1.11.10](#downloads-for-v11110)
    - [Client Binaries](#client-binaries)
    - [Server Binaries](#server-binaries)
    - [Node Binaries](#node-binaries)
  - [Changelog since v1.11.9](#changelog-since-v1119)
    - [Other notable changes](#other-notable-changes)
- [v1.11.9](#v1119)
  - [Downloads for v1.11.9](#downloads-for-v1119)
    - [Client Binaries](#client-binaries-1)

<!-- BEGIN MUNGE: GENERATED_TOC -->
- [v1.13.12](#v11312)
  - [Downloads for v1.13.12](#downloads-for-v11312)
    - [Client Binaries](#client-binaries)
    - [Server Binaries](#server-binaries)
    - [Node Binaries](#node-binaries)
  - [Changelog since v1.13.11](#changelog-since-v11311)
    - [Other notable changes](#other-notable-changes)
- [v1.13.11](#v11311)
  - [Downloads for v1.13.11](#downloads-for-v11311)
    - [Client Binaries](#client-binaries-1)

    * 3. Maximum of two entries is allowed in `--service-cluster-ip-range` and they are validated to be dual stacked `i.e. --service-cluster-ip-range=<v4>,<v6> or --service-cluster-ip-range=<v6>,<v4>`
    * 4. Max 20 bit for range (min network bits `<v6>/108` or <v4>/12)

### Avoiding Collisions in IP allocation to Services

Kubernetes 1.24 introduced a new opt-in feature that allows you to
[soft-reserve a range for static IP address assignments](https://kubernetes.io/docs/concepts/services-networking/service/#service-ip-static-sub-range)
to Services.
With the manual enablement of this feature, the cluster will prefer automatic assignment from

<!-- BEGIN MUNGE: GENERATED_TOC -->

- [v1.20.15](#v12015)
  - [Downloads for v1.20.15](#downloads-for-v12015)
    - [Source Code](#source-code)
    - [Client Binaries](#client-binaries)
    - [Server Binaries](#server-binaries)
    - [Node Binaries](#node-binaries)
  - [Changelog since v1.20.14](#changelog-since-v12014)
  - [Changes by Kind](#changes-by-kind)
    - [Bug or Regression](#bug-or-regression)
  - [Dependencies](#dependencies)

### Promoted endPort in Network Policy to Stable

Promoted `endPort` in [Network Policy](https://kubernetes.io/docs/concepts/services-networking/network-policies/#targeting-a-range-of-ports) to GA. Network Policy providers that support `endPort` field now can use it to specify a range of ports to apply a Network Policy. Previously, each Network Policy could only target a single port.

<!-- BEGIN MUNGE: GENERATED_TOC -->

- [v1.22.17](#v12217)
  - [Downloads for v1.22.17](#downloads-for-v12217)
    - [Source Code](#source-code)
    - [Client Binaries](#client-binaries)
    - [Server Binaries](#server-binaries)
    - [Node Binaries](#node-binaries)
    - [Container Images](#container-images)
  - [Changelog since v1.22.16](#changelog-since-v12216)
  - [Changes by Kind](#changes-by-kind)
    - [Feature](#feature)

pkg syscall (netbsd-arm64-cgo), const SYS_FSYNC = 95
pkg syscall (netbsd-arm64-cgo), const SYS_FSYNC ideal-int
pkg syscall (netbsd-arm64-cgo), const SYS_FSYNC_RANGE = 354
pkg syscall (netbsd-arm64-cgo), const SYS_FSYNC_RANGE ideal-int
pkg syscall (netbsd-arm64-cgo), const SYS_FTRUNCATE = 201
pkg syscall (netbsd-arm64-cgo), const SYS_FTRUNCATE ideal-int
pkg syscall (netbsd-arm64-cgo), const SYS_FUTIMENS = 472

<!-- BEGIN MUNGE: GENERATED_TOC -->

- [v1.23.17](#v12317)
  - [Downloads for v1.23.17](#downloads-for-v12317)
    - [Source Code](#source-code)
    - [Client Binaries](#client-binaries)
    - [Server Binaries](#server-binaries)
    - [Node Binaries](#node-binaries)
    - [Container Images](#container-images)
  - [Changelog since v1.23.16](#changelog-since-v12316)
  - [Changes by Kind](#changes-by-kind)
    - [Feature](#feature)

* When using IP aliases, use a secondary range rather than subnetwork to reserve cluster IPs. ([#51690](https://github.com/kubernetes/kubernetes/pull/51690), [@bowei](https://github.com/bowei))
* IPAM controller unifies handling of node pod CIDR range allocation. ([#51374](https://github.com/kubernetes/kubernetes/pull/51374), [@bowei](https://github.com/bowei))