<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Kubernetes-Operators on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/kubernetes-operators/</link>
    <description>Recent content in Kubernetes-Operators on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 20 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/kubernetes-operators/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted MongoDB Operators: MongoDB Community vs Percona vs KubeBlocks</title>
      <link>https://www.pistack.xyz/posts/2026-05-20-self-hosted-mongodb-operators-mongodb-community-percona-kubeblocks-guide/</link>
      <pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-20-self-hosted-mongodb-operators-mongodb-community-percona-kubeblocks-guide/</guid>
      <description>&lt;p&gt;Running MongoDB in production on Kubernetes requires more than a simple StatefulSet and a headless service. You need automated replica set initialization, backup scheduling, version upgrades, scaling, and failover handling. That is where MongoDB Kubernetes operators come in — specialized controllers that encode operational best practices into declarative custom resources.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Self-Hosted MySQL Operators: Vitess vs RadonDB vs Presslabs MySQL Operator</title>
      <link>https://www.pistack.xyz/posts/2026-05-20-self-hosted-mysql-operators-vitess-radondb-presslabs-guide/</link>
      <pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-20-self-hosted-mysql-operators-vitess-radondb-presslabs-guide/</guid>
      <description>&lt;p&gt;MySQL remains one of the most widely deployed relational databases, but running it on Kubernetes introduces operational challenges that a standard Deployment cannot solve. Replica set management, automated failover, backup scheduling, schema migrations, and horizontal scaling all require specialized orchestration. MySQL Kubernetes operators encode these operational patterns into declarative custom resources, turning MySQL from a manually managed stateful workload into a cloud-native service.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
