Potential impacts:

### Failing Test

- Allowed Azure Disk e2es to use newer topology labels if available from nodes. ([#117216](https://github.com/kubernetes/kubernetes/pull/117216), [@gnufied](https://github.com/gnufied))

- When creating a PVC with the volume.beta.kubernetes.io/storage-provisioner annotation already set, the PV controller might have incorrectly deleted the newly provisioned PV instead of binding it to the PVC, depending on timing and system load. ([#95909](https://github.com/kubernetes/kubernetes/pull/95909), [@pohly](https://github.com/pohly)) [SIG Apps and Storage]

* Implemented `kubeadm upgrade plan` for checking whether you can upgrade your cluster to a newer version ([#48899](https://github.com/kubernetes/kubernetes/pull/48899), [@luxas](https://github.com/luxas))
    * Implemented `kubeadm upgrade apply` for upgrading your cluster from one version to an other

" ) // This file contains two implementations of AES-GCM. The first implementation // (useGHASH) uses the KMCTR instruction to encrypt using AES in counter mode // and the KIMD instruction for GHASH. The second implementation (useGCM) uses // the newer KMA instruction which performs both operations (but still requires // KIMD to hash large nonces). // Keep in sync with crypto/tls.hasAESGCMHardwareSup. var useGHASH = cpu.S390XHasAES && cpu.S390XHasAESCTR && cpu.S390XHasGHASH var useGCM = useGHASH...

" ) // This file contains two implementations of AES-GCM. The first implementation // (useGHASH) uses the KMCTR instruction to encrypt using AES in counter mode // and the KIMD instruction for GHASH. The second implementation (useGCM) uses // the newer KMA instruction which performs both operations (but still requires // KIMD to hash large nonces). // Keep in sync with crypto/tls.hasAESGCMHardwareSup. var useGHASH = cpu.S390XHasAES && cpu.S390XHasAESCTR && cpu.S390XHasGHASH var useGCM = useGHASH...