vault-csi-provider
HashiCorp Vault Provider for Secret Store CSI Driver (by hashicorp)
vault-secrets-operator
Create Kubernetes secrets from Vault for a secure GitOps based workflow. (by ricoberger)
vault-csi-provider | vault-secrets-operator | |
---|---|---|
1 | 5 | |
291 | 611 | |
0.3% | - | |
7.9 | 8.0 | |
13 days ago | 4 days ago | |
Go | Go | |
GNU General Public License v3.0 or later | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
vault-csi-provider
Posts with mentions or reviews of vault-csi-provider.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-07-17.
-
Inject Secrets into your Pod Environments at the Container Runtime
Why not use https://github.com/kubernetes-sigs/secrets-store-csi-driver to do this? Then you don't have a strict binding to runc. A live example of using the CSI driver with a secrets provider is https://github.com/hashicorp/vault-csi-provider
vault-secrets-operator
Posts with mentions or reviews of vault-secrets-operator.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-10-12.
- Toyota Accidently Exposed A Secret Key Publicly On GitHub For Five Years
-
Learning with K3s at home. Is it "better" to store secrets encrypted in the git repo (e.g., sealed-secrets) or in a separately managed secret database (e.g., vault)?
For home use, I wouldn't bother with Vault unless that's really what you want to learn. Then it's worth looking into setting something up where you could use vault secrets, using one of the available options (I haven't seen the vault-secrets-operator being mentioned).
-
Hashicorp Vault integration with Secret objects
It is but it affects vault-secrets-operator too, see https://github.com/ricoberger/vault-secrets-operator/issues/104 (and no, I’ve only use vault-secrets-operator)
-
Automation assistants: GitOps tools in comparison
If you are using an external KMS in any case, then there are other options, such as the kubernetes-external-secrets operator that was originally started by GoDaddy and the externalsecret-operator from Container Solutions. If you use HashiCorp Vault, you also have the option of using the Vault Secrets operator. This works similarly to the Sealed Secrets Operator, but instead of managing its own key material, it retrieves the secrets from Vault. The CNCF Technology Radar from January 2021 provides an overview of the types of tools that are available for secrets management.