Writing
Notes on running your own infrastructure.
What we learned building Kaja, and the parts of Kubernetes we think you should not have to learn. RSS
Multi-cluster deployment, without inheriting multi-cluster complexity
Teams end up with several clusters for good reasons and then discover the tooling assumed one. What actually gets harder, and what does not have to.
What “roll back” should mean
Re-running a pipeline against an older commit is not a rollback. The difference is a rebuild you cannot afford and a configuration change no revert covers.
A cluster with no public IP, and what still works
We took a two-node cluster with nothing but RFC1918 addresses and published a site on it over HTTPS. Here is each step, what it required, and the parts that are genuinely a trade.
Bring your own cloud, and the assumption underneath it
BYOC promises a managed experience on infrastructure you own. Most implementations quietly require your infrastructure to be reachable from theirs, which rules out a lot of real infrastructure.
Why your database sits in Pending, and what a StorageClass is
A stateful workload that never starts is usually waiting for a disk nothing has offered. What is actually happening, and the one command to run before you add a database.
Introducing Kaja: push to deploy on clusters you already own
A deploy platform for the Kubernetes clusters you already run: builds, rollbacks, domains and HTTPS from one console, with compute that is never metered.
How pausing idle projects reduces cloud spend
Shared environments create queues; per-developer environments run all night. Isolated projects you can pause when you're done are the middle path.
Serve public traffic from a private server, without opening a port
Keep every inbound port closed and still run a real site on a real domain. How an outbound-only agent and a managed gateway make that work.
From a GitHub repo to a running app
What the path from code to a live URL looks like when there's no pipeline to wire up and no YAML to write.