Crowkis on Kubernetes: a well-behaved citizen
One container, a PVC, real health probes, hard memory bounds, graceful shutdown. Everything your cluster expects from a tenant that's read the manual.
Kubernetes rewards workloads with simple shapes, and Crowkis's shape is the simplest: one container, one persistent volume at /data, configuration entirely via environment. A Deployment (or StatefulSet, if you prefer the identity semantics) with a PVC is the whole manifest story — no operators, no CRDs, no sidecar entourage.
The probes are real: /health is wired into the image and reports actual readiness, including whether admin auth is active, so the kubelet's view matches reality. SIGTERM triggers graceful shutdown with WAL integrity preserved — pod rescheduling is a non-event, with the corpus intact on the PVC when the replacement mounts it.
Four doors in, one cache, and the model only sees genuinely new questions.
Resource governance is honest because the runtime has no garbage collector lying about memory: CROWKIS_MEMORY_LIMIT and the block-cache bound mean requests and limits you set are bounds the process actually respects. No OOMKill roulette, no mystery RSS growth at 3 a.m.
The bottom line
Run one instance per cluster license, scale it vertically (free), and let your existing Prometheus operator scrape /metrics. The Helm chart packages this shape for one-line installs — but the shape was always simple enough that the chart is a convenience, not a requirement.