Kube Architect

Ryan Brainard, Software Engineering PMTS @ Heroku by Salesforce, explains how GitOps serves as a crucial source of truth and addresses the configuration drift problems his team experienced with Helm-based pipelines. Ryan emphasizes that they avoid manual changes entirely and treat clusters as cattle, not pets - making them completely disposable and enabling seamless upgrades. This approach leverages their immutable and ephemeral workloads to maintain consistency and eliminate configuration drift at scale. Watch the full interview: https://ku.bz/WY43k-PBd This interview is a reaction to Andrew Jeffree's episode https://ku.bz/Xvyp1_Qcv

Swimmer is a native desktop Kubernetes GUI built for multi-cluster workflows, letting you browse 27+ resource types, compare clusters in split panels, and run terminal sessions per cluster, built with Tauri and Rust. More: https://ku.bz/mFQXr4w0h

Kubernetes cost optimization starts with Node Autoscaler and proper resource sizing. Amin Astaneh shares strategies: dynamically size clusters with Node Autoscaler and ensure workloads fit within resource requests. The combination of autoscaling and proper sizing prevents wasted capacity and unnecessary costs. Watch the full interview: https://ku.bz/p1RNM5ldZ This interview is a reaction to Marc Campora's episode https://ku.bz/5gMTkzLhV

📅 Kubernetes events starting in the next 24 hours: Kafka on Kubernetes: Building a Full-Stack Streaming Environment with Strimzi https://ku.bz/LqgtQr_88 Kubecon & CloudNativeCon 2026 recap https://ku.bz/m5pqvgpfw One Platform, Many Teams: Driving Kubernetes Adoption Across E.ON https://ku.bz/5Yt4YWrXx Intelligent Node Management with Karpenter in Kubernetes https://ku.bz/zZwM4DVlJ Production-Ready Kubernetes: Security, Observability, Cost & Privilege Control https://ku.bz/nfwhTYvqL 📅 Starting next week: Kubernetes for Developers: Security! https://ku.bz/xynLJrnNJ Craft Conference 2026 https://ku.bz/l7Pl4VPvy 👩🏫 Courses and 🎤 conferences to watch out for: techcamp 2026 https://ku.bz/Q-ThRC3Ny → See all Kubernetes events https://kube.events

🚦 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.

Dave, Software Engineer and Founder at Compute Gardener, explains how carbon awareness can be integrated into Kubernetes scheduling decisions through workload shifting strategies. He breaks down the concept of temporal shifting (moving workloads to cleaner times) and spatial shifting (moving workloads to cleaner locations), with his current focus on the time-based approach. Watch the full episode: https://ku.bz/zk2xM1lfW

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

"CPUs are not real metrics." Nicholas Eberts explains why CPU and memory are tough metrics for accurate saturation. When you're scaling with HPA, you want to actually utilize the resources you're paying for — but CPU doesn't tell you if your pod is truly saturated. The easy button? Requests per second. Or implement custom metrics and export them from your application. You'll get way more efficiency than CPU and memory will ever give you. Watch the full interview: https://ku.bz/jlDL5XzCd

Mac Chaffee explains the critical decision point where teams should reconsider adopting Kubernetes after initially rejecting it. He distinguishes between informed rejection - where teams understand both Kubernetes and their application needs - and uninformed rejection that creates significant risks. Mac emphasizes that teams who truly understand Kubernetes and consciously choose alternatives aren't constantly second-guessing their decision. However, teams that reject Kubernetes without understanding the problems it solves may discover they need auto-scaling, service discovery, or failover capabilities at the worst possible moment - like during Black Friday traffic spikes for e-commerce companies. Watch the full episode: https://ku.bz/9nFPmG85f