sealed-secrets-web
sops-secrets-operator
| sealed-secrets-web | sops-secrets-operator | |
|---|---|---|
| 1 | 4 | |
| 55 | 287 | |
| - | - | |
| 8.4 | 7.7 | |
| 5 days ago | 14 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.
sealed-secrets-web
-
GitOps and Kubernetes – Secure Handling of Secrets
An option that easily works with GitOps is the Operator Sealed Secrets from Bitnami. Secrets encrypted with it can only be decrypted by operators running inside the cluster, not even by the original author. For encryption, there is a CLI (and a third-party web UI) that requires a connection to the cluster. The disadvantage of this is that the key material is stored in the cluster, the secrets are bound to the cluster and one has to take care of backups and operation.
sops-secrets-operator
-
Secret Management in Kubernetes: Approaches, Tools, and Best Practices
sops-secrets-operator (sops)
-
GitOps and Kubernetes – Secure Handling of Secrets
There is also a third-party sops-secrets operator available.
-
How to pass credentials to my app?
I have configured sops-secret-controller too, I'll be using that to manage my secrets. But my problem is that I don't know beforehand the value.
-
Automation assistants: GitOps tools in comparison
SOPS that was developed by Mozilla offers significantly more options, though at the expense of a more complex configuration. Here, the key material can come from the key management systems (KMS) of the major cloud providers, from your own HashiCorp Vault, or from configured PGP keys. SOPS itself does not contain an operator, but there are different ways to use it with GitOps. Flux v2 offers native support. There is also the helm-secrets plug-in, which can also be used in ArgoCD with the manual configuration. There is also a sops-secrets operator that has been developed by a third party.
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
argocd-vault-plugin - An Argo CD plugin to retrieve secrets from Secret Management tools and inject them into Kubernetes secrets
argo-cd - Declarative Continuous Deployment for Kubernetes
vault-k8s - First-class support for Vault and Kubernetes.
external-secrets - External Secrets Operator reads information from a third-party service like AWS Secrets Manager and automatically injects the values as Kubernetes Secrets.
fleet - Deploy workloads from Git to large fleets of Kubernetes clusters
terraform-k8s - Terraform Cloud Operator for Kubernetes
sops - Simple and flexible tool for managing secrets
cluster-api - Home for Cluster API, a subproject of sig-cluster-lifecycle
Flux - Successor: https://github.com/fluxcd/flux2