- [KCCM - service controller]: enabled connection draining for terminating pods upon node downscale by the cluster autoscaler. This is done by not reacting to the taint used by the cluster autoscaler to indicate that the node is going away soon, thus keeping the node referenced by the load balancer until the VM has been completely deleted. ([#115204](https://github.com/kubernetes/kubernetes/pull/115204), [@alexanderConstantinescu](https://github.com/alexanderConstantinescu))

- When `SchedulerQueueingHints` is enabled, clear events cached in the scheduling queue as soon as possible so that the scheduler consumes less memory. ([#120586](https://github.com/kubernetes/kubernetes/pull/120586), [@sanposhiho](https://github.com/sanposhiho)) [SIG Scheduling]

  * Caveat: The alpha version no longer supports, and the beta version does not support, the "empty `podAffinityTerm.namespaces` list means all namespaces" behavior. In both alpha and beta it now means "same namespace as the pod...

  - in cases where the client specifies a timeout in the request URL, the overall request deadline is shortened now since the deadline is setup as soon as the request is received by the apiserver. ([#96901](https://github.com/kubernetes/kubernetes/pull/96901), [@tkashem](https://github.com/tkashem)) [SIG API Machinery and Testing]

      (rather than continuing until the endpoint is fully deleted).
  
    - Traffic to a service IP now starts getting rejected (as opposed to
      merely dropped) as soon as there are no longer any *usable*
      endpoints, rather than waiting until all of the terminating
      endpoints have terminated even when those terminating endpoints
      were not being used.
  

  as a failure until that Pod is terminal (its `.status.phase` is `Failed` or `Succeeded`).
  
  However, the Job controller creates a replacement Pod as soon as the termination becomes apparent.
  Once the pod terminates, the Job controller evaluates `.backoffLimit` and `.podFailurePolicy` for the
  relevant Job, taking this now-terminated Pod into consideration.
  

entering // the "error state") if the self-test fails. // // CASTs are mandatory self-checks that must be performed by FIPS 140-3 modules // before the algorithm is used. See Implementation Guidance 10.3.A. // // The name must not contain commas, colons, hashes, or equal signs. // // If a package p calls CAST from its init function, an import of p should also // be added to crypto/internal/fips140test. If a package p calls CAST on the first // use of the algorithm, an invocation of that algorithm...

entering // the "error state") if the self-test fails. // // CASTs are mandatory self-checks that must be performed by FIPS 140-3 modules // before the algorithm is used. See Implementation Guidance 10.3.A. // // The name must not contain commas, colons, hashes, or equal signs. // // If a package p calls CAST from its init function, an import of p should also // be added to crypto/internal/fips140test. If a package p calls CAST on the first // use of the algorithm, an invocation of that algorithm...

Agreement and does not cure such failure in a reasonable period of
time after becoming aware of such noncompliance. If all Recipient's
rights under this Agreement terminate, Recipient agrees to cease use
and distribution of the Program as soon as reasonably practicable.
However, Recipient's obligations under this Agreement and any licenses
granted by Recipient relating to the Program shall continue and survive.