MTmt42or·Dec 1, 2025Submission
Secret Store CSI is abandonned and should be shut down
1 points · Open discussionkubernetes-sigs
secrets-store-csi-driver
Go2020–2025
kubernetes-sigs / secrets-store-csi-driver
secrets-store-csi-driver
Secrets Store CSI driver for Kubernetes secrets - Integrates secrets stores with Kubernetes via a CSI volume.
3Distinct people
3Mentions
0Explicit recommenders
1.6KGitHub stars
What to know before exploring
What it is
Secrets Store CSI driver for Kubernetes secrets - Integrates secrets stores with Kubernetes via a CSI volume.
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year3 dated mentions
Observed mentions: 2020-10-22 14:39:06 UTC to 2025-12-01 07:18:25 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 1 | 1 | 0 |
What Hacker News says
3 sourcesI'm not a fan of this approach. I think the Secrets Store CSI Driver (https://github.com/kubernetes-sigs/secrets-store-csi-driver) has a better approach. It mounts secrets directly from a KMS (e.g. Vault, AWS KMS, GCP KMS, Azure Key Vault) into your application's file system.
Why not environment variables? Because files have stronger access control mechanisms than environment variables. Someone in the same PID namespace as your process can see your environment variables, but they can't necessarily see your files.(Although the driver does support environment variables for compatibility: https://secrets-store-csi-driver.sigs.k8s.io/topics/set-as-e...)
In Check your secrets into Git [video]I'm looking into this myself and ran across what looks to be a more "official" tool for this [1]. Kubernetes is a fast moving ecosystem and using random OSS operators has bit us in the past.
[1] https://github.com/kubernetes-sigs/secrets-store-csi-driver
In A Kubernetes operator to sync secrets from AWS Secrets Manager