SIG API Machinery implemented [warnings when using deprecated APIs](https://kubernetes.io/docs/reference/using-api/deprecation-policy/#rest-resources-aka-api-objects)
that are visible to `kubectl` users and API consumers, and metrics visible to cluster administrators.
Requests to a deprecated API are returned with a warning containing a target removal release and any replacement API.

### Feature

- Kubernetes is now built with Go 1.19.3 ([#113592](https://github.com/kubernetes/kubernetes/pull/113592), [@xmudrii](https://github.com/xmudrii)) [SIG Release and Testing]

### Bug or Regression

- Consider only plugin directory and not entire kubelet root when cleaning up mounts ([#112887](https://github.com/kubernetes/kubernetes/pull/112887), [@mattcary](https://github.com/mattcary)) [SIG Storage]

* Fixes a flaw (CVE-2019-11253) in json/yaml decoding where large or malformed documents could consume excessive server resources. Request bodies for normal API requests (create/delete/update/patch operations of regular resources) are now limited to 3MB. ([#83261](https://github.com/kubernetes/kubernetes/pull/83261), [@liggitt](https://github.com/liggitt))...

* Fix aggressive VM calls for Azure VMSS ([#83102](https://github.com/kubernetes/kubernetes/pull/83102), [@feiskyer](https://github.com/feiskyer))

- consumers of the 'certificatesigningrequests/approval' API must now have permission to 'approve' CSRs for the specific signer requested by the CSR. More information on the new signerName field and the required authorization can be found at https://kuberne...

- When the feature gates `PodDisruptionConditions` and `JobPodFailurePolicy` are both enabled,
  the Job controller now does not consider a terminating Pod (a pod that has a `.metadata.deletionTimestamp`)
  as a failure until that Pod is terminal (its `.status.phase` is `Failed` or `Succeeded`).
  

  - example manifests for the kube-apiserver, kube-controller-manager, kube-schedule, kubelet, and the cloud-controller-manager
  - labels/annotations that are consumed by any cloud specific controllers

In addition to the above, SIG Cloud Provider has been focusing on a long running effort to remove cloud provider code from kubernetes/kubernetes.

### SIG-cluster-lifecycle

- The `pod_scheduling_duration_seconds` metrics won't consider the time when a Pod fails PreEnqueue (like being gated). ([#118821](https://github.com/kubernetes/kubernetes/pull/118821), [@helayoty](https://github.com/helayoty)) [SIG Scheduling]

nttElement { G := sha3.NewShake128() G.Write(rho) G.Write([]byte{s, r}) var a nttElement var j int // index into a var buf [168]byte // buffered reads from B, matching the rate of SHAKE-128 off := len(buf) // index into buf, starts in a "buffer fully consumed" state for j < n { if off >= len(buf) { G.Read(buf[:]) off = 0 } v := uint32(buf[off]) | uint32(buf[off+1])<<8 | uint32(buf[off+2])<<16 off += 3 f, err := fieldToMontgomery(v & 0b01111111_11111111_11111111) // 23 bits if err != nil { continue } a[j]...

(dropped with a mask) and the leftmost bits are the least // significant bits (dropped with a right shift). var a nttElement var j int // index into a var buf [24]byte // buffered reads from B off := len(buf) // index into buf, starts in a "buffer fully consumed" state for { if off >= len(buf) { B.Read(buf[:]) off = 0 } d1 := byteorder.LEUint16(buf[off:]) & 0b1111_1111_1111 d2 := byteorder.LEUint16(buf[off+1:]) >> 4 off += 3 if d1 < q { a[j] = fieldElement(d1) j++ } if j >= len(a) { break } if d2 < q { a[j]...