<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Booklets on Jōkamachi Systems</title><link>https://jokamachi.systems/booklets/</link><description>Recent content in Booklets on Jōkamachi Systems</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://jokamachi.systems/booklets/index.xml" rel="self" type="application/rss+xml"/><item><title>Getting started: setting up a Jōkamachi cluster</title><link>https://jokamachi.systems/booklets/setup/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://jokamachi.systems/booklets/setup/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Stub. Chapters to follow.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;The booklet you read first if you&amp;rsquo;re going to run Jōkamachi yourself
under the &lt;a href="https://jokamachi.systems/pricing/#free"&gt;Free plan&lt;/a&gt;, or if you just want to see how
the platform is put together before deciding whether to use the
Managed or Agentic plan.&lt;/p&gt;
&lt;p&gt;It covers, in order:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Prerequisites.&lt;/strong&gt; A Hetzner account, a domain you control, and
&lt;code&gt;kubectl&lt;/code&gt; on your laptop.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Bootstrapping the control plane.&lt;/strong&gt; Running the bootstrap scripts
against a fresh set of Hetzner cloud VMs (or bare-metal servers).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Adding worker pools.&lt;/strong&gt; Mixing cloud VMs and dedicated servers in
the same cluster.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Day-2 hand-off.&lt;/strong&gt; Wiring up monitoring, automatic backups, and
the dashboard — or skipping the dashboard and reading raw
Prometheus, if you&amp;rsquo;d rather.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Where to go next.&lt;/strong&gt; Pointers into the architecture and KAOS
booklets for deeper reading.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Plain-English, low-effort, no prior Kubernetes experience assumed.&lt;/p&gt;</description></item><item><title>Introduction to the technologies</title><link>https://jokamachi.systems/booklets/intro/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://jokamachi.systems/booklets/intro/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Stub. Chapters to follow.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;A guided tour of the technologies that make a Jōkamachi cluster run:
Kubernetes itself, the container runtime, the network plane, storage,
ingress, and the supply-chain pieces that sit around them.&lt;/p&gt;
&lt;p&gt;Written for someone who has heard of Kubernetes, but has never had to
operate one.&lt;/p&gt;</description></item><item><title>Cluster architecture</title><link>https://jokamachi.systems/booklets/architecture/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://jokamachi.systems/booklets/architecture/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Stub. Chapters to follow.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;The architecture booklet: control plane, worker pools, multi-tenancy,
the isolation boundaries between customers, and the deliberately boring
networking choices that hold the whole thing together.&lt;/p&gt;
&lt;p&gt;The booklet you read before you trust us with your workloads.&lt;/p&gt;



&lt;div class="bottom-cta"&gt;
 &lt;div class="hero-actions"&gt;
 
 
 &lt;a href="https://jokamachi.systems/pricing/" class="btn-secondary"&gt;Pricing&lt;/a&gt;
 
 
 
 
 
 &lt;a href="https://jokamachi.systems/about/" class="btn-secondary"&gt;About&lt;/a&gt;
 
 
 &lt;/div&gt;
&lt;/div&gt;</description></item><item><title>KAOS — the Kubernetes Agentic Operator Substrate</title><link>https://jokamachi.systems/booklets/kaos/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://jokamachi.systems/booklets/kaos/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Stub. The chapters that exist are stubs too.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;KAOS is the &lt;strong&gt;K&lt;/strong&gt;ubernetes &lt;strong&gt;A&lt;/strong&gt;gentic &lt;strong&gt;O&lt;/strong&gt;perator &lt;strong&gt;Substrate&lt;/strong&gt; —
the layer agentic operators live in and act through, and the operator
that ships with the &lt;a href="https://jokamachi.systems/pricing/#agentic"&gt;Agentic pricing tier&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;The booklet is structured as a progression from &amp;ldquo;you don&amp;rsquo;t need KAOS&amp;rdquo;
to &amp;ldquo;you actually want KAOS, here&amp;rsquo;s why&amp;rdquo;, because that&amp;rsquo;s the order in
which the value becomes apparent. KAOS is not a starting point; it&amp;rsquo;s
a destination you reach after you&amp;rsquo;ve earned operational experience
with the cluster yourself.&lt;/p&gt;</description></item><item><title>Performance profiling Kubernetes on Hetzner</title><link>https://jokamachi.systems/booklets/performance/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://jokamachi.systems/booklets/performance/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Stub. Chapters to follow.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;When you choose Hetzner over a hyperscaler, you also choose a
different set of trade-offs. Hetzner&amp;rsquo;s load balancer behaves
differently from AWS NLB; their cloud VMs share CPU cores in ways
their dedicated servers don&amp;rsquo;t; running a custom NAT gateway can save
real money or burn real engineering time, depending on the workload.&lt;/p&gt;
&lt;p&gt;This booklet puts numbers behind the choices. We benchmark the
options against real workloads and publish what we found, so you
don&amp;rsquo;t have to.&lt;/p&gt;</description></item><item><title>Kubenix: stronger primitives for cluster definitions</title><link>https://jokamachi.systems/booklets/kubenix/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://jokamachi.systems/booklets/kubenix/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Stub. The chapters that exist are stubs too.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Kubernetes is the right tool for running production workloads
because the world doesn&amp;rsquo;t stand still. Kubenix is the right tool
for &lt;em&gt;describing what you want Kubernetes to run&lt;/em&gt;, because hand-
stitching Helm charts loses the relationships between services that
make a cluster more than the sum of its parts.&lt;/p&gt;
&lt;p&gt;The booklet covers both halves of that argument and what they
unlock together.&lt;/p&gt;</description></item></channel></rss>