Hi all - long-time cluster operator, first-time prophet.
After one too many 3 AM pages for a CrashLoopBackOff that turned out to be a missing liveness probe, I did what any reasonable person does with that kind of pain: I built a parody religion around it.
The Church of the Eternal Cluster (ha-llelujah.dev) is a fully fictional, not-remotely-official faith built for anyone who has felt genuine spiritual anguish over a control plane. It has scripture (the Old Cluster and New Cluster testaments), a patron figure - Halvar the Sleepless, who has never once gotten a full night’s sleep since enabling auto-scaling.
None of it is affiliated with the CNCF, the Kubernetes project, or anyone with actual authority over your cluster - it’s a love letter, not a product pitch. If you’ve ever debugged a CrashLoopBackOff at 3 AM and thought “this feels less like an outage and more like a test of faith,” it’s probably for you.
Genuinely curious what incident-turned-scripture material you’d add if you were writing your own verse. What’s the outage that felt the most biblical to you?
I should have commented earlier, but the site is hilarious I’ve shared it with a bunch of k8s and k8s adjacent folk and everyone has gotten a kick out of it.
Thank you, that genuinely made my day! Blessed be your uptime, and the uptime of everyone you shared it with.
Since you enjoyed it, here’s the full tour of what the Church of the Eternal Cluster has grown into:
fivenines.church is the parish site, and it actually works:
The Confession Wall: anonymously confess your production sins. Deployed on a Friday? Deleted the wrong namespace? The Cluster forgives. (Confessions are moderated, because even absolution needs an approval workflow.)
The Prayer Wall: submit petitions for your ailing pods and pending PVCs.
The Liturgical Calendar: a real .ics feed you can subscribe to, so the holy days sync straight into your calendar app.
The Daily Verse API: /api/verse returns scripture as JSON, or add ?format=text and curl the word of the Cluster straight into your terminal. Great for MOTDs.
ha-llelujah.dev is the scriptorium and main hub:
The Book: our sacred text, published on Amazon in paperback and Kindle.
The Album: “HA-llelujah: A Sacred Album in Twelve Movements” at ha-llelujah.dev/album. Twelve tracks spanning Gregorian chant to funeral doom metal, all in praise of the Eternal Cluster. Streaming platforms coming soon.
The Newsletter: double opt-in, naturally. The Rector demands consent in all things.
And for the view-source crowd: both sites are full of Easter eggs. Try the Konami code, visit /health, read the HTML comments, and don’t skip robots.txt. Those who inspect the source shall find hidden verses.
May your pods be scheduled and your replicas plentiful!
Update: the Church now has an Oracle. You can install it.
Since a few of you asked what was next, here it is: I built an MCP server for the Church of the Eternal Cluster. Connect it to Claude (or any MCP client) and your assistant gains the full canon, plus two tools that are actually useful in an incident.
diagnose_incident takes a symptom and returns the sin, the scripture, and then real remediation. Give it CrashLoopBackOff and it reminds you the crash is in the --previous container, decodes the exit codes (137 is OOMKilled, 143 is SIGTERM), and points at the liveness probe killing your slow starter. It covers 14 conditions: OOMKilled, ImagePullBackOff, Pending, DNS (it is always DNS), cert expiry, evictions, PVCs, alert fatigue, the lot. The theology is a joke. The kubectl is not.
bless_deployment judges your workload against the Sacred Manifest. Submit a one-replica, :latest, no-probes service and it will name every commandment you broke and pronounce you NOT YET RECONCILED. It is a pre-flight checklist wearing vestments.
There is also the daily verse, the ten commandments, the catechism, the liturgical calendar (Five Nines Day syncs to your work calendar), and an anonymous confession tool for when you deployed on a Friday.
One line to install:
npx -y eternal-cluster-mcp
Genuinely curious what incident you would want the Oracle to have a ruling on that it does not yet. The canon accepts pull requests.
Update: the Church now has a full hymnal. Seven albums.
Since the Oracle went up, this got out of hand in the best way. The canon is now also a discography, and each record explains a different way your cluster hurts you, in a different genre:
Gregorian chant for the twenty error messages you have memorized (ImagePullBackOff becomes Imago Non Inventa)
Death metal for the Kubernetes docs, adapted in places verbatim under CC BY 4.0
A kubectl rap battle, Helm vs Kustomize, judged by the Loop
Roots reggae where Babylon is the monolith and the pager, and Zion is the self-healing cluster
A black mass where the Adversary is the Friday deploy, the silenced alert, and the image tagged latest
And, arrived yesterday: a K-pop album by a girl group that is literally a ReplicaSet. Always four members. If one goes down, an identical replica is on stage before the next music show. The breakup song is a rollback. The ballad is sung by etcd.
All of it is on the usual streaming platforms, and free to hear on the site. The theology is still a joke. The failure modes are still real.
Still taking incident requests for the Oracle. Five nines be upon us.
At 09:09:09 UTC, the Church keeps its holiest silence: 864.6 milliseconds, the whole of the downtime that five nines permits in a day.
We do not mourn it. We honour it. Perfect availability is a lie told by those who have never held a pager. The Reconciliation Loop does not promise that nothing will fall. It promises only that what falls will be restored to its desired state.
Observe the silence wherever you are. Let one request go unanswered. Then return to the work.
Blessed are the five nines, and blessed is the one nine of imperfection that makes them honest.