vault-secrets-operator
sops
| vault-secrets-operator | sops | |
|---|---|---|
| 5 | 157 | |
| 636 | 17,150 | |
| - | 1.9% | |
| 8.0 | 9.1 | |
| 6 days ago | 5 days ago | |
| Go | Go | |
| MIT License | Mozilla Public 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.
vault-secrets-operator
- 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.
sops
-
Git-crypt – transparent file encryption in Git
How does this compare to mozilla's sops[1]. I've heard sops is also used for this kind of usecase, although it seems to do much more.
[1] https://github.com/getsops/sops
-
Do not use secrets in environment variables and
You can also do some nice things with https://github.com/getsops/sops, I store encrypted password and secrets on git with sops, but I also use nix so I have near perfect integration with my services.
- Age is a simple, modern and secure file encryption tool, format, and Go library
-
Managing NixOS Secrets via SOPS, sops-nix and opsops
SOPS is a simple, yet powerful tool for managing secrets. It consumes a clear secret file in various formats and encrypts values using keys. The encrypted file can be then stored in a version control system and decrypted when needed.
-
From Dotenv to Dotenvx: Next Generation Config Management
There's also sops: https://github.com/getsops/sops
I've used it at two jobs now over about 5 years and have had zero issues.
-
Pico.sh – Hacker Labs
My script just sets up default .sops.yaml for https://github.com/getsops/sops
You can further edit .sops.yaml(eg have multiple of them) and decide how you split secrets in your directory tree to further customize who can decrypt the secrets.
It works pretty well for prod/dev splits, etc
-
Encrypting your secrets with Mozilla SOPS using two AWS KMS Keys
Mozilla SOPS (Secrets OPerationS) is an open-source command-line tool for managing and storing secrets. It uses secure encryption methods to encrypt secrets at rest and decrypt them at runtime. SOPS supports a variety of key management systems, including AWS KMS, GCP KMS, Azure Key Vault, and PGP. It's particularly useful in a DevOps context where sensitive data like API keys, passwords, or certificates need to be securely managed and seamlessly integrated into application workflows.
-
An opinionated template for deploying a single k3s cluster with Ansible backed by Flux, SOPS, GitHub Actions, Renovate, Cilium, Cloudflare and more!
Encrypted secrets thanks to SOPS and Age
-
Tracking SQLite Database Changes in Git
We do the exact same thing to keep track of some credentials we use sops[1] and AWS KMS to separate credentials by sensitivity, then use the git differ to view the diffs between the encrypted secrets
Definitely not best practice security-wise, but it works well
[1] https://github.com/getsops/sops
-
The Twelve-Factor App
For anyone new to SOPS like I was - https://github.com/getsops/sops
What are some alternatives?
sealed-secrets - A Kubernetes controller and tool for one-way encrypted Secrets
kubernetes-external-secrets - Integrate external secret management systems with Kubernetes
Vault - A tool for secrets management, encryption as a service, and privileged access management
Flux - Successor: https://github.com/fluxcd/flux2
age - A simple, modern and secure encryption tool (and Go library) with small explicit keys, no config options, and UNIX-style composability.
argocd-vault-plugin - An Argo CD plugin to retrieve secrets from Secret Management tools and inject them into Kubernetes secrets
git-crypt - Transparent file encryption in git
helm-secrets - A helm plugin that help manage secrets with Git workflow and store them anywhere
terraform-provider-sops - A Terraform provider for reading Mozilla sops files
atlantis - Terraform Pull Request Automation
terragrunt - Terragrunt is a flexible orchestration tool that allows Infrastructure as Code written in OpenTofu/Terraform to scale.