spiffe-vault
vault-creds
| spiffe-vault | vault-creds | |
|---|---|---|
| - | 1 | |
| 76 | 84 | |
| - | - | |
| 8.3 | 5.5 | |
| 12 days ago | 3 months ago | |
| Go | Go | |
| MIT License | Apache License 2.0 |
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.
spiffe-vault
We haven't tracked posts mentioning spiffe-vault yet.
Tracking mentions began in Dec 2020.
vault-creds
-
Hashicorp Vault for Developers?
Exactly, we hide this from our devs. They can add secrets to hc vault via ui or via cli and know the „keywords“ to render it to properties. Which we then provide via env vars or properties file to app. For databases we do the same, there we use https://github.com/uswitch/vault-creds which hides the database related things. For encrypted communication we used in the past a sidecar with envoy that simply took certs from vault and in our apps we added the pki ca we managed via vault. So this was also hidden and devs not had to take care of encryption in their apps (today you use a service mesh for it) ;) and especially were also not affected by expired certs, as envoy has hot reload. For Kafka we still use this mechanism to implement authn and authz. There we have a callback which rotates pods when Kafka keystone is near expiry date. The only thing our devs have to worry about is encryption as a service. There I found so far no abstraction.
What are some alternatives?
spire - The SPIFFE Runtime Environment
argocd-vault-plugin - An Argo CD plugin to retrieve secrets from Secret Management tools and inject them into Kubernetes secrets
cosign - Code signing and transparency for containers and binaries
bank-vaults - A Vault swiss-army knife: A CLI tool to init, unseal and configure Vault (auth methods, secret engines).
vault-secrets-operator - Create Kubernetes secrets from Vault for a secure GitOps based workflow.
consul - Consul is a distributed, highly available, and data center aware solution to connect and configure applications across dynamic, distributed infrastructure.
in-toto-golang - A Go implementation of in-toto. in-toto is a framework to protect software supply chain integrity.
external-secrets - External Secrets Operator reads information from a third-party service like AWS Secrets Manager and automatically injects the values as Kubernetes Secrets.
vault-csi-provider - HashiCorp Vault Provider for Secret Store CSI Driver
helm-secrets - A helm plugin that help manage secrets with Git workflow and store them anywhere
boundary - Boundary enables identity-based access management for dynamic infrastructure.