vault-k8s
sops-secrets-operator
Our great sponsors
| vault-k8s | sops-secrets-operator | |
|---|---|---|
| 5 | 4 | |
| 734 | 248 | |
| 1.9% | - | |
| 0.0 | 0.0 | |
| 10 days ago | 13 days ago | |
| Go | Go | |
| Mozilla Public License 2.0 | 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-k8s
-
GitOps and Kubernetes – Secure Handling of Secrets
Hashicorp Vault k8s is an operator that modifies pods via a mutating webhook to connect between vault and pod via sidecars (additional containers) to provide secrets. This has the major advantage that no secret objects are created in Kubernetes here. The disadvantage is that this way only works with Vault.
-
Solving ArgoCD Secret Management with the argocd-vault-plugin
They’ve made it so you can define the order that the vault sidecar starts in, so that the proxy will be running first. https://github.com/hashicorp/vault-k8s/issues/53
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?
kubernetes-external-secrets - Integrate external secret management systems with Kubernetes
argo-cd - Declarative continuous deployment for Kubernetes.
sealed-secrets - A Kubernetes controller and tool for one-way encrypted Secrets
terraform-k8s - Terraform Cloud Operator for Kubernetes
fleet - Deploy workloads from Git to large fleets of Kubernetes clusters
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
flux2 - Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.
awx - AWX provides a web-based user interface, REST API, and task engine built on top of Ansible. It is one of the upstream projects for Red Hat Ansible Automation Platform.
kustomize-sops - KSOPS - A Flexible Kustomize Plugin for SOPS Encrypted Resources