Из ленты dev.to devops — кратко, чтобы не потерять.
Quick take ChromaDB 1.0.0 rewrote the server in Rust and quietly broke most of the values.yaml configs you find online. Auth keys are ignored, logging keys are ignored, and the persistence semantics changed. Here is a values.yaml that actually works in production, with every block explained. If you only have 90 seconds, this is the shape: Use amikos-tech/chromadb-chart , the most maintained chart on Artifact Hub. For ChromaDB 1.0.0+ assume chromadb.auth.* is dead. Network-level security is the new model. Persistence is non-optional , since the Rust server always writes to disk and no PVC means no durability. Why the old guides will burn you in 2026 I spent half a Saturday last quarter migrating a ChromaDB deployment from 0.4.x to 1.0.x and watched four tutorials silently break. Three thing
Полный текст и контекст у первоисточника: https://dev.to/muskan_8abedcc7e12/chromadb-helm-valuesyaml-the-2026-production-setup-45hh