This article examines why Copy Fail (CVE-2026-31431) breaks container assumptions and provides a small, safe Python check to determine whether your nodes can reach the vulnerable kernel path.

More: https://ku.bz/CTv-Yf60c

This article shows how a default AWS EKS setting lets any pod reach the node's metadata service and steal its IAM credentials, then walks through the simple fix.

More: https://ku.bz/DXYZGjvf2

This article explains a new alpha feature in Kubernetes 1.36 that loads admission policies from files on disk at startup, so they are live before anything else and nobody can delete them.

More: https://ku.bz/B9JxC5dVt

On-prem apps talking to cloud services need a path — and there are three.

Raglin Anthony explains: public internet with HTTPS (simple, but at the mercy of variability), AWS Site-to-Site VPN (private and encrypted), or AWS Direct Connect (a physical cable that bypasses the internet entirely — suitable for production and compliance workloads).

Whichever path you pick, DNS resolution across environments is always the last thing you have to sort out.



Watch the full interview: https://ku.bz/2XqMJnLVx

This article explains why three old Kubernetes CVEs will never get a code fix, and what to change in your cluster now that scanners are about to start flagging them again.

More: https://ku.bz/22Rr95v9F

A pizza order became a 15-container, 200-trace system.

In Kube Signals episode two, Brian Teller and Mauricio (Salaboy) Salatino examine observability, state management, governance, and trust for non-deterministic agents.

They discuss:

- Why multi-agent runtimes can recreate monolith scaling
- How OpenTelemetry exposes prompts, completions, and decisions
- Why execution history turns agent trust into measurable evidence

Watch: https://ku.bz/TlVjXdnb6

Kubernetes moves too fast to track everything. Learn Kubernetes Weekly filters out the noise to deliver one curated email with useful articles, tutorials, tools, jobs, events, and CFPs. Subscribe to Learn Kubernetes Weekly.

Guardrails are not one-size-fits-all. David Parry argues that AI systems touching Kubernetes need deterministic rules that match the company, the deployment model, and the compliance requirements around sensitive data.

He points to code review and YAML inspection as places where these guardrails should be explicit and enforceable, not left to improvisation.



Watch the full interview: https://ku.bz/c5J05syX3

This interview is a reaction to Mai Nishitani's episode https://ku.bz/3hWvQjXxp.

This article walks through a real Copy Fail pod escape on Talos Linux, showing how a shared page cache breaks container isolation and why gVisor or microVMs help.

More: https://ku.bz/tYzhJx61Q

Kubernetes problems often hide in controller timing, implicit defaults, and capacity assumptions.

This week in Learn Kubernetes Weekly:

🔎 A production race condition left orphaned pods blocking new deployments.
📦 Source Hydrated Infrastructure Models commit rendered manifests for explicit GitOps audits.
🖥 Headlamp replaces the archived Kubernetes Dashboard and maps familiar workflows to a maintained UI.
⚙️ Kubernetes 1.36 adds pod-level CPU and memory management.
📊 The k8s-overcommit operator reclaims idle capacity according to priority classes.

Read issue 201: https://kube.today/issues/201

This issue is brought to you by LearnKube — understand how Kubernetes works, and what to do when it breaks. Live training with 60% hands-on labs: https://ku.bz/hypSbyc-V

This article walks through building a Kubernetes admission webhook in Go from scratch, including the TLS trust setup and the bootstrapping deadlock nobody warns you about.

More: https://ku.bz/tdxnc5S4r

Kubesafe is a tool that prevents accidental execution of dangerous commands on the wrong Kubernetes cluster by providing a safety net for cluster management.

More: https://ku.bz/3hC23K79L

Kogaro continuously validates Kubernetes config with 60+ checks across reference, resource, security, image, and network domains, catching silent failures before they impact production.

More: https://ku.bz/SWl3-LNty

Moving to Kubernetes doesn't replace your security practices, but it adds a layer on top.

Rodrigo Bersa at AWS breaks down what carries over and what must change.

What stays: least privilege, perimeter security, network access control, authentication and authorization.

What changes:

- Supply chain security — you're managing hundreds of images, not just VMs
- Multi-tenancy by default — workloads share nodes; namespace isolation and network policies keep them separate
- In-cluster auth needs its own model, separate from infrastructure-layer controls





Watch the full interview: https://ku.bz/dB7PDNt0v

This case study shows how a team ran ServiceNow's MID Server on EKS as a StatefulSet and faked the EC2 metadata service so the agent would accept IRSA credentials.

More: https://ku.bz/mdkryD536