From c5cbb8f9b52df2ea9dcceeb48b9d52a4a67fbd09 Mon Sep 17 00:00:00 2001 From: David Wetmore <167476544+dwetmore@users.noreply.github.com> Date: Tue, 10 Feb 2026 17:49:30 -0500 Subject: [PATCH] docs: refresh README for ollama+openwebui deployment --- README.md | 28 ++++++++++++++++++---------- 1 file changed, 18 insertions(+), 10 deletions(-) diff --git a/README.md b/README.md index 2d3c854..f0650ae 100644 --- a/README.md +++ b/README.md @@ -4,27 +4,35 @@ This repository contains Kubernetes manifests for deploying a local LLM stack wi ## Current deployed architecture -The actively deployed stack is: +The active deployment includes only: -- **Ollama**: in-cluster LLM runtime and HTTP API (`ollama:11434`) -- **OpenWebUI**: the only user-facing web interface +- **Ollama**: in-cluster LLM runtime + HTTP API at `http://ollama:11434` +- **OpenWebUI**: the only user-facing web UI; it calls Ollama via in-cluster DNS Runtime flow: -1. User accesses OpenWebUI through ingress. -2. OpenWebUI sends model requests directly to Ollama via in-cluster DNS (`http://ollama:11434`). -3. Argo CD reconciles the manifests from this repo. +1. User opens OpenWebUI through ingress. +2. OpenWebUI sends model requests to `http://ollama:11434`. +3. Argo CD reconciles manifests from this repo. ## Repo layout -- `overlays/dev-ollama/`: deploys **only** Ollama and OpenWebUI (plus their PVCs, Service, and OpenWebUI Ingress). -- `base/`: older manifests present in the repo but not part of the `overlays/dev-ollama` deployment path. +- `overlays/dev-ollama/`: deploys only Ollama + OpenWebUI (PVCs, Services, and OpenWebUI Ingress). +- `base/`: deprecated legacy manifests; not used by `overlays/dev-ollama`. ## Ingress exposure (dev) -`overlays/dev-ollama/openwebui-ing.yaml` exposes only OpenWebUI using a nip.io hostname: +Ingress exposes **only OpenWebUI** (no chatbot ingress). -- `webui.172.17.93.185.nip.io` +Use this hostname pattern: + +- `webui..nip.io` + +Get `WSLIP` in WSL: + +```bash +hostname -I | awk '{print $1}' +``` ## Deploy with Argo CD