KamoCRM

Keys and NetworkPolicies on in-cluster inference; Kamo reranker and Kamo Local LLM

FeatureKlusterServices
Shipped
September 25, 2026 at 12:44 AM UTC
Author
Kamo
Commit
9a8447f

TEI embeddings and the new cross-encoder reranker require TEI_API_KEY; bergamot, LibreTranslate and the new Kamo-owned Ollama (qwen3:4b) sit behind the Kamo auth proxy; ocrservice, TEI, the proxies and the LLM accept only their callers. Services switch to proxy ports only after each rollout completes. The proxy template sets map_hash_bucket_size 128: the 71-byte "Bearer <64 hex>" key does not fit nginx's default 64-byte bucket and nginx refuses to start. The reranker runs TEI cpu-1.9.4: 1.5's hf-hub 0.3.2 cannot follow the Hub's rename and resolve-cache redirects for this model. Each deploy step checks its server Secret and key exist before applying (the servers' references are required).

All changes

Like what you see shipping?

All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.

Start Free ForeverView Pricing