Please note
* **The port range used by DKP components has been changed.** Managing network policies is now easier since most ports are in the 4200-4299 range. Please refer to the [documentation](https://deckhouse.io/documentation/v1.62/network_security_setup.html) for an up-to-date list of the ports in use and instructions on how to assign a specific port.
Major changes
* **Support for Kubernetes 1.30 has been added while support for Kubernetes 1.25 has been discontinued.**
* You can now send logs via a TCP or UDP [socket](https://deckhouse.io/documentation/v1.62/modules/460-log-shipper/cr.html#clusterlogdestination-v1alpha1-spec-socket); _text_, _JSON_, _CEF_, _Syslog_ encodings are supported.
* A leader label (`leader=true`) has been added to the active DKP controller pod (d8-system/deckhouse). You can now run commands in the DKP pod in a more convenient fashion, regardless of whether the pod is running in high availability mode or not, e.g.:
shell
kubectl -n d8-system -l app=deckhouse,leader=true -c deckhouse logs
* A [nodeGroups.instanceClass.configDrive](https://deckhouse.io/documentation/v1.62/modules/030-cloud-provider-openstack/cluster_configuration.html#openstackclusterconfiguration-nodegroups-instanceclass-configdrive) boolean parameter has been added to the OpenStack provider for the _SimpleWithInternalNetwork_ layout to control whether an additional disk containing the node's configuration will be mounted on the node. This parameter must be enabled if DHCP is disabled on the network designated as the _mainNetwork_.
* An option to manage VPA settings (the [resourcesRequests](https://deckhouse.io/documentation/v1.62/modules/650-runtime-audit-engine/configuration.html#parameters-resourcesrequests) parameter) has been added to the runtime-audit-engine module.
* Users are not allowed to create namespaces prefixed with `d8-` and `kube-`. Only DKP can create these _system_ namespaces.
* A [section](https://deckhouse.io/documentation/latest/module-development/) has been added to the documentation with information on how to get your DKP module up and running.
* [Deckhouse CLI](https://deckhouse.io/documentation/v1.62/deckhouse-cli/), the tool for working with Deckhouse Kubernetes Platform clusters, is now available for Windows.
Component version updates
- Kubernetes control plane: `v1.27.15`, `v1.28.11`, `v1.29.6`, `v1.30.2`
- cloud-provider-yandex CSI plugin: `v0.12.0`
- cloud-provider-vsphere CSI plugin: `v3.0.0`
- deckhouse-cli (d8 tool): `0.2.1`
- dex: `2.40.0`
- helm_lib: `1.26.0`
- nginx (Ingress controller 1.10): `1.25.5`
A list of internal modules or their components that will be restarted during the upgrade
- Kubernetes control plane
- Ingress-controller with the `HostPortWithFailover` inlet
- Ingress-controller v1.10
- bashible-apiserver
- capi-controller-manager
- cilium-agent
- cloud-provider-*
- deckhouse
- dex (user-auth)
- documentation
- ebpf-exporter
- kube-proxy
- kubeconfig-generator (user-auth)
- kubelet
- log-shipper
- machine-controller-manager
- metallb
- network-policy-engine
- node-exporter
- node-local-dns
- registry-packages-proxy
- runtime-audit-engine
See [CHANGELOG v1.62](https://github.com/deckhouse/deckhouse/blob/main/CHANGELOG/CHANGELOG-v1.62.md) for more details.