Reloader
helm-secrets
Our great sponsors
Reloader | helm-secrets | |
---|---|---|
34 | 12 | |
6,590 | 1,261 | |
4.6% | - | |
9.0 | 8.4 | |
2 days ago | 18 days ago | |
Go | Shell | |
Apache 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.
Reloader
-
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
- AWS secret store CSI Driver provider - how to reload pod after SecretProvider update?
-
State of Kubernetes Secrets Management in 2022
Unfortunately, there isn't one out-of-the-box, elegant solution for triggering deployments to be reloaded with the solutions we've shown. You'd need to rely on open source tools such as Reloader, which watches for changes in ConfigMap and Secrets and does rolling upgrades on Pods with their associated Deployment, StatefulSet, DaemonSet, and DeploymentConfig.
-
One multi-container deployment vs. a separate deployment for each image?
It makes sense to use multiple containers for the same deployment, if they serve the same purpose, i.e. if there's a reloader present etc.
- Kubernetes Reload/Restart pod on file changes
-
How to monitor secret changes in Kubernetes?
If you just need to restart pods, https://github.com/stakater/Reloader might be a good option. Anything more advanced will likely require a component that integrates with the Kube API.
-
How should I manage my Helm charts?
E.g. on a cloud provider use their secrets management solution. Bring the secrets from git/sops into their store, then for the application use external-secrets to bring a copy into your namespace and update your deployments with reloader.
-
Sharing/syncing secrets across clusters
on top of that combine https://github.com/stakater/Reloader into the mix to bounce pods around when it detects a cm or secret that gets updated from upstream
- Trigger redeployment after configmap change?
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
kubernetes-reflector - Custom Kubernetes controller that can be used to replicate secrets, configmaps and certificates.
vault-secrets-operator - Create Kubernetes secrets from Vault for a secure GitOps based workflow.
sops - Simple and flexible tool for managing secrets
argocd-operator - A Kubernetes operator for managing Argo CD clusters.
k8s-configmap-watcher
argo-rollouts - Progressive Delivery for Kubernetes
helm-charts - Misc helm charts
flux2 - Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.
hull - The incredible HULL - Helm Uniform Layer Library - is a Helm library chart to improve Helm chart based workflows
secrets-store-csi-driver-provider-gcp - Google Secret Manager provider for the Secret Store CSI Driver.