#artifacts

MLflow runs listed but artifacts return 404 after redeploy: artifacts stored inside the container

After we redeployed our MLflow tracking server on Kubernetes, every run older than the deploy showed metrics but no artifacts, and model loading failed. The server wrote artifacts to a local directory in the pod. We moved to proxied artifact storage on S3 and recovered what we could.