- Pods were not allowed to mix the usage of `user-namespaces` (`hostUsers: false`) and `volumeDevices`. Kubernetes returned an error in this case. ([#132868](https://github.com/kubernetes/kubernetes/pull/132868), [@rata](https://github.com/rata))

- `etcd`: updated to `v3.5.10`. ([#121566](https://github.com/kubernetes/kubernetes/pull/121566), [@mzaian](https://github.com/mzaian))
- `k8s.io/dynamic-resource-allocation/controller:` `UnsuitableNodes` can now handle a mix of allocated and unallocated claims correctly. ([#120338](https://github.com/kubernetes/kubernetes/pull/120338), [@pohly](https://github.com/pohly))

             type="string" offset="0"/>
      <match value="\000\000\001\000" type="string" offset="0"/>
    </magic>
    <glob pattern="*.ico"/>
  </mime-type>

  <mime-type type="image/vnd.mix"/>
  <mime-type type="image/vnd.ms-modi">
       <glob pattern="*.mdi"/>
       <_comment>Microsoft Document Imaging</_comment>
       <magic priority="50">

- ValidatingAdmissionPolicy was promoted to GA and will be `enabled` by default. ([#123405](https://github.com/kubernetes/kubernetes/pull/123405), [@cici37](https://github.com/cici37))
- When scheduling a mix of pods using `ResourceClaims` and others that don't, scheduling a pod with `ResourceClaims` has a lower impact on scheduling latency. ([#121876](https://github.com/kubernetes/kubernetes/pull/121876), [@pohly](https://github.com/pohly))

## Known Issues

### CPU and Memory manager are not working correctly for Guaranteed Pods with multiple containers