<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Secrets - Tag - vo.rs</title><link>https://vo.rs/tags/secrets/</link><description>Secrets - Tag - vo.rs</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Thu, 19 Dec 2024 10:00:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/secrets/" rel="self" type="application/rss+xml"/><item><title>Kubernetes Secrets Management: SOPS, Sealed Secrets, or External Secrets</title><link>https://vo.rs/story/kubernetes-secrets-management-sops-sealed-secrets-or-external-secrets/</link><description>&lt;p&gt;Kubernetes Secrets are not secret. That&amp;rsquo;s the first thing nobody tells you. A &lt;code&gt;Secret&lt;/code&gt; object is base64-encoded YAML sitting in etcd, and base64 is encoding, not encryption — anyone with &lt;code&gt;get secrets&lt;/code&gt; on the namespace can read it back in plaintext with a single command. Encryption at rest in etcd helps a little, but the real problem turns up the moment you adopt GitOps: now you want everything in a repo, and committing a base64 blob of your database password to Git is the kind of decision that ends careers. So you reach for tooling. There are three serious contenders, and I&amp;rsquo;ve run all of them in anger.&lt;/p&gt;</description><pubDate>Thu, 19 Dec 2024 10:00:00 +0000</pubDate></item></channel></rss>