<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Kubernetes on KeyValueStore.com</title>
    <link>https://keyvaluestore.com/tags/kubernetes/</link>
    <description>Recent content in Kubernetes on KeyValueStore.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 06 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://keyvaluestore.com/tags/kubernetes/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Revision Viewer Opens etcd Snapshots and Shows Every Revision of a Kubernetes Object the Way kubectl Prints It</title>
      <link>https://keyvaluestore.com/revision-viewer-opens-etcd-snapshots-and-shows-every-revision-of-a-kubernetes-object-the-way-kubectl-prints-it/</link>
      <pubDate>Tue, 06 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://keyvaluestore.com/revision-viewer-opens-etcd-snapshots-and-shows-every-revision-of-a-kubernetes-object-the-way-kubectl-prints-it/</guid>
      <description>&lt;p&gt;A Kubernetes cluster stops taking changes, and the API server reports &lt;code&gt;etcdserver: mvcc: database space exceeded&lt;/code&gt;. etcd has hit its quota, 2 GiB unless someone raised it, and raised the NOSPACE alarm. Now the questions are what filled it, and whether a compaction, a defrag or a cleanup will get it back. etcd&amp;rsquo;s own tools give totals. They don&amp;rsquo;t say which resources take the space.&lt;/p&gt;&#xA;&lt;p&gt;The &lt;a href=&#34;https://keyvaluestore.com/tools/revisions/&#34;&gt;Revision Viewer&lt;/a&gt; opens an etcd snapshot, the file &lt;code&gt;etcdctl snapshot save&lt;/code&gt; writes, and shows what fills it: how close it is to the quota, which keys and Kubernetes resources take the space, how much is old revisions that compaction would remove, and how much is free pages that only a defrag gives back. Pick a key, and you see every revision the file keeps and what changed in each.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
