<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kubernetes Security on Subhash Dasyam</title><link>https://subhash.net/tags/kubernetes-security/</link><description>Recent content in Kubernetes Security on Subhash Dasyam</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 23 Dec 2025 21:36:22 +0400</lastBuildDate><atom:link href="https://subhash.net/tags/kubernetes-security/index.xml" rel="self" type="application/rss+xml"/><item><title>Policy-as-Code for AI Workloads in Kubernetes: Kyverno/OPA Patterns for Model and Data Safety</title><link>https://subhash.net/posts/policy-as-code-for-ai-workloads-in-kubernetes/</link><pubDate>Tue, 23 Dec 2025 21:26:17 +0400</pubDate><guid>https://subhash.net/posts/policy-as-code-for-ai-workloads-in-kubernetes/</guid><description>&lt;h2 id="1-why-this-matters">1. Why This Matters&lt;/h2>
&lt;p>Your container is signed. Your image is scanned. Your CVE count is zero.&lt;/p>
&lt;p>None of that stops a backdoored model from running inference.&lt;/p>
&lt;p>Container security and model security are different problems. Traditional Kubernetes hardening protects the runtime environment. It does not protect against:&lt;/p></description></item><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>