At VictoriaMetrics, we built vlagent as a high-performance log collector for VictoriaLogs. To validate its performance and correctness under a real production-like load, we developed a benchmark suite and ran it against 8 popular log collectors. This post covers the methodology, throughput results, resource usage, and delivery correctness.

With the retirement of ingress-nginx I've seen a lot of frustrations with Gateway API migrations due to differences in some of the resource models. The common problem is that Ingress users are often running self-service models, where application teams fully own their ingress configuration, including TLS certificates.

Standard migration paths require downtime. At our scale, taking hundreds of disks (backing data stores like ClickHouse, CockroachDB, Kafka, Prometheus) offline was off limits. This blog introduces an in-place PVC re-binding technique that swaps a PersistentVolumeClaim's backing PersistentVolume while keeping the underlying disk intact. It requires only a single pod restart per volume, done entirely using the Kubernetes API natively with no custom software or control plane hacks.

Stop paying for idle resources. Learn to identify and eliminate the hidden blockers preventing your cluster from scaling down.

How we took a 5-service Java application from docker-compose up to a production-grade Kubernetes cluster — and every bug we hit along the way.

This article explores how Cilium Cluster Mesh simplifies multi-cluster Kubernetes connectivity, covering both the underlying challenges of so-called Mesh solution and how Cilium addresses them. It also provides a hands-on scenario that interconnects a multi-cloud application running on the native Kubernetes services of Amazon Web Services and Google Cloud Platform.

In this article, we'll walk through how to build a fully automated CI/CD workflow using Argo CD, Argo CD Image Updater, GitHub, Amazon Elastic Container Registry, Amazon Elastic Kubernetes Service. This setup enables automatic deployment whenever a new container image is pushed to the registry with no manual intervention.

Most people interact with Kubernetes through the cloud. They probably are as close to the cluster as they are to their laptop. Using a cluster in the cloud with a web browser or terminal is fine but there is something more intimate or rewarding to deploying a kubernetes cluster on bare metal. And even more rewarding is physically unplugging a node and watch Kubernetes rebalancing the workloads.

Every AI agent eventually asks for the same thing: "Let me run a program." Sometimes it's a harmless pytest. Sometimes it's pip install sketchy-package && python run.py. Either way, the moment you let an agent execute code, you're running untrusted bytes on a machine you care about.