<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Kubernetes-Operator on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/kubernetes-operator/</link>
    <description>Recent content in Kubernetes-Operator on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 16 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/kubernetes-operator/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted ClickHouse Kubernetes Operations: Altinity Operator vs Official Operator vs clickhouse-backup</title>
      <link>https://www.pistack.xyz/posts/2026-05-16-self-hosted-clickhouse-kubernetes-operations-altinity-operator-clickhouse-backup-guide/</link>
      <pubDate>Sat, 16 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-16-self-hosted-clickhouse-kubernetes-operations-altinity-operator-clickhouse-backup-guide/</guid>
      <description>&lt;p&gt;ClickHouse has become the go-to OLAP database for real-time analytics, log processing, and time-series workloads. Deploying ClickHouse on Kubernetes brings scalability and resilience, but managing ClickHouse clusters at scale requires specialized tooling. This guide compares three essential tools for self-hosted ClickHouse operations on Kubernetes: the &lt;strong&gt;Altinity Kubernetes Operator&lt;/strong&gt;, the &lt;strong&gt;Official ClickHouse Operator&lt;/strong&gt;, and &lt;strong&gt;clickhouse-backup&lt;/strong&gt; for disaster recovery.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
