<?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>BalkanDevOps</title><link>https://www.balkandevops.com/</link><description>Recent content on BalkanDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 29 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.balkandevops.com/index.xml" rel="self" type="application/rss+xml"/><item><title>Three ways to deploy Helm charts on Kubernetes, and when each one breaks</title><link>https://www.balkandevops.com/posts/helm-deployment-patterns/</link><pubDate>Mon, 29 Jun 2026 00:00:00 +0000</pubDate><guid>https://www.balkandevops.com/posts/helm-deployment-patterns/</guid><description>Most teams deploy Helm charts the way they did on day one and never revisit it. Here are the three patterns I&amp;#39;ve run in production, and where each one breaks.</description></item><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><item><title>Taming Azure AI Foundry with LiteLLM: budgets and key rotation</title><link>https://www.balkandevops.com/posts/taming-azure-ai-foundry-with-litellm/</link><pubDate>Sun, 07 Jun 2026 00:00:00 +0000</pubDate><guid>https://www.balkandevops.com/posts/taming-azure-ai-foundry-with-litellm/</guid><description>Azure AI Foundry is amazing until you have to manage it for more than one team. Here is how LiteLLM became the gateway that fixed my key sprawl, capped everyone&amp;rsquo;s spend, and turned key rotation from a fire drill into a thirty second job.</description></item></channel></rss>