pkg syscall (netbsd-arm64-cgo), const F_OK = 0
pkg syscall (netbsd-arm64-cgo), const F_OK ideal-int
pkg syscall (netbsd-arm64-cgo), const F_PARAM_MASK = 4095
pkg syscall (netbsd-arm64-cgo), const F_PARAM_MASK ideal-int
pkg syscall (netbsd-arm64-cgo), const F_PARAM_MAX = 4095
pkg syscall (netbsd-arm64-cgo), const F_PARAM_MAX ideal-int
pkg syscall (netbsd-arm64-cgo), const F_RDLCK = 1

pkg syscall (darwin-arm64), const SO_REUSESHAREUID = 4133
pkg syscall (darwin-arm64), const SO_REUSESHAREUID ideal-int
pkg syscall (darwin-arm64), const SO_SNDBUF = 4097
pkg syscall (darwin-arm64), const SO_SNDLOWAT = 4099
pkg syscall (darwin-arm64), const SO_SNDLOWAT ideal-int
pkg syscall (darwin-arm64), const SO_SNDTIMEO = 4101
pkg syscall (darwin-arm64), const SO_SNDTIMEO ideal-int

* Fixed issues ([#39202](https://github.com/kubernetes/kubernetes/pull/39202)), ([#41041](https://github.com/kubernetes/kubernetes/pull/41041)) and ([#40941](https://github.com/kubernetes/kubernetes/pull/40941)) that caused the iSCSI connections to

with this, and the default behavior was changed. The `VolumeCapacityPriority` preferred a node with the least allocatable, but the `StorageCapacityScoring` preferred a node with the maximum allocatable. See [KEP-4049](https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/4049-storage-capacity-scoring-of-nodes-for-dynamic-provisioning/README.md) for details. ([#128184](https://github.com/kubernetes/kubernetes/pull/128184), [@cupnes](https://github.com/cupnes)) [SIG Scheduling, Storage...

- The 404 request handler for the GCE Ingress load balancer now exports prometheus metrics, including:

  - `http_404_request_total` (the number of 404 requests handled)
  - `http_404_request_duration_ms` (the amount of time the server took to respond in ms)

* The formerly publicly-available cAdvisor web UI that the kubelet ran on port 4194 by default is now turned off by default. The flag configuring what port to run this UI on `--cadvisor-port` was deprecated in v1.10. Now the default is `--cadvisor-port=0`, in other words, to not run the web server. If you still need to run cAdvisor,...

- Resolves a potential issue with GC and NS controllers which may delete objects after getting a 404 response from the server during its startup. This PR ensures that requests to aggregated APIs will get 503, not 404 while the APIServiceRegistrationController hasn't finished its job. ([#104748](https://github.com/kubernetes/kubernetes/pull/104748), [@p0lyn0mial](https://github.com/p0lyn0mial))

* kube-apiserver: requests to endpoints handled by unavailable extension API servers (as indicated by an `Available` condition of `false` in the registered APIService) now return `503` errors instead of `404` errors. ([#58070](https://github.com/kubernetes/kubernetes/pull/58070), [@weekface](https://github.com/weekface))

* When a namespace is being deleted and spec.finalizers are still being processed, stop returning a 409 conflict error and instead return the object as we would during metadata.finalizer processing. ([#84122](https://github.com/kubernetes/kubernetes/pull/84122), [@smarterclayton](https://github.com/smarterclayton))

* Ensure Azure load balancer cleaned up on 404 or 403 when deleting LoadBalancer services. ([#75256](https://github.com/kubernetes/kubernetes/pull/75256), [@feiskyer](https://github.com/feiskyer))



# v1.14.0-beta.2

[Documentation](https://docs.k8s.io)