title: k3s secrets.yaml produces an unexpected result after decryption
body: <p>I am taking over a k3s cluster and am trying to solve a problem with this:</p>
  <pre><code>apiVersion: v1
  kind: Secret
  metadata:
    name: clouddesktop-prod-secrets
    namespace: clouddesktop-prod
  data:
    tskey: dHNrZXkta0drTWVWNkNOVFJMLVNlRkZKVFFRalM3RDgzRllvVkxCTQ==
  </code></pre>
  <p>... is used along with with this snippet in my deployment.yaml</p>
  <pre><code>    - name: AUTHKEY
        valueFrom:
          secretKeyRef:
            name: clouddesktop-prod-secrets
            key: tskey
  </code></pre>
  <p>If I am understanding it correctly, the value under tskey will be &quot;decrypted&quot; and then made available as an envirnment variable called ENV_AUTHKEY.</p>
  <p>In other words the decryption process that k3s applies will convert the encrypted value &quot;dHNrZXkta0drTWVWNkNOVFJMLVNlRkZKVFFRalM3RDgzRllvVkxCTQ==&quot; into a plaintext value, e.g. &quot;tskey-abc145f&quot; and makes it available to the runnning container as environment variable &quot;ENV_AUTHKEY&quot;</p>
  <p>I have verified that indeed an environment variable called &quot;ENV_AUTHKEY&quot; is created, in other words that k3s appends ENV_ to the name.</p>
  <p>But as far as I can tell the plaintext is wrong. The environment variable &quot;ENV_AUTHKEY&quot; is indeed created, but, it seems to not have the expected value.</p>
  <p>Now by the documentation left for me by my predecessor, I am to create the encrypted value with this simple step:</p>
  <pre><code>echo -n &quot;tskey-abc145f&quot; | base64
  </code></pre>
  <p>So I am using base64 as the &quot;encryption&quot; expecting that this is what k3s expects. But the eventually decrypted value appears to me to be incorrect.</p>
  <p>What I am trying to determine is what k3s will use to decrypt my encrypted value.</p>