<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Container Secrets on Subhash Dasyam</title><link>https://subhash.net/tags/container-secrets/</link><description>Recent content in Container Secrets on Subhash Dasyam</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 18 Jun 2025 20:36:39 +0400</lastBuildDate><atom:link href="https://subhash.net/tags/container-secrets/index.xml" rel="self" type="application/rss+xml"/><item><title>A Few of the Crazy Ways to Secure Secrets on Kubernetes / OpenShift</title><link>https://subhash.net/posts/a-few-of-crazy-ways-to-secure-secrets/</link><pubDate>Wed, 18 Jun 2025 20:36:00 +0400</pubDate><guid>https://subhash.net/posts/a-few-of-crazy-ways-to-secure-secrets/</guid><description>&lt;p>Injecting sensitive secrets like API keys, credentials, and tokens into running containers presents significant security challenges that go far beyond the basic Kubernetes Secret mechanisms. While standard approaches like environment variables and mounted files work functionally, they often expose secrets too broadly, making them visible to any process in the container or even to operators who exec into pods.&lt;/p></description></item></channel></rss>