<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>K8s on fabian.run</title>
    <link>https://fabian.run/tags/k8s/</link>
    <description>Recent content in K8s on fabian.run</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 01 Nov 2022 10:49:06 +0200</lastBuildDate>
    <atom:link href="https://fabian.run/tags/k8s/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>TIL: k8s sealed secrets only work with explicit namespace(s)</title>
      <link>https://fabian.run/posts/til_sealed_secret_namespaces/</link>
      <pubDate>Tue, 01 Nov 2022 10:49:06 +0200</pubDate>
      <guid>https://fabian.run/posts/til_sealed_secret_namespaces/</guid>
      <description>&lt;p&gt;When using the bitnami sealed secrets controller&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt; in your kubernetes cluster you explicitly have to&#xA;set the namespace of your secret before generating the SealedSecret &lt;code&gt;.yaml&lt;/code&gt;.&lt;/p&gt;&#xA;&lt;p&gt;When you omit the namespace metadata &lt;code&gt;namespace: default&lt;/code&gt; will be added by the &lt;code&gt;kubeseal&lt;/code&gt; cli and&#xA;the controller will then not be able to decrypt the secret into your actual namespace. You will get the&#xA;error message: &lt;code&gt;no key could decrypt secret&lt;/code&gt;.&lt;/p&gt;&#xA;&lt;p&gt;The namespace is part of the encryption to prevent that someone just decrypts the secret into another namespace&#xA;with different access rights and then will be able to read the contents of the decrypted secret&#xA;there&lt;sup id=&#34;fnref:2&#34;&gt;&lt;a href=&#34;#fn:2&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;2&lt;/a&gt;&lt;/sup&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
