<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Istio on StackSimplify | DevOps &amp; Cloud Education by Kalyan Reddy</title><link>https://stacksimplify.com/tags/istio/</link><description>Recent content in Istio on StackSimplify | DevOps &amp; Cloud Education by Kalyan Reddy</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Tue, 14 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://stacksimplify.com/tags/istio/index.xml" rel="self" type="application/rss+xml"/><item><title>A/B Testing for ML Models: When Offline Metrics Lie</title><link>https://stacksimplify.com/blog/ab-testing-ml-models/</link><pubDate>Tue, 14 Apr 2026 00:00:00 +0000</pubDate><guid>https://stacksimplify.com/blog/ab-testing-ml-models/</guid><description>You retrained the model. Accuracy went up 2% on the test set. You deployed it. Revenue dropped 5%.
What happened? Offline metrics lie. A model that scores better on historical data can score worse on real users.
Canary vs A/B Testing Approach Question It Answers Traffic Split Canary &amp;ldquo;Does it break anything?&amp;rdquo; 10-20% to new model A/B Testing &amp;ldquo;Does it actually improve outcomes?&amp;rdquo; 50/50 to both models You need both. Canary first, then A/B.</description></item><item><title>Canary Deployments for ML Models with KServe and Istio</title><link>https://stacksimplify.com/blog/canary-rollouts-ml-models/</link><pubDate>Tue, 14 Apr 2026 00:00:00 +0000</pubDate><guid>https://stacksimplify.com/blog/canary-rollouts-ml-models/</guid><description>You do canary deployments for APIs every day. Why not for ML models?
New model ready. Looks good in testing. Deploy to production. Hope it works. It doesn&amp;rsquo;t. Rollback takes 5 minutes. Five minutes of garbage predictions. Damage done.
How It Works Role Traffic Description Champion (80%) Production traffic Current model, proven, stable Canary (20%) Test traffic New version, running alongside Both run simultaneously. Same endpoint. Istio handles the traffic split.</description></item></channel></rss>