DevOps as a Service from Flant Dedicated 24x7x365 support Discover the benefits
22 March 2022
Evgeny Samoilov, product manager

Deckhouse Kubernetes Platform v1.30 stable is released

Keep on reading to learn more about some awesome improvements and features in the new Deckhouse version — v1.30.16, including support for Kubernetes v1.22, Debian GNU/Linux 9-11, the namespace-configurator module, and the Early OOM killer component in the node-manager module.

Significant Changes

Kubernetes v1.22 support has been added. Older versions of Kubernetes prior to v1.19 are no longer supported.

Cert-exporter as well as alerts to track certificates expiration and cert-exporter health have been added. Note that this feature is currently available in Deckhouse EE only.

The local-path-provisioner module has been updated to the v0.0.21; the reclaimPolicy field has been added to the module configuration, the default reclaimPolicy is now set to Retain (you can manually change it to Delete).

DexAuthenticator is now based on oauth2-proxy v7.2.0.

etcd has been upgraded to version 3.5.1.

A new namespace-configurator module has been added. You can use it to automatically assign annotations and labels to namespaces. Note that this feature is currently available in Deckhouse EE only.

An Early OOM killer component has been added to the node-manager module. It prevents nodes from freezing on OOM (Out of Memory) events while the OS kernel frees memory pages.

Debian 9, 10, 11, CentOS 8, and RHEL 8 have been added to the list of supported operating systems.

Other changes

Below are some of the new features of existing components and modules:

  • chrony — NTP daemons on nodes are now disabled when this module is enabled.
  • control-plane-manager — a basic audit policy for kube-apiserver requests has been added. By default, requests logs about service account events in system namespaces (kube-system, d8-*) and all resource actions in those namespaces are now collected.
  • deckhouse — the following features have been added to the deckhouse module:
    • canary releases are implemented for Early Access and Stable release channels;
    • Deckhouse version update is now prevented if Kubernetes version is earlier than v1.19;
    • alerts are generated if Deckhouse updates are skipped: alert severity is getting higher if more releases are skipped.
  • dhctl — while creating cluster resources during bootstrapping, you now can access the metadata of objects deployed in the cloud using Terraform (networks/subnetworks IDs, security groups IDs). It makes the creation of new clusters more flexible and allows you to get the desired cloud infrastructure in one click.
  • ingress-nginx — dashboards with metrics essential for nginx process (CPU, memory, processed requests, configuration reloads) and dedicated dashboards for ingress-controller itself have been added.
The updated Grafana dashboard for the ingress-nginx module
  • istio — the alliance.ingressGateway.nodePort.port option is now available. It sets a static port for the ingressgateway service of the NodePort type.
  • monitoring-kubernetes — the eBPF exporter that monitors global and per-cgroup OOMs has been added to the module.
  • prometheus/grafana — support for Grafana notification channels has been added. Without notification channels, it was impossible to get alerts in Grafana for data sources outside of Prometheus (e.g., ClickHouse). This problem is now solved.
  • user-authn — a webhook checking the uniqueness of domain name and ingress class among all DexAuthenticators has been added.
  • okmeter — the okmeter agent image is now updated on its own, regardless of Deckhouse versions.

The documentation now includes a number of new sections, and several existing sections have been updated:

Please, refer to the changelog to see the full list of Deckhouse v1.30 changes and improvements. Note that the first Deckhouse v1.30.x stable release is v1.30.16.


For those who prefer a hands-on approach, the Getting Started guide will help you to start your journey with the Deckhouse Kubernetes platform.

Follow @deckhouseio for updates and join our Telegram chat to ask any questions! Deckhouse’s main GitHub repo might also be useful to ask for feature requests and discuss any issues.