Operations¶
Everything in the cluster is described in Git and deployed by Argo CD. This section is for maintainers and anyone running their own copy.
| Page | For |
|---|---|
| Environments and delivery | Production and staging in one cluster, and how an image or chart change rolls out |
| Argo CD | The Applications, what lives where, and day-to-day deploys and rollbacks |
| Observability | Tracing to Langfuse, the live and evaluation projects, environments |
| Ingestion pipelines | Loading docs, issues and code into Milvus with Kubeflow Pipelines |
Ground rules¶
- Git is the only writer. No
kubectl editon managed namespaces. A change is a pull request; Argo CD shows anything else as drift. - Secrets never go in Git. Charts reference Kubernetes Secrets by name. The
list of Secrets to create is in
deploy/argocd/README.md. - GPU releases are synced by hand.
llm-runtimeandllm-judgerestart a GPU pod and reload a model, so they never auto-sync. - CI never touches the cluster. It tests every PR and, on
main, builds and pushes images. Argo CD deploys.