- The deprecated flag `--hard-pod-affinity-symmetric-weight` and `--scheduler-name` have been removed from `kube-scheduler`. Use `ComponentConfig` instead to configure those parameters. ([#102805](https://github.com/kubernetes/kubernetes/pull/102805), [@ahg-g](https://github.com/ahg-g))

pkg syscall (freebsd-arm64), type RtMetrics struct, Sendpipe uint64
pkg syscall (freebsd-arm64), type RtMetrics struct, Ssthresh uint64
pkg syscall (freebsd-arm64), type RtMetrics struct, Weight uint64
pkg syscall (freebsd-arm64), type RtMsghdr struct
pkg syscall (freebsd-arm64), type RtMsghdr struct, Addrs int32
pkg syscall (freebsd-arm64), type RtMsghdr struct, Errno int32

- Kube-proxy service health returns http header `X-Load-Balancing-Endpoint-Weight` with number of local endpoints. The same information is still available in response body JSON `payload.LocalEndpoints`. ([#118999](https://github.com/kubernetes/kubernetes/pull/118999), [@cezarygerard](https://github.com/cezarygerard))

    * b. kubectl get pod test-pod -o custom-columns=CONTAINER:.spec.containers[-2:].name
* scheduler: use incremental scheduling cycle in PriorityQueue to put all in-flight unschedulable pods back to active queue if we received move request ([#73309](https://github.com/kubernetes/kubernetes/pull/73309), [@cofyc](https://github.com/cofyc))

pkg syscall (freebsd-riscv64), type RtMetrics struct, Sendpipe uint64 #53466
pkg syscall (freebsd-riscv64), type RtMetrics struct, Ssthresh uint64 #53466
pkg syscall (freebsd-riscv64), type RtMetrics struct, Weight uint64 #53466
pkg syscall (freebsd-riscv64), type RtMsghdr struct #53466
pkg syscall (freebsd-riscv64), type RtMsghdr struct, Addrs int32 #53466
pkg syscall (freebsd-riscv64), type RtMsghdr struct, Errno int32 #53466

* scheduler: use incremental scheduling cycle in PriorityQueue to put all in-flight unschedulable pods back to active queue if we received move request ([#73309](https://github.com/kubernetes/kubernetes/pull/73309), [@cofyc](https://github.com/cofyc))

  After the connection closed(received GOAWAY), the client's other in-flight requests won't be affected, and the client will reconnect. 
  The flag min value is 0 (off), max is .02 (1/50 requests); .001 (1/1000) is a recommended starting point.

    Potential impacts:

    <!-- conflict with application/x-font-ghostscript
    <glob pattern="*.gsf"/> -->
    <glob pattern="*.gslib"/>
    <glob pattern="*.minigsf"/>
  </mime-type>
  <mime-type type="audio/x-sap">
    <_comment>Slight Atari Player</_comment>
    <tika:link>https://asap.sourceforge.net/sap-format.html</tika:link>
    <magic priority="50">
      <match value="SAP\r\n" type="string" offset="0"/>
    </magic>

* scheduler: use incremental scheduling cycle in PriorityQueue to put all in-flight unschedulable pods back to active queue if we received move request ([#73309](https://github.com/kubernetes/kubernetes/pull/73309), [@cofyc](https://github.com/cofyc))