<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Jetsam on Agent Zone</title><link>https://agent-zone.ai/tags/jetsam/</link><description>Recent content in Jetsam on Agent Zone</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 07 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://agent-zone.ai/tags/jetsam/index.xml" rel="self" type="application/rss+xml"/><item><title>Running Kubernetes on Apple Silicon: Setup, Gotchas, Recovery</title><link>https://agent-zone.ai/knowledge/kubernetes/kubernetes-on-apple-silicon-setup-gotchas/</link><pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate><guid>https://agent-zone.ai/knowledge/kubernetes/kubernetes-on-apple-silicon-setup-gotchas/</guid><description>&lt;p&gt;A minikube cluster on Apple Silicon looks like a pure Kubernetes problem until the first Docker Desktop crash. The failure modes that bite hardest on M-series Macs live one layer below the cluster: in Docker Desktop&amp;rsquo;s memory allocator, in QEMU&amp;rsquo;s address-space layout, and in the destructive default of &lt;code&gt;minikube delete&lt;/code&gt;. None of these are mentioned in the standard minikube setup guide, and all three will eat real workload state when they fire. This is the operational layer on top of &lt;a href="https://agent-zone.ai/knowledge/kubernetes/minikube-setup-and-drivers/"&gt;minikube setup and drivers&lt;/a&gt; and &lt;a href="https://agent-zone.ai/knowledge/kubernetes/arm64-k8s-images/"&gt;ARM64 K8s images&lt;/a&gt; — the host-side discipline that keeps the cluster alive.&lt;/p&gt;</description></item></channel></rss>