sops-secrets-operator
webui
| sops-secrets-operator | webui | |
|---|---|---|
| 4 | 3 | |
| 286 | 137 | |
| - | - | |
| 7.7 | 3.0 | |
| 13 days ago | almost 2 years ago | |
| Go | TypeScript | |
| 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.
webui
-
GitOps using Flux and Flagger
There is no UI for Flux. It does have an experimental UI that is not in an active development state at the time of writing this.
-
Automation assistants: GitOps tools in comparison
This allows the developer to analyze their deployments and correct errors all without having to access the cluster. For authentication , there are interfaces for common protocols, such as LDAP and OIDC. Via configurable roles and groups, users can granted access the projects and applications for which they are responsible. The developers of Flux v2 are currently working on a web interface. However, it is still in an experimental state.
-
Deploying to different namespaces via Jenkins in k8s (and secrets mgmt)
That's what I said: "I'm a Flux guy." I agree that Flux v2 is much better than Flux v1. But setting up ArgoCD is a drag. With Flux, you just run the CLI command and everything is committed to the repo and deployed in the cluster. Flux is only missing the UI but I think that this will change soon (https://github.com/fluxcd/webui).
What are some alternatives?
kubernetes-external-secrets - Integrate external secret management systems with Kubernetes
Flux - Successor: https://github.com/fluxcd/flux2
argo-cd - Declarative Continuous Deployment for Kubernetes
werf - A solution for implementing efficient and consistent software delivery to Kubernetes facilitating best practices.
sealed-secrets - A Kubernetes controller and tool for one-way encrypted Secrets
fleet - Deploy workloads from Git to large fleets of Kubernetes clusters
cluster-api - Home for Cluster API, a subproject of sig-cluster-lifecycle
terraform-k8s - Terraform Cloud Operator for Kubernetes
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.
sops - Simple and flexible tool for managing secrets
kamus - An open source, git-ops, zero-trust secret encryption and decryption solution for Kubernetes applications