operational: deploy hero ecosystem on K8s cluster #15

Closed
opened 2026-02-07 15:09:13 +00:00 by despiegk · 5 comments
Owner
  • bring live in kubernetes cluster Jan
  • geomind
  • ourworld
  • mycelium

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

+ bring live in kubernetes cluster Jan - geomind - ourworld - mycelium 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
despiegk added this to the next milestone 2026-02-07 15:09:13 +00:00
despiegk added this to the ACTIVE project 2026-02-07 15:09:13 +00:00
despiegk removed this from the ACTIVE project 2026-02-07 15:12:43 +00:00
despiegk modified the milestone from next to now 2026-02-07 15:14:50 +00:00
despiegk added this to the ACTIVE project 2026-02-07 15:14:52 +00:00
Owner

Proof of Concept — Live

A single-VM deployment is live at https://herobooks.gent02.grid.tf, proving the software works end-to-end:

  • All 3 libraries loaded: GeoMind (9 books), Mycelium (21 books), OurWorld (6 books)
  • Semantic search with AI summary
  • MCP endpoint at /mcp (6 tools for AI agents)
  • HTML-based UI (current web format)
  • All other "now" issues resolved (26 closed)

Deployment infra: deploy/single-vm/ (OpenTofu + zinit, no Docker)

Remaining for Production

  • Book curation: Kristof to confirm which books are appropriate for public sharing
  • k3s cluster deployment: Ops to deploy on kubernetes (single-VM is PoC only)

Update: Removed the live single vm for now

## Proof of Concept — Live A single-VM deployment is live at **https://herobooks.gent02.grid.tf**, proving the software works end-to-end: - All 3 libraries loaded: GeoMind (9 books), Mycelium (21 books), OurWorld (6 books) - Semantic search with AI summary - MCP endpoint at `/mcp` (6 tools for AI agents) - HTML-based UI (current web format) - All other "now" issues resolved (26 closed) Deployment infra: `deploy/single-vm/` (OpenTofu + zinit, no Docker) ## Remaining for Production - **Book curation**: Kristof to confirm which books are appropriate for public sharing - **k3s cluster deployment**: Ops to deploy on kubernetes (single-VM is PoC only) --- Update: Removed the live single vm for now
Owner

@despiegk can you confirm which books you want live on the cluster? Then we can bring it live. Thanks.

@despiegk can you confirm which books you want live on the cluster? Then we can bring it live. Thanks.
Owner

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

  • Private instance with password for internal docs
  • Public instance without password
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 - Private instance with password for internal docs - Public instance without password
mik-tf changed title from operational to operational: deploy hero ecosystem on K8s cluster 2026-02-26 03:36:49 +00:00
Owner

Status 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:

  1. hero_services (formerly hero_zero) — orchestrator that manages 12+ hero services via zinit. Produces a fat Docker image with all services. hero_books is one of its managed services.
  2. hero_archipelagos — pure WASM frontend (Dioxus 0.7). Produces static WASM/JS/HTML files. Needs a web server (nginx or hero_books itself) to serve the assets. The books island UI lives here.
  3. hero_embedder — vector search service (runs alongside hero_books for semantic search features).

Blocking items

Ready

  • hero_books CI: passing (PR #64)
  • hero_services: active development by Timur, Docker image builds
  • hero_books libraries: geomind, ourworld, mycelium all present in examples/ebooks_local
## Status 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: 1. **hero_services** (formerly hero_zero) — orchestrator that manages 12+ hero services via zinit. Produces a fat Docker image with all services. hero_books is one of its managed services. 2. **hero_archipelagos** — pure WASM frontend (Dioxus 0.7). Produces static WASM/JS/HTML files. Needs a web server (nginx or hero_books itself) to serve the assets. The books island UI lives here. 3. **hero_embedder** — vector search service (runs alongside hero_books for semantic search features). ### Blocking items - K8s cluster from Jan - Kubernetes manifests / Helm charts (none exist yet on Forge) - hero_archipelagos wiring: https://forge.ourworld.tf/lhumina_code/hero_archipelagos/issues/13 ### Ready - hero_books CI: passing (PR #64) - hero_services: active development by Timur, Docker image builds - hero_books libraries: geomind, ourworld, mycelium all present in examples/ebooks_local
Owner

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:

  • CI is green (PR #64)
  • Native WASM UI moved to hero_archipelagos
  • Deployment tracked at hero_services level

Closing.

## 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: **→ https://forge.ourworld.tf/lhumina_code/hero_services/issues/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: - CI is green (PR #64) - Native WASM UI moved to hero_archipelagos - Deployment tracked at hero_services level Closing.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
lhumina_code/hero_books#15
No description provided.