infrastructure
sops-secrets-operator
infrastructure | sops-secrets-operator | |
---|---|---|
3 | 4 | |
38 | 286 | |
- | - | |
9.7 | 7.7 | |
4 days ago | 11 days ago | |
YAML | Go | |
- | 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.
infrastructure
-
Nebox Inventory For Network Automation: Source Of Truth for Ansible Tower Playbook Device management
For my home infrastructure, I use Netbox as my source of truth for managing DNS and DHCP records. If that sounds interesting to you, here's my code: https://github.com/fred-drake/infrastructure
-
How to pass credentials to my app?
Feel free to peruse my solution for inspiration: https://github.com/fred-drake/infrastructure
- Home Infrastructure Ansible / Docker / K8S on Github
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?
ansible-role-k3s - Ansible role for installing k3s as either a standalone server or HA cluster.
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
home-ops - Wife approved HomeOps driven by Kubernetes and GitOps using Flux
cluster-template - A template for deploying a Kubernetes cluster with k3s or Talos
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