<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Mlflow on BalkanDevOps</title><link>https://www.balkandevops.com/tags/mlflow/</link><description>Recent content in Mlflow on BalkanDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 18 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.balkandevops.com/tags/mlflow/index.xml" rel="self" type="application/rss+xml"/><item><title>MLflow on Kubernetes: why the community chart is not enough</title><link>https://www.balkandevops.com/posts/mlflow-on-kubernetes-community-chart-not-enough/</link><pubDate>Thu, 18 Jun 2026 00:00:00 +0000</pubDate><guid>https://www.balkandevops.com/posts/mlflow-on-kubernetes-community-chart-not-enough/</guid><description>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.</description></item></channel></rss>