<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Scaling on gNMIc Operator</title><link>https://a2c17dad.gnmic-operator2.pages.dev/tags/scaling/</link><description>Recent content in Scaling on gNMIc Operator</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 12 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://a2c17dad.gnmic-operator2.pages.dev/tags/scaling/index.xml" rel="self" type="application/rss+xml"/><item><title>Target Distribution and Horizontal Pod Autoscaling</title><link>https://a2c17dad.gnmic-operator2.pages.dev/blog/2026-04-12-scaling-target-distribution/</link><pubDate>Sun, 12 Apr 2026 00:00:00 +0000</pubDate><guid>https://a2c17dad.gnmic-operator2.pages.dev/blog/2026-04-12-scaling-target-distribution/</guid><description>&lt;p>Every telemetry deployment eventually hits the same question: how many collector pods do you need, and what happens when that number changes? A new datacenter comes online and 200 targets get added to the inventory. A firmware rollout restarts half the fabric and every device reconnects at once. The three gNMIc pods that handled the workload comfortably are now saturated, and someone has to bump a replica count and wait for redistribution to settle.&lt;/p></description></item></channel></rss>