- The metrics `container_cpu_load_average_10s`, `container_cpu_load_d_average_10s`, and `cpu_tasks_state` have been dropped from the reported metrics by cadvisor. This is done because the values were always 0, because a flag was not enabled in the kubelet. ([#134981](https://github.com/kubernetes/kubernetes/pull/134981), [@haircommander](https://github.com/haircommander))...

pkg syscall (freebsd-arm64), const WNOHANG ideal-int
pkg syscall (freebsd-arm64), const WNOWAIT = 8
pkg syscall (freebsd-arm64), const WNOWAIT ideal-int
pkg syscall (freebsd-arm64), const WSTOPPED = 2
pkg syscall (freebsd-arm64), const WSTOPPED ideal-int
pkg syscall (freebsd-arm64), const WTRAPPED = 32
pkg syscall (freebsd-arm64), const WTRAPPED ideal-int
pkg syscall (freebsd-arm64), const WUNTRACED = 2

pkg syscall (darwin-arm64), const WNOWAIT ideal-int
pkg syscall (darwin-arm64), const WORDSIZE = 64
pkg syscall (darwin-arm64), const WORDSIZE ideal-int
pkg syscall (darwin-arm64), const WSTOPPED = 8
pkg syscall (darwin-arm64), const WSTOPPED ideal-int
pkg syscall (darwin-arm64), const WUNTRACED = 2
pkg syscall (darwin-arm64), const WUNTRACED ideal-int
pkg syscall (darwin-arm64), func Accept(int) (int, Sockaddr, error)

pkg syscall (freebsd-riscv64), const WNOWAIT = 8 #53466
pkg syscall (freebsd-riscv64), const WNOWAIT ideal-int #53466
pkg syscall (freebsd-riscv64), const WSTOPPED = 2 #53466
pkg syscall (freebsd-riscv64), const WSTOPPED ideal-int #53466
pkg syscall (freebsd-riscv64), const WTRAPPED = 32 #53466
pkg syscall (freebsd-riscv64), const WTRAPPED ideal-int #53466
pkg syscall (freebsd-riscv64), const WUNTRACED = 2 #53466

this._handleSwipe()\n      if (this._config.pause === 'hover') {\n        // If it's a touch-enabled device, mouseenter/leave are fired as\n        // part of the mouse compatibility events on first tap - the carousel\n        // would stop cycling until user tapped out of it;\n        // here, we listen for touchend, explicitly pause the carousel\n        // (as if it's the second time we tap on it, mouseenter compat event\n        // is NOT fired) and after a timeout (to allow for mouse compatibility\n    ...

- kube-scheduler dropped support for configuration files with apiVersion `componentconfig/v1alpha1`. Ensure kube-scheduler is configured using command-line flags or a configuration file with apiVersion `kubescheduler.config.k8s.io/v1alpha1` before upgrading to 1.13.

(this._config.pause !== 'hover') {\n        return\n      }\n\n      // If it's a touch-enabled device, mouseenter/leave are fired as\n      // part of the mouse compatibility events on first tap - the carousel\n      // would stop cycling until user tapped out of it;\n      // here, we listen for touchend, explicitly pause the carousel\n      // (as if it's the second time we tap on it, mouseenter compat event\n      // is NOT fired) and after a timeout (to allow for mouse compatibility\n      // events...

- Dropped support for the Container Runtime Interface (CRI) version `v1alpha2`, which means that container runtimes just have to implement `v1`. ([#110618](https://github.com/kubernetes/kubernetes/pull/110618), [@saschagrunert](https://github.com/saschagrunert))...

- Kube-proxy in nftables mode now allows pods on nodes without local service endpoints to access LoadBalancer Service ExternalIPs (with `externalTrafficPolicy: Local`). Previously, such traffic was dropped. This change brings nftables mode in line with iptables and IPVS modes, allowing traffic to be forwarded to available endpoints elsewhere in the cluster. ([#133969](https://github.com/kubernetes/kubernetes/pull/133969), [@aroradaman](https://github.com/aroradaman))...

* Fixed an issue with informers missing an `Added` event if a recently deleted object was immediately recreated at the same time the informer dropped a watch and relisted. ([#83911](https://github.com/kubernetes/kubernetes/pull/83911), [@matte21](https://github.com/matte21))