One Ollama Endpoint, Two Very Different Backends
Introduction Nine namespaces in my cluster depend upon a local language model. The SDR research stack tags transcriptions, the politics dashboard summarizes feeds, the congressional-trade tracker prepares daily summaries, and several agents submit work to the service continuously. Despite their differing purposes and operational rhythms, each consumer was designed to address one stable hostname on port 11434. That hostname fronts two active Ollama deployments: an RTX 5090 in a desktop tower that is intentionally powered down at intervals, and an NVIDIA GB10 Spark board whose unified-memory architecture causes GPU-backed allocations to count against the pod’s memory limit. The repository contains a CPU-only deployment manifest, but the active Kustomization excludes it under ordinary circumstances. The Spark deployment is therefore the operational fallback. ...