operational: deploy hero ecosystem on K8s cluster #15
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
ask Kristof which books are good
can be as current web format (just html based, like now), so we have something live
make sure all other "now" issues resolved
Proof of Concept — Live
A single-VM deployment is live at https://herobooks.gent02.grid.tf, proving the software works end-to-end:
/mcp(6 tools for AI agents)Deployment infra:
deploy/single-vm/(OpenTofu + zinit, no Docker)Remaining for Production
Update: Removed the live single vm for now
@despiegk can you confirm which books you want live on the cluster? Then we can bring it live. Thanks.
Kristof, do we bring it live? Can you confirm which books you want? Should be straightforward afterwards. We can sync with ops to bring an instance live.
We can even do
operationalto operational: deploy hero ecosystem on K8s clusterStatus update
CI is now green on PR #64 — hero_books builds and passes all tests (fmt, clippy, unit tests, smoke tests).
What needs to deploy on the K8s cluster
The full hero ecosystem, not just hero_books alone:
Blocking items
Ready
Moved to hero_services
hero_books doesn't deploy independently — it runs as one of 12+ services inside the hero_services Docker image, managed by zinit via
hero_zero run.The deployment/operational concern belongs at the orchestrator level:
→ lhumina_code/hero_services#24 — Deploy hero_services on Jan's K8s cluster
That issue covers K8s manifests, persistent volumes, ingress, CI/CD image publishing, and the priority libraries (geomind, ourworld, mycelium).
hero_books status
All hero_books issues are now resolved:
Closing.