Potential impacts:
    If an SLO/alert has been defined based on `volume_operation_total_seconds`, it might get violated because of the more accurate metric might be significantly larger than previously reported. The metric is defined to be a histogram and the new semantic could change the distribution. ([#78061](https://github.com/kubernetes/kubernetes/pull/78061), [@yuxiangqian](https://github.com/yuxiangqian))

* fix smb remount issue on Windows ([#73661](https://github.com/kubernetes/kubernetes/pull/73661), [@andyzhangx](https://github.com/andyzhangx))
* kube-apiserver: a request body of a CREATE/UPDATE/PATCH/DELETE resource operation larger than 100 MB will return a 413 "request entity too large" error. ([#73805](https://github.com/kubernetes/kubernetes/pull/73805), [@caesarxuchao](https://github.com/caesarxuchao))

non-zero. If GCDVarTime returns an error, x is not modified. // // The output will be resized to the size of the larger of a and b. func (x *Nat) GCDVarTime(a, b *Nat) (*Nat, error) { u, _, err := extendedGCD(a, b) if err != nil { return nil, err } return x.set(u), nil } // extendedGCD computes u and A such that a = GCD(a, m) and u = A*a - B*m. // // u will have the size of the larger of a and m, and A will have the size of m. // // It is an error if either a or m is zero, or if they are both even....

*   Unified eager and `tf.function` execution:

    *   Eager mode can now execute each op as a `tf.function`, allowing for more
        consistent feature support in future releases.
    *   It is available for immediate use.
        *   See the `TF_RUN_EAGER_OP_AS_FUNCTION` environment variable in

are non-zero. If GCDVarTime returns an error, x is not modified. // // The output will be resized to the size of the larger of a and b. func (x *Nat) GCDVarTime(a, b *Nat) (*Nat, error) { u, _, err := extendedGCD(a, b) if err != nil { return nil, err } return x.set(u), nil } // extendedGCD computes u and A such that u = GCD(a, m) = A*a - B*m. // // u will have the size of the larger of a and m, and A will have the size of m. // // It is an error if either a or m is zero, or if they are both even....

* kube-apiserver: a request body of a CREATE/UPDATE/PATCH/DELETE resource operation larger than 100 MB will return a 413 "request entity too large" error. ([#73805](https://github.com/kubernetes/kubernetes/pull/73805), [@caesarxuchao](https://github.com/caesarxuchao))

- Kubernetes 1.24 bumped version of golang it is compiled with to go1.18, which introduced significant changes to its garbage collection algorithm. As a result, we observed an increase in memory usage for kube-apiserver in larger an heavily loaded clusters up to ~25% (with the benefit of API call latencies drop by up to 10x on 99th percentiles). If the memory increase is not acceptable for you you can mitigate by setting GOGC env variable (for our tests using GOGC=63 brings...

- Introduce minReadySeconds api to the StatefulSets. ([#100842](https://github.com/kubernetes/kubernetes/pull/100842), [@ravisantoshgudimetla](https://github.com/ravisantoshgudimetla)) [SIG API Machinery, Apps and Testing]