September 13 Small Kubernetes for your local experiments: k0s, MicroK8s, kind, k3s, and Minikube

So you’ve come up with an idea to automate, unify, or transform something in a cluster, but you don’t want to risk ruining the cluster. This scenario is familiar to most people who’ve had experience with Kubernetes. To do that, what you need is an easy-to-set-up sandbox to test your idea without taking too much […]

Continue reading

September 3 werf vs. Docker: What is the difference when it comes to building images?

This article is the next installment in the “werf vs. …” series. In the previous article, we discussed the ways that werf differs from Helm. This article compares werf with an even more basic tool: Docker. Our followers often wonder what the point is of building images using werf when Docker and its Dockerfiles are […]

Continue reading

August 26 werf vs. Helm: Should you even compare them?

This article attempts to provide a detailed answer to a question we stumble upon every now and then: What is the difference between werf and Helm? At first glance, both of these tools seem to be designed with the same purpose: automating application deployment in Kubernetes. However, the reality is a little more complicated than […]

Continue reading

August 16 Best practices for deploying highly available apps in Kubernetes. Part 2

In Part One, we shared some recommendations for a number of Kubernetes mechanisms that facilitate the deployment of highly available applications. We discussed aspects of the scheduler operation, update strategies, priorities, probes, etc. This second part discusses the remaining three crucial topics: PodDisruptionBudget, HorizontalPodAutoscaler, and VerticalPodAutoscaler (the numbering continues from Part One). 9. PodDisruptionBudget The […]

Continue reading

August 6 Best practices for deploying highly available apps in Kubernetes. Part 1

As you know, deploying a basic viable app configuration in Kubernetes is a breeze. On the other hand, trying to make your application as available and fault-tolerant as possible inevitably entails a great number of hurdles and pitfalls. In this article, we break down what we believe to be the most important rules when it […]

Continue reading

Jule 28 Announcing Deckhouse, the Kubernetes Platform from Flant is now generally available

Today, we are delighted to announce the first Open Source release of Deckhouse. Developing and operating the platform in numerous, very diverse use cases took three and a half years. Deckhouse currently helps us maintain over 170 production clusters (3,500+ nodes) with more than 3,000 applications running. Deckhouse is the quintessence of our experience in […]

Continue reading

Jule 20 Failure stories #3. How we saved our monitoring system during the OVHcloud fire

This article shares our experience in addressing the impact the OVH data centers fire had on our monitoring infrastructure and lessons learned. Our monitoring system at large First of all, let me say a few words about how we monitor customers’ applications and the infrastructure as a whole. For this, we use three different types […]

Continue reading

June 17 Using Debezium, CDC for Apache Kafka, with PostgreSQL and MongoDB

In my work, I deal a lot with novel technical solutions/software. But unfortunately, it’s not always that they can boast with extensive information I might need. This article fulfills one such gap linked to my recent task when I was supposed to turn two popular DBMS (PostgreSQL и MongoDB) into event streams and send those […]

Continue reading

June 7 Why Flant acquired Okmeter monitoring company and what we should expect from this deal

Okmeter is a server monitoring solution that is available in both SaaS and on-prem versions. Flant and Okmeter have been working together since 2017. For Flant, Okmeter is one of the primary tools for monitoring customer infrastructure; over the years, companies have been cooperating to improve Okmeter observability capabilities. In mid-May, Flant announced the acquisition […]

Continue reading

May 27 Failure stories #2. How to destroy Elasticsearch while migrating it within Kubernetes

Our internal production infrastructure has a not too critical part which we use for testing various technical solutions, including different Rook versions for stateful applications. At the time of events described in this article, this part of the infrastructure was running Kubernetes 1.15, and we decided to upgrade it. The Rook operator v0.9 provisioned persistent […]

Continue reading