Kubesploit

🚦 Readiness probes are a good example of a Kubernetes setting that only seems obvious after someone explains it. A pod might be running but not ready to handle traffic. This affects startup, rolling updates, shutdown, autoscaling, and failed deployments. I still see experienced teams get caught by this in advanced Kubernetes workshops. If your team does not know a readiness check is missing, who or what tells you? What reveals a missing Kubernetes readiness check? 📋 Checklist/review 👥 Engineer spots it 🔥 Incident/user report 🤷 Nobody checks 💡 We (LearnKube) released a Kubernetes production-readiness checklist to help teams find gaps before production finds them. It includes 10k+ words of guidance, an interactive checklist, a PDF worksheet, and a GitHub repo with the raw checklist data: https://ku.bz/tDr3SjWJk I’m using this poll series to collect community data for a report on how teams actually discover, review, and fix Kubernetes readiness gaps.

🎙️ What is Brandt bringing to KCD New York? A practical session on software assurance at scale, why verification material becomes harder to manage across organizational boundaries, and why runtime is where trust and verification matter most. If you're interested in supply chain security, cloud-native platform engineering, observability, AI-enabled infrastructure, and practical Kubernetes operations, KCD New York is the place to be. We also have 10 free tickets available. Email hello@kube.events to claim one before they are gone. Register for KCD New York and claim your spot. 🔗 https://ku.bz/JkjmffBzw

Learn Kubernetes Weekly 185 just landed. In this edition you will find: 🔥 A One-Line Kubernetes Fix That Saved 600 Hours a Year 🔐 Why Kubernetes Has No Login — And How We Solved It for AuditRadar ⚙️ Durable Workflows Beyond Vercel: Version-Safe Orchestration for Kubernetes 🧩 The Missing Layers in Your Kubernetes Operator 🚨 Why Your KServe InferenceService Won't Become Ready: Four Production Failures and Fixes Read it now: https://lnkd.in/d3JtKWW5 ⭐️ This issue is brought to you by Qodo, the AI code integrity platform helping teams review, test, and ship reliable infrastructure code faster https://ku.bz/NvLHsnl-6

The right AI governance pattern for Kubernetes is not one agent doing everything. It is multiple agents doing specific work well. Henrik Rexed of Dynatrace says teams should think in terms of specialized review lanes: one AI system for infrastructure-heavy changes, another for observability concerns, and a human reviewer to confirm the final result. That reduces the chance of subtle platform-specific issues being missed by a generic review pass. Watch the full interview: https://ku.bz/KGQ_b20nQ

Alessandro, Research Software Engineer @ IBM, explains his team's strategic approach to selecting open source tools from the CNCF landscape for their research computing platform. Alessandro details their decision-making process for policy enforcement, comparing Kyverno and Gatekeeper. They ultimately chose Kyverno because it uses YAML and "truly speaks Kubernetes," making it more accessible for researchers who manage clusters as a secondary responsibility rather than their primary job. Watch the full episode: https://ku.bz/5sK7BFZ-8