You probably do not need Kubernetes
For most classical ML use cases, a single FastAPI server behind a load balancer is enough. The model is a few hundred MB; latency is a few ms; the team is two engineers. Reach for heavier infrastructure only when traffic, latency, or compliance demand it.
The minimum surface area
- An HTTP endpoint that accepts a raw row, returns probability + decision + version.
- A health endpoint for the load balancer.
- A version endpoint that returns model metadata.
- Structured logging of every prediction (input, output, version, latency).
- A circuit breaker to the rule-based fallback when the model fails.
The deployment ritual
Shadow-deploy first: route 10% of traffic to the new model, log predictions but use the old model's decision. Compare distributions. Promote only after the shadow passes. Always keep the previous artifact one click away for rollback.