The following components will be restarted during the update from the Deckhouse 1.30
* Ingress controllers of version >=0.33;
* Kubernetes Control Plane components and kubelet will restart for 1.20, 1.21 and 1.22 minor versions.
Component version updates
* Dex: 2.31.0
* control-plane: 1.20.15, 1.21.9, 1.22.6
* cluster-autoscaler: 0.19.0
* csi (for Kubernetes 1.21, 1.22)
* provisioner: 3.1.0
* attacher: 3.4.0
* resizer: 1.4.0
* snapshotter: 5.0.1
* livenessprobe: 2.5.0
Features
* [linstor](https://deckhouse.io/ru/documentation/latest/modules/031-linstor/faq.html) - the new module. It enables a replicated block storage solution in the cluster using the LINSTOR and the DRBD kernel module. It is actively developed now;
* Kubernetes Control Plane new features:
* [Ability](https://github.com/deckhouse/deckhouse/pull/807) to automatically update the Kubernetes version when updating Deckhouse. To do this, specify `Automatic` as the value for the `kubernetesVersion` field in the `ClusterConfiguration` resource (secret `d8-cluster-configuration/kube-system`). The current default version is 1.19;
* Kubernetes scheduler takes into account availability zones when scheduling Pods;
* [Ability](https://github.com/deckhouse/deckhouse/pull/783) to turn on and off active [admission controller's](https://kubernetes.io/docs/reference/access-authn-authz/admission-controllers/#what-does-each-admission-controller-do). The `ExtendedResourceToleration` and `EventRateLimit` parameters are now enabled by default;
* [Ability](https://github.com/deckhouse/deckhouse/pull/766) to specify parameters for rotation of kubelet log files;
* The `TTLAfterFinished` parameter is [enabled](https://github.com/deckhouse/deckhouse/pull/781) in clusters of versions >1.21. It allows using the `ttlSecondsAfterFinished` parameter in Jobs to automatically delete them after completion;
* Fixed issue when system components could affect cluster auto-scaling;
* [Fixed](https://github.com/deckhouse/deckhouse/pull/989) `ingress-nginx-controller` vulnerability, which could lead to an explosion of sensitive data if the invalid `auth-url` was accidentally specified.
See [the CHANGELOG v1.31](https://github.com/deckhouse/deckhouse/blob/main/CHANGELOG/CHANGELOG-v1.31.md) for more details.