using ethtool to disable checksum offload on your primary network interface, you should
  now be able to stop doing that. ([#92035](https://github.com/kubernetes/kubernetes/pull/92035), [@danwinship](https://github.com/danwinship)) [SIG Network and Node]

  using ethtool to disable checksum offload on your primary network interface, you should
  now be able to stop doing that. ([#92035](https://github.com/kubernetes/kubernetes/pull/92035), [@danwinship](https://github.com/danwinship)) [SIG Network and Node]

America/Port-au-Prince America/Port_of_Spain America/Porto_Acre America/Porto_Velho America/Puerto_Rico America/Punta_Arenas America/Rainy_River America/Rankin_Inlet America/Recife America/Regina America/Resolute America/Rio_Branco America/Rosario America/Santa_Isabel America/Santarem America/Santiago America/Santo_Domingo America/Sao_Paulo America/Scoresbysund America/Shiprock America/Sitka America/St_Barthelemy America/St_Johns America/St_Kitts America/St_Lucia America/St_Thomas America/St_Vincent America/Swift_Current...

- Overall, enable the feature of `PreferNominatedNode` will  improve the performance of scheduling where preemption might frequently happen, but in theory, enable the feature of `PreferNominatedNode`, the pod might not be scheduled to the best candidate node...

for resizing existing persistent volumes.

### NonPreemptingPriority to Stable

This feature adds [a new option to PriorityClasses](https://github.com/kubernetes/enhancements/issues/902),
which can enable or disable pod preemption.

### Storage Plugin Migration

pkg syscall (darwin-arm64), const EV_DELETE ideal-int
pkg syscall (darwin-arm64), const EV_DISABLE = 8
pkg syscall (darwin-arm64), const EV_DISABLE ideal-int
pkg syscall (darwin-arm64), const EV_DISPATCH = 128
pkg syscall (darwin-arm64), const EV_DISPATCH ideal-int
pkg syscall (darwin-arm64), const EV_ENABLE = 4
pkg syscall (darwin-arm64), const EV_ENABLE ideal-int
pkg syscall (darwin-arm64), const EV_EOF = 32768

// ---
// New uses of this type are discouraged because of difficulty describing its usage when embedded in APIs.
//  1. Ignored fields.  It includes many fields which are not generally honored.  For instance, ResourceVersion and FieldPath are both very rarely valid in actual usage.
//  2. Invalid usage help.  It is impossible to add specific help for individual usage.  In most embedded usages, there are particular

     * -Dio.netty.noKeySetOptimization=true<br>
     * -Dio.netty.recycler.maxCapacityPerThread=0<br>
     * -Dlog4j.shutdownHookEnabled=false<br>
     * -Dlog4j2.formatMsgNoLookups=true<br>
     * -Dlog4j2.disable.jmx=true<br>
     * -Dlog4j.skipJansi=true<br>
     * -Dsun.java2d.cmm=sun.java2d.cmm.kcms.KcmsServiceProvider<br>
     * -Dorg.apache.pdfbox.rendering.UsePureJavaCMYKConversion=true<br>
     *  */

is disabled by default). An API server fronted by an L7 load balancer that already mitigates these http/2 attacks may choose not to enable the kube-apiserver mitigation to avoid disrupting load balancer → kube-apiserver connections if http/2 requests from multiple clients share the same backend connection. An API server on a private network may choose not to enable the kube-apiserver mitigation to prevent performance regressions for unauthenticated clients. Authenticated requests rely on the fix...

	    and a signed binary exponent of at least 16 bits.</li>

	<li>Give an error if unable to represent an integer constant
	    precisely.</li>

	<li>Give an error if unable to represent a floating-point or
	    complex constant due to overflow.</li>

	<li>Round to the nearest representable constant if unable to
	    represent a floating-point or complex constant due to limits
	    on precision.</li>
</ul>