Check out our latest post on running canary deployments in Kubernetes with Argo Rollouts, Istio, and passive health checks, using Kiali to track traffic: https://t.co/pp7mUgLYGj

Ever wanted your own home cluster? Learn how to run VMs in containers on a budget—hardware, storage, and networking included: https://t.co/ALknvEk2Jh

🚀 Deckhouse Kubernetes Platform v1.70 stable is out! The ceph-csi module replaced with csi-ceph, NGINX Ingress Controller 1.12 added (default now 1.10), falco_events metric removed. All DKP components will restart during update. See the CHANGELOG: https://t.co/dvjUsmBp6o

🚀 Deckhouse Kubernetes Platform v1.68 stable, featuring Huawei Cloud support and highAvailability for DexAuthenticator, is out. Also, known vulnerabilities have been addressed in 29 modules. Other improvements:

🚀 Deckhouse Kubernetes Platform v1.64 stable is out. Please note: Dashboard works only over HTTPS, Grafana 8 removed, major metallb update. See the CHANGELOG for more information:

Deckhouse Kubernetes Platform (DKP) 1.66 is out ⚡️ Know before update: 🔹 All control plane components will restart. 🔹 The minimum supported Kubernetes version is 1.27. For more information, see the CHANGELOG:

Here's a continuation of our series looking at Wasm application tools in Kubernetes clusters. This time, we'll be using an off-the-shelf operator called Kwasm to run an application. https://t.co/2PrWd8bBYj

Deckhouse Kubernetes Platform v1.64 stable is out! The l2-load-balancer module is replaced by metallb, and the new deckhouse-tools module allows offline CLI access. Other improvements:

Running WebAssembly applications in Kubernetes might seem challenging, but with Deckhouse Kubernetes Platform, it's a breeze. Discover how to set up your environment, install essential components, and run a test Wasm app in our latest article. https://t.co/yoMNFQDaJf

Deckhouse Kubernetes Platform v1.63 stable is out! The l2-load-balancer module has been redesigned, a new type of Ingress controller inlets has been introduced, and sidecar containers now have a default CPU utilization limit. Other improvements: https://t.co/2Np5JppXUh

Deckhouse Kubernetes Platform v1.60 stable is out! Support for Debian 9 has been discontinued. The method of calculating routes on nodes has been updated for the OpenStack provider. And more

Deckhouse Kubernetes Platform v1.59 stable is out! Support for Debian 12, high availability mode for Deckhouse, support for zVirt in EE, Grafana v10

⭐️⭐️⭐️ Yay! Deckhouse hits 1,000 stars on GitHub! Kudos to those who have participated in our chat room, tried Deckhouse, and used it over all these years. You are the ones who made it all possible! - GitHub https://t.co/cgmbwkS5ny - English-language chat https://t.co/zo5GjLS1w3

Deckhouse Kubernetes Platform v1.58 stable is out! Support for Kubernetes 1.29, support for VMware Cloud Director and more!

Want to try Deckhouse Kubernetes Platform out without all those fancy clouds and powerful servers? Well, now you can! Here is a detailed guide on how to get a taste of its key features on your own laptop using kind, a tool for running local #K8s clusters.

We have initiated the process of migrating from the LINSTOR module built into Deckhouse to the sds-drbd module, which will eventually replace LINSTOR. Find its documentation here:

🔊 Deckhouse v1.56 stable is out! The new version features several bug fixes and improvements: Istio 1.19 support has been added, Ingress controller v1.1 is now considered obsolete, etc.

🔊 Deckhouse v1.55 stable is out! The cilium version in the cni-cilium module has been upgraded from version 1.12 to 1.14. In the istio module, it is now possible to specify the timeout for a TCP connection between the istio sidecar and the service

🔊 Deckhouse v1.54 stable is out! The Ingress controller version 1.9 has been introduced. It is based on the chroot version of Nginx (which is more secure) and adds fixes for several recently discovered critical vulnerabilities

We share our experience of creating a CSI driver for shared SAN in Kubernetes as part of Deckhouse Virtualization module development. Read on to find out why we ultimately settled on QCOW2, what we did to improve performance, etc.