Page 5 — Technical articles on Kubernetes, K3s, and Proxmox
Why AI training jobs on K3s get OOMKilled from GPU memory shortages, why Vertical Pod Autoscaler doesn't cover GPU resources, and how to size requests/limits correctly using measurement-based design.
You ran the K3s disable-traefik flag but ingress-nginx still can't bind port 443. The culprit is ServiceLB (klipper-lb), another default K3s component. Here's how to diagnose it, disable it correctly, and what changes if you're running MetalLB.
A real incident where enabling automated resource optimization on K3s caused all replicas to be evicted simultaneously, triggering a full outage. This post explains why pods get evicted en masse and how PodDisruptionBudget's minAvailable setting prevents it.
K3s and Kubernetes CronJobs can keep showing 'Succeeded' while quietly not running for weeks. Here's how concurrencyPolicy, startingDeadlineSeconds, the 100-missed-schedule limit, and exit code 0 combine to create silent failures, and how to monitor for it.
Intermittent DNS failures in K3s usually come from ndots:5 query amplification combined with a UDP conntrack race condition. We break down NodeLocal DNSCache's benefits and side effects, plus K3s's own coredns-custom persistence trap.
A K3s PVC stuck in Pending often traces back to one fact: local-path-provisioner never enforces capacity limits. This post digs into hypervisor thin provisioning, Volume Node Affinity Conflicts, and the backup misconceptions hiding in K3s local storage design.
When CPU/memory-based HPA on K3s can't keep up with event-driven workloads, should you extend HPA or adopt KEDA, the CNCF-graduated project? Here's a 3-point decision framework, plus what to watch for on K3s.
A deep dive into how live-migrating a K3s control plane VM on Proxmox can break etcd quorum, explained through heartbeat/election-timeout mechanics and Proxmox affinity design, with concrete operational countermeasures.
Ever had a K3s cluster blocked by Docker Hub's pull rate limit? Here's how a Harbor private registry with Proxy Cache dodges the limit, plus vulnerability scanning, signing, and production-grade operational design.
Right-sizing nodes and adopting Spot VMs on AKS often plateaus because LoadBalancer-per-service billing and monitoring add-ons are structural fixed costs that operational tuning can't touch. We break down the real bottleneck and compare it to K3s's lightweight cost structure.