<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Announcement on gNMIc Operator</title><link>https://fbe70dc2.gnmic-operator2.pages.dev/tags/announcement/</link><description>Recent content in Announcement on gNMIc Operator</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 08 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://fbe70dc2.gnmic-operator2.pages.dev/tags/announcement/index.xml" rel="self" type="application/rss+xml"/><item><title>Introducing gNMIc Operator</title><link>https://fbe70dc2.gnmic-operator2.pages.dev/blog/2026-02-08-introducing-gnmic-operator/</link><pubDate>Sun, 08 Feb 2026 00:00:00 +0000</pubDate><guid>https://fbe70dc2.gnmic-operator2.pages.dev/blog/2026-02-08-introducing-gnmic-operator/</guid><description>&lt;p>Today we&amp;rsquo;re releasing &lt;strong>gNMIc Operator&lt;/strong>: A Kubernetes operator that brings cloud-native lifecycle management to &lt;a href="https://gnmic.openconfig.net/">gNMIc&lt;/a> telemetry collectors. It&amp;rsquo;s been a long road to get here, and I want to share a bit of the backstory.&lt;/p>
&lt;h2 id="an-idea-almost-4-years-in-the-making-todo-list">An idea almost 4 years in the &lt;del>making&lt;/del> TODO list&lt;/h2>
&lt;p>The idea was always clear: gNMIc should not only be a powerful CLI tool, but also a scalable, production-grade telemetry collector that could be orchestrated alongside the rest of your infrastructure. That led to multiple improvements to gNMIc (Clustering, Target Loaders,&amp;hellip;), but one of them was a bit more ambitious than the others: A gNMIc Kubernetes operator.&lt;/p></description></item></channel></rss>