sops-secrets-operator
helm-secrets
sops-secrets-operator | helm-secrets | |
---|---|---|
4 | 12 | |
286 | 1,302 | |
- | - | |
7.7 | 8.3 | |
13 days ago | 9 days ago | |
Go | Shell | |
Mozilla Public License 2.0 | 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.
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.
helm-secrets
-
Simplified Deployment: A Deep Dive into Containerization and Helm
helm plugin install https://github.com/databus23/helm-diff helm plugin install https://github.com/aslafy-z/helm-git helm plugin install https://github.com/jkroepke/helm-secrets
-
My recently deployed media apps in ArgoCD, migrating from Terraform.
I use Helm secrets which integrates Mozilla Sops to handle secrets in my Helm charts.
-
How to Deploy and Scale Strapi on a Kubernetes Cluster 1/2
Use Helm Secrets.
-
Secret Management in Kubernetes: Approaches, Tools, and Best Practices
ArgoCD users would have to build container images with SOPS baked in using Helm chart extensions or Kustomize extensions. Flux allows configuring sops directly into the Flux manifests.
-
GitOps and Kubernetes – Secure Handling of Secrets
There is also the helm secrets plugin, which can also be used in ArgoCD with manual configuration.
-
Disable auto sync at application level when managed by ApplicationSet.
Not sure if this is applicable for your use case, but you could use helm-secrets to fetch remote value files from https or git: https://github.com/jkroepke/helm-secrets/wiki/Values
-
Goodbye Sealed Secrets, hello SOPS
$ helm plugin install https://github.com/jkroepke/helm-secrets --version v3.14.0
-
How should I manage my Helm charts?
https://github.com/jkroepke/helm-secrets powered by sops
-
Thoughts on using git-crypt
SOPS is great, and there are a lot of GitOps tools that either integrate with SOPS directly or make it relatively painless to integrate into your workflow, e.g. helm-secrets.
-
How to manage passwords in Helm
SOPS and helm-secrets: https://github.com/jkroepke/helm-secrets
What are some alternatives?
kubernetes-external-secrets - Integrate external secret management systems with Kubernetes
sealed-secrets - A Kubernetes controller and tool for one-way encrypted Secrets
argo-cd - Declarative Continuous Deployment for Kubernetes
vault-secrets-operator - Create Kubernetes secrets from Vault for a secure GitOps based workflow.
sops - Simple and flexible tool for managing secrets
fleet - Deploy workloads from Git to large fleets of Kubernetes clusters
argocd-operator - A Kubernetes operator for managing Argo CD clusters.
terraform-k8s - Terraform Cloud Operator for Kubernetes
argo-rollouts - Progressive Delivery for Kubernetes
hull - The incredible HULL - Helm Uniform Layer Library - is a Helm library chart to improve Helm chart based workflows