<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Csi on Le Site de François</title><link>https://lesitedefrancois.be/en/tags/csi/</link><description>Recent content in Csi on Le Site de François</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 François</copyright><atom:link href="https://lesitedefrancois.be/en/tags/csi/index.xml" rel="self" type="application/rss+xml"/><item><title>Secrets Store CSI Driver</title><link>https://lesitedefrancois.be/en/security/csi-secret-store/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://lesitedefrancois.be/en/security/csi-secret-store/</guid><description>&lt;p&gt;&lt;strong&gt;Secrets Store CSI Driver&lt;/strong&gt; (formally &lt;code&gt;secrets-store.csi.k8s.io&lt;/code&gt;) is a Kubernetes SIG Auth project that uses the Container Storage Interface to mount secrets, certificates, and keys from external secret backends directly into pod filesystems as ephemeral &lt;code&gt;tmpfs&lt;/code&gt; volumes, bypassing the Kubernetes &lt;code&gt;Secret&lt;/code&gt; object and etcd entirely. The driver runs as a DaemonSet on every node; when a pod referencing a CSI volume of type &lt;code&gt;secrets-store.csi.k8s.io&lt;/code&gt; is scheduled, the driver communicates with a &lt;strong&gt;provider plugin&lt;/strong&gt; over gRPC to retrieve the secret content from the configured backend, writes it to a per-pod &lt;code&gt;tmpfs&lt;/code&gt; mount, and makes it available inside the container at the specified path. When the pod terminates, the &lt;code&gt;tmpfs&lt;/code&gt; is unmounted and the data is gone — secrets have no persistence beyond the lifetime of the pod that requested them.&lt;/p&gt;</description></item></channel></rss>