I usually donāt get excited about Kubernetes version numbers. Most releases come, we skim the changelog, upgrade when forced, and move on. But v1.35 made me stop for a bit. Not because itās flashy.Because it feelsā¦ mature. Kubernetes v1.35 was released on December 17, 2025, and itās called Timbernetes ā The World Tree Release. The … Read more
If youāve worked with Kubernetes long enough, you already know this truth: Most Kubernetes issues donāt start in the cluster. They start in YAML. A missing resource limit.A privileged container left unnoticed.No readiness probe, no liveness probe. Everything looks fineā¦ until it isnāt. Thatās exactly the problem K8sGuardian Engine is built to solve. K8sGuardian Engine … Read more
This is not a copyāpaste documentation blog. This guide comes from real incidents, real mistakes, and real recoveries in production. To be honest, most teams start thinking seriously about Kubernetes Disaster Recovery only after something bad has already happened. I was no different. For a long time, I believed that High Availability was enough. Then … Read more
Iāve been running Kubernetes clusters for years now, and I still get that sinking feeling every time I delete a deployment or uninstall a Helm chart and justā¦ assume itās really gone. It never is. Thereās always something left behind. Quietly rotting in etcd, taking up space, slowing things down, and occasionally breaking stuff in … Read more
Kubernetes just dropped version 1.33, and itās one of the most meaningful releases in recent years. If you manage clusters, run production apps, or work in DevOps, this version comes packed with upgrades that simplify operations, boost performance, and tighten security. In this blog, weāll break down all major enhancements in Kubernetes 1.33, explain how … Read more
Introduction Air-gapped environments are common in regulated industries (defense, banking, pharma) where clusters and CI/CD systems cannot talk directly to the public internet. The challenge is to keep development velocity without sacrificing security: builds must run, images must be scanned and signed, and artifacts must be available inside the offline environment ā all while keeping … Read more
1. Problem StatementA pod is repeatedly crashing and restarting, showing the error status CrashLoopBackOff whenchecking with kubectl get pods. resources: requests: memory: “256Mi”limits: memory: “512Mi” Manually Restart the Podkubectl delete pod <pod-name> -n <namespace>