operator
sops
operator | sops | |
---|---|---|
5 | 150 | |
1,096 | 15,160 | |
1.7% | 1.6% | |
9.4 | 9.0 | |
5 days ago | 9 days ago | |
Go | Go | |
GNU Affero General Public License v3.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.
operator
-
My recently deployed media apps in ArgoCD, migrating from Terraform.
minio has a k8 operator as well which I use at work: https://github.com/minio/operator
- Using Minio operator in AKS cluster. Minio tenants stuck in "Waiting for pod get ready" even though the pods are ready. What to do? Solution on git issues not helping :(
-
Need help adding TLS certificates to a tenant in a k3s cluster
So far I have seen some minio documentation (1, 2, ) about how to add the certificates correctly but I haven't been able to set it up correctly :-(
-
I'm slightly struggling to understand MinIO concepts
Yesterday, I tried to install MinIO, as I'm looking for a distributed object storage solution for Spark jobs on Kubernetes. I read the docs, went to the Github repo and followed the steps to install it using Helm. Here's what I did :
-
Monitor Minio with Prometheus on Kubernetes
Thank you! I assume you refer to this operator here, am I right? I will have a look at this, and also at the annotations possibility. Another question: is it deliberate that no Helm install is available?
sops
-
Pico.sh – Hacker Labs
My script just sets up default .sops.yaml for https://github.com/getsops/sops
You can further edit .sops.yaml(eg have multiple of them) and decide how you split secrets in your directory tree to further customize who can decrypt the secrets.
It works pretty well for prod/dev splits, etc
-
Encrypting your secrets with Mozilla SOPS using two AWS KMS Keys
Mozilla SOPS (Secrets OPerationS) is an open-source command-line tool for managing and storing secrets. It uses secure encryption methods to encrypt secrets at rest and decrypt them at runtime. SOPS supports a variety of key management systems, including AWS KMS, GCP KMS, Azure Key Vault, and PGP. It's particularly useful in a DevOps context where sensitive data like API keys, passwords, or certificates need to be securely managed and seamlessly integrated into application workflows.
-
An opinionated template for deploying a single k3s cluster with Ansible backed by Flux, SOPS, GitHub Actions, Renovate, Cilium, Cloudflare and more!
Encrypted secrets thanks to SOPS and Age
-
Tracking SQLite Database Changes in Git
We do the exact same thing to keep track of some credentials we use sops[1] and AWS KMS to separate credentials by sensitivity, then use the git differ to view the diffs between the encrypted secrets
Definitely not best practice security-wise, but it works well
[1] https://github.com/getsops/sops
-
The Twelve-Factor App
For anyone new to SOPS like I was - https://github.com/getsops/sops
- Storing and managing private keys
-
Show HN: Shello – Wrangle Environment Variables
I've found this is largely solved by strictly separating plain config and secrets, and then having secrets pull from GCP secret manager / vault / whatever.
You can then commit all the config (including the secret identifiers) and it all just works so long as you're authenticated with your secret storage system.
We do this for the live configuration as well in line with Gitops and find it to work well.
If you don't want to use a cloud secret manager you can also use something like https://github.com/getsops/sops to commit the encrypted secrets safely
-
Check your secrets into Git [video]
Basically, the simpler the better --just encrypt your secrets and check them in to version control.
We use SOPS[0] for this, and have found it to be pretty nice.
[0]: https://github.com/getsops/sops
-
How to secure secrets of docker-compose stacks with git?
The answer is that secrets shouldn't be stored in the git repo at all, but somewhere safe like a password manager or Mozilla's SOPS which people seem to love.
-
Is it safe to commit a Terraform file to GitHub?
Unfortunately, the SOPS project is in some sort of a limbo state and there has been quite a long period with limited maintenance and unclear position from Mozilla. Despite the project being accepted into the CNCF, it's still unclear what will happen with it going forward.
What are some alternatives?
longhorn - Cloud-Native distributed storage built on and for Kubernetes
sealed-secrets - A Kubernetes controller and tool for one-way encrypted Secrets
postgres-operator - PostgreSQL operator for Kubernetes
Vault - A tool for secrets management, encryption as a service, and privileged access management
certgen - A dead simple tool to generate self signed certificates for MinIO TLS deployments
age - A simple, modern and secure encryption tool (and Go library) with small explicit keys, no config options, and UNIX-style composability.
metallb - A network load-balancer implementation for Kubernetes using standard routing protocols
git-crypt - Transparent file encryption in git
home-ops - Wife approved HomeOps driven by Kubernetes and GitOps using Flux
terraform-provider-sops - A Terraform provider for reading Mozilla sops files
tofu-controller - A GitOps OpenTofu and Terraform controller for Flux
vault-secrets-operator - Create Kubernetes secrets from Vault for a secure GitOps based workflow.