MLflow on Kubernetes: why the community chart is not enough
The community MLflow chart is great for a demo and useless for production. It knows nothing about your Key Vault, your Workload Identity, your Traefik ingress, or your certs. Here is the layered Helm pattern I run instead, where the open source chart stays untouched and your cloud specifics live in a thin layer on top. Plus the one missing package that breaks Workload Identity on day one.