From 4d9d537d83cb02e864b3d96367d5d0ce2bdaf4d6 Mon Sep 17 00:00:00 2001 From: Andrew Stoltz Date: Mon, 27 Apr 2026 16:56:35 -0500 Subject: [PATCH] fix(knowledge): repoint Ollama at edge1 + flip README to LIVE (Sprint E B7) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Two changes after the Phase 2.4 deploy went live at https://knowledge.iamworkin.lan: 1. **Ollama URL flip**: from BLUEJAY-WS (10.0.56.20:11434) to edge1 Pi 5 (10.0.57.17:11434). Honors the cluster-clean architecture from bluejay-infra@0f9d56e ("Workstation is private dev hardware and should not be in the cluster path"). Query-time embeddings (~ms per query) are fast enough on edge1; bulk index rebuilds (Phase 2.5+) will need a separate ingestion lane that can opt into the workstation GPU when present. ArgoCD picks up the env-var change and rolls the pod automatically — no image rebuild needed. 2. **README LIVE status**: flip the staged-not-yet-applied banner to LIVE 2026-04-27. Pod running, certificate issued, PVC bound, /healthz 200, /api/v1/editions [] (initial-deploy state). Phase 2.5+ admin UI handles bulk population. Co-Authored-By: Claude Opus 4.7 (1M context) --- apps/knowledge/README.md | 8 ++++++-- apps/knowledge/knowledge.yaml | 11 +++++++---- 2 files changed, 13 insertions(+), 6 deletions(-) diff --git a/apps/knowledge/README.md b/apps/knowledge/README.md index 89e9c70..34679ae 100644 --- a/apps/knowledge/README.md +++ b/apps/knowledge/README.md @@ -1,7 +1,11 @@ # knowledge — FlowerCore.Knowledge.Web (Phase 2.4 K8s deploy) -**Status:** manifests staged, **NOT YET APPLIED**. Image must be built + -imported AND DNS record provisioned before `git push`. +**Status:** **LIVE 2026-04-27** at `https://knowledge.iamworkin.lan` — +Phase 2.4 closed. Pod running, certificate issued (step-ca-acme), PVC +bound (Longhorn 20Gi RWO), ArgoCD `infra-knowledge` synced. `/healthz` +returns 200, `/api/v1/editions` returns `[]` (initial-deploy state — no +*.db files in the PVC yet; Phase 2.5+ admin UI handles bulk +population). - Plan: [`../../../FlowerCore.Notes/docs/ai-agents/flowercore-knowledge-service-plan.md`](../../../FlowerCore.Notes/docs/ai-agents/flowercore-knowledge-service-plan.md) - Sprint: [`../../../FlowerCore.Notes/docs/ai-station/sprint-e-xxl-plan.md`](../../../FlowerCore.Notes/docs/ai-station/sprint-e-xxl-plan.md) (Track B) diff --git a/apps/knowledge/knowledge.yaml b/apps/knowledge/knowledge.yaml index 1467ad8..84159be 100644 --- a/apps/knowledge/knowledge.yaml +++ b/apps/knowledge/knowledge.yaml @@ -116,11 +116,14 @@ spec: value: "50" - name: FlowerCore__Editions__ProfileDirectory value: "/app/editions" - # Embed via BLUEJAY-WS GPU (R9700, 32GB VRAM). Pi5 Ollama is - # ~4-5x slower; use the workstation while we have it. - # Memory: feedback_pi5_nomic_embed_slow. + # Embed via edge1 Pi 5 + AI HAT+ (10.0.57.17:11434). Cluster + # services do not depend on BLUEJAY-WS (private dev hardware) per + # bluejay-infra@0f9d56e. Query-time embedding is fast enough on + # edge1 (~ms per query); bulk index rebuilds (Phase 2.5+) will + # need a separate ingestion lane that can opt into the + # workstation GPU when present. - name: FlowerCore__Ollama__BaseUrl - value: "http://10.0.56.20:11434" + value: "http://10.0.57.17:11434" resources: requests: cpu: 100m