Page 2 — Technical articles on Kubernetes, K3s, and Proxmox
Your kubernetes service monitor isn't being scraped and there's no error to explain why. The root cause is almost always one of three things: label mismatches, a missing namespaceSelector, or RBAC. Here's how to diagnose each one against the official docs.
Kubernetes GPU multi-tenancy isn't a binary choice between namespace isolation and dedicated nodes. This article breaks down the cost-vs-isolation trade-off and how to design a hybrid approach.
Splitting dev/staging/production by Git branch is a GitOps anti-pattern that undermines Kubernetes' declarative foundations. Learn why drift happens, how to migrate to a directory-based, trunk-based setup, and how to design for fleet-scale growth.
Kubernetes certificate management is technically a matter of days. What actually takes time is the organizational process of getting sign-off. Here's how cert-manager automates the technical side, and how to design away the operational debt that remains.
Code generated and executed by AI agents can no longer be treated as a trusted, reviewed product. This article explains the limits of container isolation and why Kata Containers' microVM isolation is becoming essential when designing AI agent sandboxes on Kubernetes.
Why doesn't live migrating a VM (KubeVirt) between Kubernetes nodes break the connection? We break down Calico's IP persistence and BGP route convergence, and what it means for teams moving off VMware.
Container image signing explained: tags can be overwritten by anyone, and passing CI tests doesn't guarantee the image running in production is the one you built. Learn how Sigstore and Kyverno work together to reject unsigned images on Kubernetes/K3s, integrated into a GitOps workflow.
World Cup broadcasts duplicate every camera feed across two independent paths and simply discard whichever packet arrives second. That seemingly wasteful design shares the same philosophy as Kubernetes high availability and multi-AZ architecture.
AI-generated Kubernetes manifests pass kubectl apply and 'work' — but getting Kubernetes resource design wrong drives massive overprovisioning. Here's why AI struggles with production-grade requests/limits and what to check before you ship.
Fleet management for K3s edge operations breaks down once you're troubleshooting devices one at a time by hand. Here's how declarative management and Rancher Fleet let you design edge operations that don't depend on any single person.