pkg syscall (darwin-arm64), const SO_WANTOOBFLAG ideal-int
pkg syscall (darwin-arm64), const SYS_ACCEPT = 30
pkg syscall (darwin-arm64), const SYS_ACCEPT ideal-int
pkg syscall (darwin-arm64), const SYS_ACCEPT_NOCANCEL = 404
pkg syscall (darwin-arm64), const SYS_ACCEPT_NOCANCEL ideal-int
pkg syscall (darwin-arm64), const SYS_ACCESS = 33
pkg syscall (darwin-arm64), const SYS_ACCESS ideal-int

- [`KTIJ-25448`](https://youtrack.jetbrains.com/issue/KTIJ-25448) When project JDK is less than one defines in jvmToolchain block, run with Idea fails with `has been compiled by a more recent version of the Java Runtime`
- [`KT-60603`](https://youtrack.jetbrains.com/issue/KT-60603) K2: Investigate intellij tests failures in branch 2.0

no longer be valid. You must correct these files before upgrading.** When specifying keys in JSON resource definitions during direct API server communication, the keys are case-sensitive. A bug introduced in Kubernetes 1.8 caused the API server to accept a request with incorrect case and coerce it to correct case, but this behaviour has been fixed in 1.11 and the API server will once again be enforcing the correct case. It’s worth noting that during this time, the `kubectl` tool continued to enforce...

- kubeadm: make the command "kubeadm alpha kubeconfig user" accept a "--config" flag and remove the following flags:
  - apiserver-advertise-address / apiserver-bind-port: use either localAPIEndpoint from InitConfiguration or controlPlaneEndpoint from ClusterConfiguration.

pkg syscall (netbsd-arm64-cgo), const SO_USELOOPBACK = 64
pkg syscall (netbsd-arm64-cgo), const SO_USELOOPBACK ideal-int
pkg syscall (netbsd-arm64-cgo), const SYS_ACCEPT = 30
pkg syscall (netbsd-arm64-cgo), const SYS_ACCEPT ideal-int
pkg syscall (netbsd-arm64-cgo), const SYS_ACCESS = 33
pkg syscall (netbsd-arm64-cgo), const SYS_ACCESS ideal-int
pkg syscall (netbsd-arm64-cgo), const SYS_ACCT = 51

ull/102344) leading to early shutdown, resource leaks, or long delays in actually completing pod shutdown. As a consequence of this change the Kubelet now correctly takes into account the resources of running and terminating pods when deciding to accept new pods, since terminating pods are still holding on to those resources. This stricter handling may surface to end users as pod rejections when creating pods that are scheduled to mostly full nodes that have other terminating pods holding the resources...

- Changes behaviour of kube-proxy start; does not attempt to set specific `sysctl` values (which does not work in recent Kernel versions anymore in non-init namespaces), when the current sysctl values are already set higher. ([#103174](https://github.com/kubernetes/kubernetes/pull/103174), [@Napsty](https://github.com/Napsty))

  Ginkgo V2 doesn't accept go test's `-parallel` flags to parallelize Ginkgo specs, please switch to use `ginkgo -p` or `ginkgo -procs=N` instead. ([#109111](https://github.com/kubernetes/kubernetes/pull/109111), [@chendave](https://github.com/chendave)) [SIG API Machinery,...

    * loading a -viper-config=e2e.yaml with suffix (introduced in 1.13) works again and now has a regression test

<table>
  <tr>
    <td>previous</td>
    <td>now</td>
  </tr>
  <tr>
    <td>GET /swagger.json</td>
    <td>GET /openapi/v2
Accept: application/json</td>
  </tr>
  <tr>
    <td>GET /swagger-2.0.0.pb-v1</td>
    <td>GET /openapi/v2
Accept: application/com.github.proto-openapi.spec.v2@v1.0+protobuf</td>