Kubernetes Deployments, DaemonSets, and StatefulSets: a Deep Dive from a Product

<p>The folklore about losing a Kubernetes node is specific and widely repeated. The node controller waits forty seconds before marking an unresponsive node <code>NotReady</code>,

<p>If you have already explored <a href="https://bibekkakati.com/blog/docker-explained-containers-and-architecture" rel="noopener noreferrer">Docker</a>, you know how convenient

<p>Kubernetes at the edge has been "the next big thing" for a few years now, and this month the honest assessment showed up in the reporting: edge Kubernetes has hit a wall, and

<p>Kubernetes Concepts are not random; each one has a beautiful problem-solving story behind it. </p> <p>Most people learn Kubernetes the wrong way.</p> <p>They see it as a list

<p>In <a href="https://peculiarengineer.com/blog/kubernetes-first-app-k3s-single-node/" rel="noopener noreferrer">Part One</a> I deployed nginx on a single k3s node and killed a

<p>I deployed Ollama on Kubernetes, and the GPU worker node locked up mid-rollout. No logs, no error, just a dead pod that wouldn’t terminate and a new one that wouldn’t schedule.