In cloud environments this problem is usually solved by a managed load balancer. In a self-hosted Proxmox setup we need an equivalent component that sits on the boundary between the public network and the private cluster network. Here, HAProxy plays that role.

Thankfully on Kubernetes, updates to the ephemeral containers feature and the addition of the --profile and --target options to kubectl debug have greatly simplified this process. There is now a fairly easy means of creating a privileged process context that shares a pid namespace with a specific target container.

Luxury Yacht is a cross-platform GUI desktop app for managing Kubernetes clusters and resources.

It's a plugin for kubectl that gives you a UNIX find-like experience. Find resource based on name regex, age, labels, status, node name, restarts, image name, or a jq filter — and then print, patch, annotate or delete any.

The Operator is designed to unlock seamless and effortless distributed performance testing in the cloud and enable continuous integration for CI/CD. By design, the entire system is cloud native and focuses on automation and CI practices. One strong feature about the system is its ability to horizontally scale to meet any required performance demands.

Most of what's been written about blameless post-incident reviews is about managers not blaming engineers, and engineers not blaming each other, because blame shuts down learning. What many miss is that engineers still blame themselves, and the damage is the same.

Every GCP resource and API have quotas. In a big organization, you can start having production incidents due to hitting quotas you didn't know about in projects you have never touched before.

We at Outreach are working hard to improve performance of our platform for our clients. Reducing startup times of nodes and pods can have positive impact on performance and cost as well. I am part of our infrastructure team focusing on AWS and Kubernetes and I recently implemented several improvements in node and startup time. I decided to share some of them in this article.

Kubernetes Network Policies are powerful, but when it comes to allowing egress access to specific domains, things get tricky. Most real world applications don't connect to fixed IPs, they rely on third-party APIs, cloud services, and CDNs with dynamic DNS records. In this post, I'll take you through the motivation behind building FQDN-Controller, how it works under the hood, and how you can use it to create clean, DNS-aware egress policies natively within Kubernetes.

Kloak transparently intercepts outbound TLS traffic in Kubernetes using eBPF uprobes, replacing hashed placeholders with real secrets at the kernel level before encryption. Applications never handle actual credentials, and no sidecars or code changes are required.

Do you really need separate systems for caching, queues, search, documents, and vector embeddings when you already have Postgres?