Tracked topic
This raises a potential area for enhancement in Kubernetes. One option would be introducing a minimal termination history — similar to lastState in ContainerStatus — for ephemeral containers. The lastState field could be added to EphemeralContainerStatus with minimal breaking changes, since ephemeral containers are never restarted. It would store only the most recent termination record. The design decision to exclude lastState made sense when ephemeral containers were introduced in alpha (Kubernetes v1.16). As kubectl debug becomes a standard incident response tool across the ecosystem, the ab
What kubectl debug doesn’t tell you: The silent evidence gapInstead of dynamically building VM images on every provision, I used existing Proxmox VM templates. My templates already had cloud-init enabled, SSH access configured, and base OS packages installed. This gave me: Faster VM provisioning — no image builds in the critical path Better control over OS hardening — managed outside the Kubernetes workflow Easier debugging — when something goes wrong, the VM layer is a known quantity
K3s on On-Prem Infrastructures the GitOps Way: Writing a Custom k0rdent Template from Scratch… If you zoom out and look at what it really costs to run Kubernetes, the data shows where time, money, and effort add up: Komodor’s 2025 Enterprise Kubernetes Report found teams lose roughly 34 workdays per year resolving Kubernetes incidents, with nearly 80% of production issues tied to recent syst… …
… How AI Benefits from Technologies Like Kubernetes Kubernetes, the de facto standard for container orchestration, provides AI with the robust foundation needed to thrive at scale. …
… However, once the session ends, Kubernetes does not retain the termination context of that session in its API. This is not a kubectl bug — it follows directly from the Kubernetes API design for ephemeral containers. …
… Existing VM templates instead of building images every time k0rdent managing the full cluster lifecycle K3s as the Kubernetes bootstrap At a high level, the flow looks like this: User → k0rdent ↓ Proxmox Infrastructure BYOT VMs ↓ Control Plane Provider ↓ Bootstrap Provider K3s ↓ Running Kubernetes … …
… External Secrets Operator running within each Kubernetes cluster. Kubernetes Secrets generated and maintained by ESO for application consumption. …
… The Kubernetes irony The irony is sharpest in the Kubernetes ecosystem. Kubernetes is the SRE moment for infrastructure – the most successful embodiment of “design for failure” ever built. …
… This is the same pattern Kubernetes uses for device plugins and the metrics server — a per-node agent that collects local hardware data. …
… References Kubernetes repository: https://github.com/kubernetes/kubernetes k0s repository: https://github.com/k0sproject/k0s k0rdent repository: https://github.com/k0rdent/k0rdent k0smotron repository: https://github.com/k0sproject/k0smotron Cilium repository: https://github.com/cilium/cilium Dynam…
… Networking and traffic management The networking layer combines Kubernetes-native primitives with Istio’s service mesh capabilities to provide secure, observable, and policy-driven traffic management: Kubernetes Services expose workloads internally with stable DNS-based discovery Azure Load Balance… …
… The combination of: k0s lightweight Kubernetes k0rdent multi-cluster orchestration OpenStack private cloud infrastructure creates a powerful platform engineering stack . 1. Prepare your environment Before you touch Kubernetes, make sure your base environment is correct. …
