<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Operators on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/operators/</link>
    <description>Recent content in Operators on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 30 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/operators/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Kubernetes Monitoring Operators: kube-prometheus-stack vs VictoriaMetrics vs OpenTelemetry</title>
      <link>https://www.pistack.xyz/posts/2026-04-30-k8s-monitoring-operators-kube-prometheus-victoriametrics-opentelemetry-guide/</link>
      <pubDate>Thu, 30 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-04-30-k8s-monitoring-operators-kube-prometheus-victoriametrics-opentelemetry-guide/</guid>
      <description>&lt;p&gt;Monitoring a Kubernetes cluster requires collecting metrics from nodes, pods, containers, and the control plane, then storing, querying, and visualizing that data. The traditional approach — manually deploying Prometheus, configuring service monitors, setting up Grafana dashboards, and managing Alertmanager rules — is complex and error-prone.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
