berglas
helm-secrets
berglas | helm-secrets | |
---|---|---|
37 | 12 | |
1,224 | 1,316 | |
0.1% | - | |
6.9 | 8.3 | |
6 days ago | 13 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.
berglas
-
How to deploy a Django app to Google Cloud Run using Terraform
Secret Manager: secure storage for sensitive data e.g passwords.
- How do you handle sensitive variables with a service-worker?
-
Increasing Your Cloud Function Development Velocity Using Dynamically Loading Python Classes
Google Secret Manager
-
Getting started using Google APIs: API Keys (Part 2)
API keys are easy to "leak" or compromise, so best to not only use the restrictions presented to you when you create them but physically protect them as well. Don't code them in plain-text, don't check them into GitHub, etc. Store them in a secure database or use a service like GCP Secret Manager.
-
Need some advice on API key storage
I've been looking at Google Secret Manager which sounds promising but I've not been able to find any examples or tutorials that help with the actual practical details of best practice or getting this working. I'm currently reading about Cloud Functions which also sound promising but again, I'm just going deeper and deeper into GCP without feeling like I'm gaining any useful insights.
-
Secure GitHub Actions by pull_request_target
In this post, I described how to build secure GitHub Actions workflows by pull_request_target event instead of pull_request event. Using pull_request_target, you can prevent malicious codes from being executed in CI. And by managing secrets in secrets management services such as AWS Secrets Manager and Google Secret Manager and access them via OIDC, you can restrict the access to secrets securely. To migrate pull_request to pull_request_target, several modifications are needed. And pull_request_target has a drawback that it's difficult to test changes of workflows, so it's good to introduce pull_request_target to repositories that require strong permissions in CI. For example, a Terraform Monorepo tends to require strong permissions for CI, so it's good to introduce pull_request_target to it.
-
Need Help with Deploying Directus on Google Cloud Platform (GCP)
If you want to make these secrets more secure and get versioning and access logs for them, you may want to switch to Secret Manager later on. They can still be exposed as environment variables to your code. It's a little more setup work, so start with the simple approach at the top.
-
Has anyone been able to implement the OpenAI API with a Firebase Function (which is needed for the env variable API Key)?
https://cloud.google.com/secret-manager https://aws.amazon.com/secrets-manager/
- Securely storing Social Security Numbers with Firebase?
- Dónde van las credenciales cuando voy a subir un código a la nube para correr 24/7?
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
helm-charts
vault-secrets-operator - Create Kubernetes secrets from Vault for a secure GitOps based workflow.
kube-secrets-init - Kubernetes mutating webhook for `secrets-init` injection
sops - Simple and flexible tool for managing secrets
gitleaks - Protect and discover secrets using Gitleaks 🔑
argocd-operator - A Kubernetes operator for managing Argo CD clusters.
cocert - Split and distribute your private keys securely amongst untrusted network
argo-rollouts - Progressive Delivery for Kubernetes
secrets-store-csi-driver-provider-gcp - Google Secret Manager provider for the Secret Store CSI Driver.
hull - The incredible HULL - Helm Uniform Layer Library - is a Helm library chart to improve Helm chart based workflows