as well as tracking of field ownership, running on the Kubernetes API server. Server-side Apply helps users and controllers manage their resources via declarative configurations. It allows them to create and/or modify their objects declaratively, simply by sending their fully specified intent. After being in beta for a couple releases, [Server-side Apply](https://kubernetes.io/docs/reference/using-api/server-side-apply/) is now generally available.

### Container Storage Interface graduations...

  </mime-type>
  <mime-type type="application/vnd.3m.post-it-notes">
    <glob pattern="*.pwn"/>
  </mime-type>
  <mime-type type="application/vnd.accpac.simply.aso">
    <glob pattern="*.aso"/>
  </mime-type>
  <mime-type type="application/vnd.accpac.simply.imp">
    <glob pattern="*.imp"/>
  </mime-type>
  <mime-type type="application/vnd.acucobol">
    <glob pattern="*.acu"/>
  </mime-type>

- Passing an invalid policy name in the `--cpu-manager-policy` flag will now cause the kubelet to fail instead of simply ignoring the flag and running the `cpumanager`’s default policy instead. ([#80294](https://github.com/kubernetes/kubernetes/pull/80294), [@klueska](https://github.com/klueska))

non-empty manifests directory. This makes the preflight checks less heavy-handed by specifically checking for well-known files (kube-apiserver.yaml, kube-controller-manager.yaml, kube-scheduler.yaml, etcd.yaml) in /etc/kubernetes/manifests instead of simply checking for a non-empty directory. ([#57287](https://github.com/kubernetes/kubernetes/pull/57287), [@mattkelly](https://github.com/mattkelly))

* PVC Protection alpha feature was renamed to Storage Protection. The Storage Protection feature...