This article is about the patterns that actually work when you're managing real databases in Kubernetes, not hello-world demos: when your boss says "everything should be containerized" but your databases laugh in the face of ephemeral pods, and when GitOps meets a 200GB production database that absolutely cannot lose a single transaction.

Operators make life easier, but they are not always an option. In this post, I'll walk through a practical way to deploy large language models on OpenShift without relying on the OpenShift AI or NVIDIA operators. The approach uses llama.cpp as a lightweight runtime engine and runs a quantized GGUF model to enable efficient inference with minimal dependencies.

This article explains how Cosign, Kyverno, and Harbor can work together to enforce image signature verification in Kubernetes. The approach is well-suited for enterprise environments with private registries, custom TLS certificates, and restricted access to public transparency logs.

Jenkins might feel like legacy tech, but it's still powering CI/CD at thousands of companies. Instead of ripping it out, here's how to modernize it with Kubernetes — solving cost tracking, resource isolation, and scalability problems along the way.

This blog aims to provide a practical example of how core tools like Kubernetes, Terraform, and DevContainers can be combined to build a local data platform in a structured and maintainable way.

Netfence runs as a daemon on your VM/container hosts and automatically injects eBPF filter programs into cgroups and network interfaces, with a built-in DNS server that resolves allowed domains and populates the IP allowlist.

A lightweight, extensible Kubernetes Operator that probes any endpoint—HTTP/JSON, TCP, DNS, ICMP, Trino, OpenSearch, and more—and routes alerts to Slack or e-mail with a simple Custom Resource.

Argo CD Diff Preview is a tool that renders the diff between two branches in a Git repository. It is designed to render manifests generated by Argo CD, providing a clear and concise view of the changes between two branches. It operates similarly to Atlantis for Terraform, creating a plan that outlines the proposed changes.

So we built a pipeline that’s intentionally “boring”: GitHub pull requests, GitHub Actions, Kubernetes, and Argo CD — split across staging and production.

This post is a walkthrough of how a feature goes from a developer’s machine to real users, and why we made the choices we did.

How I reduced pod startup times from minutes to seconds with intelligent image preloading

If Red Hat trusts OpenShift to run the control plane for their largest infrastructure orchestrator, the same pattern should apply to your smallest.