kustomize-sops
secrets-store-csi-driver
| kustomize-sops | secrets-store-csi-driver | |
|---|---|---|
| 8 | 22 | |
| 600 | 1,174 | |
| 1.7% | 0.8% | |
| 6.8 | 8.5 | |
| 13 days ago | 7 days ago | |
| Go | Go | |
| 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.
kustomize-sops
-
Ask HN: Who's an open source maintainer/project that needs sponsorship or help?
I maintain several open source projects, most notably:
Sparkmagic (https://github.com/jupyter-incubator/sparkmagic)
Sparkmagic provides jupyter magics and kernels for working with remote Spark clusters. It's used by thousands of developers and companies like Pinterest, Amazon, more!
I've been maintaining for the past few years and would love help!
KSOPS (https://github.com/viaduct-ai/kustomize-sops)
KSOPS, or kustomize-SOPS, is a kustomize KRM exec plugin for SOPS encrypted resources. KSOPS can be used to decrypt any Kubernetes resource, but is most commonly used to decrypt encrypted Kubernetes Secrets and ConfigMaps. As a kustomize plugin, KSOPS allows you to manage, build, and apply encrypted manifests the same way you manage the rest of your Kubernetes manifests.
KSOPS is the most popular kustomize plugin and I'd love help maintaining and improving it from out GitOps fanatics.
- KSOPS v4 Supports KRM Exec Functions
-
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.
- Show HN: A Flexible Kustomize Plugin for SOPS Encrypted Resource
- ArgoCD vs. FluxCD and how they handle Secrets
-
5 Ways to Access Kubernetes Clusters
The common wisdom is to use something that reconciles in cluster (e.g. a CSI driver as recommended in AKS, or sealed secrets, or vault injector) or a kustomize plugin (like ksops, advantage of just rendering out standard secrets in the cluster itself)
-
Gotta love gitops
We've considered this, but then went with argocd + ksops for the key agility.
-
10 Anti-patterns for Kubernetes Deployment !!
Check out ksops from viaduct https://github.com/viaduct-ai/kustomize-sops
secrets-store-csi-driver
-
Check your secrets into Git [video]
I'm not a fan of this approach. I think the Secrets Store CSI Driver (https://secrets-store-csi-driver.sigs.k8s.io/) has a better approach.
-
EKS secrets - Bitnami sealed secrets or KMS?
Secret Store CSI Driver is what we're playing with now. Pretty excellent.
-
How does your company do secret management? AWS/GCP/Azure/Vault/CyberArk etc. thoughts?
If you deploy on k8s, keep your eye on https://secrets-store-csi-driver.sigs.k8s.io/
- K8s secret management
-
Secret Management in Kubernetes: Approaches, Tools, and Best Practices
Considering the major limitations of using Kubernetes Secrets, there are many new approaches being developed by the Kubernetes community. Kubernetes SIGs like the Secrets Store CSI Driver and solutions like the external secrets operator that works with third-party secret managers, and options to seal secrets through tools like bitnami’s sealed-secrets. To skip the tools and move directly to best practices, click here.
-
Azure AKS/Container App can't access Key vault using managed identity
Just to clarify, CSI secret driver is from cncf not Microsoft. Only msft piece is the portion that integrates with key vault. https://secrets-store-csi-driver.sigs.k8s.io/
-
Vault Secrets in K8S, use CRD Injector ?
https://secrets-store-csi-driver.sigs.k8s.io/ and https://developer.hashicorp.com/vault/tutorials/kubernetes/kubernetes-secret-store-driver
-
Shhhh... Kubernetes Secrets Are Not Really Secret!
The Secrets Store CSI Driver is a native upstream Kubernetes driver that can be used to abstract where the secret is stored from the workload. If you want to use a cloud provider's secret manager without exposing the secrets as Kubernetes Secret objects, you can use the CSI Driver to mount secrets as volumes in your pods. This is a great option if you use a cloud provider to host your Kubernetes cluster. The driver supports many cloud providers and can be used with different secret managers.
-
SealedSecrets or external secret operator?
If you want security they are both bad, use something like the secret manager of your choice API directly in your app or https://secrets-store-csi-driver.sigs.k8s.io/ this will keep the actual secrets out of etcd and env vars and give you more security
- Secrets Management on Kubernetes: How do you handle it?
What are some alternatives?
argocd-vault-plugin - An Argo CD plugin to retrieve secrets from Secret Management tools and inject them into Kubernetes secrets
kubernetes-external-secrets - Integrate external secret management systems with Kubernetes
sealed-secrets - A Kubernetes controller and tool for one-way encrypted Secrets
flux2 - Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.
secrets-store-csi-driver-provider-gcp - Google Secret Manager provider for the Secret Store CSI Driver.
helm-secrets - A helm plugin that help manage secrets with Git workflow and store them anywhere
external-secrets - External Secrets Operator reads information from a third-party service like AWS Secrets Manager and automatically injects the values as Kubernetes Secrets.
sops-secrets-operator - Kubernetes SOPS secrets operator
ingress-nginx - Ingress-NGINX Controller for Kubernetes
etcd - Distributed reliable key-value store for the most critical data of a distributed system