Technical articles on Kubernetes, K3s, and Proxmox
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.
MCP servers and AI agents on K3s don't reveal why they called a given tool just from logs. Here's how OpenTelemetry's GenAI semantic conventions make non-deterministic execution observable.
Are you still designing K3s cluster management access around a corporate VPN? Learn 3 practical steps to secure kubectl and Rancher dashboard access with identity instead of network perimeter, plus the pitfall most teams hit when they implement zero trust.
You can't know how resilient your production K3s environment really is until something actually breaks. Monitoring and alerting only detect failure after the fact. This guide covers how to get started with chaos engineering using CNCF's LitmusChaos on K3s, and how to judge which workloads are safe to break first and which ones demand extra caution.
A real-world MCP permission bypass shows why Kubernetes/K3s clusters need disciplined RBAC design and audit-log separation before letting AI agents operate them.
You set up an HPA in K3s and Pods still won't scale. The usual culprits are unset resource requests silently disabling metrics, and a self-reinforcing HPA/VPA feedback loop. Here's how to diagnose and fix it.