- Fix endpoints status out-of-sync when the pod state changes rapidly ([#125675](https://github.com/kubernetes/kubernetes/pull/125675), [@tnqn](https://github.com/tnqn)) [SIG Apps, Network and Testing]
- For statically provisioned PVs, if its volume source is CSI type or it has migrated annotation, when it's deleted, the PersisentVolume controller won't changes its phase to the Failed state. 
  

## Before Upgrading

* When Response is a `metav1.Status`, it is no longer copied into the audit.Event status. Only the "status", "reason" and "code" fields are set.  For example, when we run `kubectl get pods abc`, the API Server returns a status object:

- Fix endpoints status out-of-sync when the pod state changes rapidly ([#125675](https://github.com/kubernetes/kubernetes/pull/125675), [@tnqn](https://github.com/tnqn)) [SIG Apps, Network and Testing]
- For statically provisioned PVs, if its volume source is CSI type or it has migrated annotation, when it's deleted, the PersisentVolume controller won't changes its phase to the Failed state. 
  

### **Application Autoscaling**
#### Horizontal Pod Autoscaler
* [alpha] [HPA Status Conditions](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough/#appendix-horizontal-pod-autoscaler-status-conditions).


### **Cluster Lifecycle**
#### kubeadm

*.cloudera.site
*.cn-north-1.airflow.amazonaws.com.cn
*.cn-northwest-1.airflow.amazonaws.com.cn
*.cns.joyent.com
*.code.run
*.compute-1.amazonaws.com
*.compute.amazonaws.com
*.compute.amazonaws.com.cn
*.compute.estate
*.cryptonomic.net
*.customer-oci.com
*.d.crm.dev
*.database.run
*.dev-builder.code.com
*.dev.adobeaemcloud.com
*.developer.app
*.digitaloceanspaces.com
*.dweb.link
*.elb.amazonaws.com

-73.863739013671875 40.732749938964844 -73.76513671875 40.718353271484375 3 6.70 20.5 0.5 0.5 0 0 21.5 1 196 131 green 0.04 0.0 0.0 62 37 5.37 1288 717.02 4 Queens 071702 4071702 I QN18 Rego Park 4108 1380 478 4 Queens 047800 4047800 I QN06 Jamaica Estates-Holliswood 4106 3389335 2 2014-03-15 17:23:01 2014-03-15 17:32:25 N 1 -73.864006042480469 40.732711791992188 -73.896461486816406 40.735050201416016 3 2.22 9.5 0 0.5 0 0 10 2 1 196 157 green 0.00 0.0 0.0 58 42 8.95 1288 717.02 4 Queens 071702 4071702...

- Updates to pod status via the status subresource now validate that `status.podIP` and `status.podIPs` fields are well-formed. ([#90628](https://github.com/kubernetes/kubernetes/pull/90628), [@liggitt](https://github.com/liggitt)) [SIG Apps and Node]
- Wait for all CRDs to show up in discovery endpoint before reporting readiness. ([#89145](https://github.com/kubernetes/kubernetes/pull/89145), [@sttts](https://github.com/sttts)) [SIG API Machinery]

- Added a `.status.features.supplementalGroupsPolicy` field to Nodes. The field is true when the feature is implemented in the CRI implementation (KEP-3619). ([#125470](https://github.com/kubernetes/kubernetes/pull/125470), [@everpeace](https://github.com/everpeace)) [SIG API Machinery, Apps, Node and Testing]

    * If the serialization type is 'application/json':
    * If serialization fails, and the original status code was an failure (e.g. 4xx or 5xx), the original status code will be returned.

- `kubectl diff` now returns 1 only on diff finding changes, and >1 on kubectl errors. The "exit status code 1" message as also been muted. ([#87437](https://github.com/kubernetes/kubernetes/pull/87437), [@apelisse](https://github.com/apelisse)) [SIG CLI, and SIG Testing]