Page 4 — Technical articles on Kubernetes, K3s, and Proxmox
How long does failover really take with K3s embedded etcd versus kubeadm stacked/external etcd? We examine the gap between official RTO targets and real-world recovery times, and how failure domains and node counts differ.
Enabling both HPA and VPA in Kubernetes can make two well-intentioned automations fight each other, sending autoscaling into an endless spiral. Here's why the conflict happens, and how to combine them safely with updateMode and metric separation.
K3s vs RKE2 is often reduced to a feature checklist. Using a real production migration incident, we break down CIS Hardening, HA requirements, and storage assumptions to help you choose the right distribution for production.
Is K3s really as lightweight as everyone says? We compare K3s and kubeadm-based standard Kubernetes control plane memory and CPU usage using official data and multiple independent benchmarks, and explain why the datastore choice (etcd vs SQLite) can flip the result.
KEDA and HPA aren't an either-or choice. When event-driven workloads grow on K3s/Kubernetes, here's why HPA alone hits its limits and how to decide when to add KEDA alongside it.
Building edge AI inference on K3s runs into standard Kubernetes GPU resource management (integer units, request=limit). Here's how to share one GPU across multiple models, and what to watch for with time-slicing.
Should your CI/CD build runner infrastructure run on K3s or standard Kubernetes? We compare job startup latency, Cluster Autoscaler cold starts, and the cost structures of GitLab Runner and GitHub Actions ARC to find the right selection criteria.
The difference between K3s and Kubernetes isn't just a feature list. The HelmChart CRD is an automation layer that quietly reverts manual helm upgrades and kubectl edits — here's how it works and how to avoid it.
Your HPA increased replica count, but the Pod is stuck Pending. The real cause is that Cluster Autoscaler needs minutes to add a node. Here's the delay breakdown, a diagnostic checklist, overprovisioning, and how Karpenter compares.
We deployed both Linkerd and Istio Ambient Mesh on K3s and compared them directly. From proxy architecture and real memory numbers to a K3s-specific CNI path pitfall, here is the decision framework for picking a service mesh on a lightweight K3s cluster.