Reloader
sops
Our great sponsors
Reloader | sops | |
---|---|---|
34 | 150 | |
6,718 | 15,114 | |
4.2% | 2.7% | |
9.0 | 9.0 | |
5 days ago | 4 days ago | |
Go | Go | |
Apache 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.
Reloader
-
How are people managing env vars for Static Applications?
You can combine this approach with something like https://github.com/stakater/Reloader to automatically restart pods when a certain secret value changes. So if your static code needs to be rebuilt when certain values change, you can use an init container to run the build on startup.
-
Containers are crashing due to memory exhaustion caused by secret rotation every minute.
This is not a cron job? I'm not sure if it helps, but you can have pods do a rolling restart on secret updates: https://github.com/stakater/Reloader that would clear the resources each run, but I'm not entirely clear on what you're looking to achieve.
-
True Secrets Auto Rotation with ESO and Vault
If you use secrets as Environment Variables you will need to use something to make workloads get the new credentials, if they just loose connection. You can use the Reloader project for that.
-
Automating Configuration Updates in Kubernetes with Reloader
Reloader is designed to simplify the process of updating application configurations in Kubernetes. It monitors ConfigMaps and Secrets for changes and triggers rolling upgrades for associated resources such as Deployments, StatefulSets, DaemonSets, and more. Reloader eliminates the need for manual intervention and reduces the risk of errors during the configuration update process.
-
How to start a Go project in 2023
The go k8s packages are pretty bloated - this may also just be a niche case. If you are looking to get secrets with hot reloading, you might also consider mounting a file or setting env vars and coupling it with this reloading operator: https://github.com/stakater/Reloader
-
What Wishlist Features Would You Like To See From K8s?
For the auto restart this has been a staple install in all clusters for years for me: https://github.com/stakater/Reloader
-
Flux & Helm noob here - How do I pass secret values to Helm charts being handled by Flux?
If you didn't want to use SOPS, for some reason, you can certainly take advantage of external secrets as another commenter proposed, but you won't be able to accomplish (2) without an external tool adding to the mix, like Reloader: https://github.com/stakater/Reloader – that's because something has to update the HelmRelease in order to trigger it to upgrade. (You could just wait for the reconciler to come along, but the tendency is to set the polling interval longer than the default, so Helm won't be re-trying as often, in case something goes wrong...)
- Create new pods upon secret/configmap change in pipeline
-
Environment variables - manifest or configMap?
You can install https://github.com/stakater/Reloader And then it's just matter of a single annotation and it restarts automatically when there are changes.
- AWS secret store CSI Driver provider - how to reload pod after SecretProvider update?
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?
kubernetes-external-secrets - Integrate external secret management systems with Kubernetes
sealed-secrets - A Kubernetes controller and tool for one-way encrypted Secrets
kubernetes-reflector - Custom Kubernetes controller that can be used to replicate secrets, configmaps and certificates.
Vault - A tool for secrets management, encryption as a service, and privileged access management
k8s-configmap-watcher
age - A simple, modern and secure encryption tool (and Go library) with small explicit keys, no config options, and UNIX-style composability.
flux2 - Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.
git-crypt - Transparent file encryption in git
helm-charts - Misc helm charts
terraform-provider-sops - A Terraform provider for reading Mozilla sops files
secrets-store-csi-driver-provider-gcp - Google Secret Manager provider for the Secret Store CSI Driver.
vault-secrets-operator - Create Kubernetes secrets from Vault for a secure GitOps based workflow.