kustomize-sops
argocd-vault-plugin
| kustomize-sops | argocd-vault-plugin | |
|---|---|---|
| 8 | 9 | |
| 601 | 761 | |
| 1.8% | 1.3% | |
| 6.8 | 7.3 | |
| 19 days ago | 13 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
argocd-vault-plugin
-
GitOps and Kubernetes – Secure Handling of Secrets
ArgoCD supports SOPS with the vault Plugin.
-
Injecting secrets from Vault into Helm charts with ArgoCD
repoServer: rbac: - verbs: - get - list - watch apiGroups: - '' resources: - secrets - configmaps initContainers: - name: download-tools image: registry.access.redhat.com/ubi8 env: - name: AVP_VERSION value: 1.11.0 command: [sh, -c] args: - >- curl -L https://github.com/argoproj-labs/argocd-vault-plugin/releases/download/v$(AVP_VERSION)/argocd-vault-plugin_$(AVP_VERSION)_linux_amd64 -o argocd-vault-plugin && chmod +x argocd-vault-plugin && mv argocd-vault-plugin /custom-tools/ volumeMounts: - mountPath: /custom-tools name: custom-tools extraContainers: - name: avp-helm command: [/var/run/argocd/argocd-cmp-server] image: quay.io/argoproj/argocd:v2.4.8 securityContext: runAsNonRoot: true runAsUser: 999 volumeMounts: - mountPath: /var/run/argocd name: var-files - mountPath: /home/argocd/cmp-server/plugins name: plugins - mountPath: /tmp name: tmp-dir - mountPath: /home/argocd/cmp-server/config name: cmp-plugin - name: custom-tools subPath: argocd-vault-plugin mountPath: /usr/local/bin/argocd-vault-plugin volumes: - configMap: name: cmp-plugin name: cmp-plugin - name: custom-tools emptyDir: {} - name: tmp-dir emptyDir: {} # If you face issue with ArgoCD CRDs installation, then uncomment below section to disable it #crds: # install: false
- K8s and HIPPA/PHI compliant systems - Need advice!
-
Learning with K3s at home. Is it "better" to store secrets encrypted in the git repo (e.g., sealed-secrets) or in a separately managed secret database (e.g., vault)?
argoproj-labs/argocd-vault-plugin
-
Best solution to use Argocd with helm and manage secrets ? Don't say flux !
We’re using https://github.com/argoproj-labs/argocd-vault-plugin which allows you to define secrets in git (works with more backends than just hashicorp vault despite the name). The documentation took me a bit to figure out, but so far it works.
-
Best Practices for Argo CD
Argo CD Vault plugin
- Removing replication count, resource, tolerations, pvc when app is onboarded using ArgoCD
- Gotta love gitops
-
Best/Secure way to add a secret for ArgoCD Helm Chart?
I used argocd vault plugin https://github.com/IBM/argocd-vault-plugin
What are some alternatives?
sealed-secrets - A Kubernetes controller and tool for one-way encrypted Secrets
kubernetes-external-secrets - Integrate external secret management systems with Kubernetes
flux2 - Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.
vault-secrets-operator - Create Kubernetes secrets from Vault for a secure GitOps based workflow.
helm-secrets - A helm plugin that help manage secrets with Git workflow and store them anywhere
sops-secrets-operator - Kubernetes SOPS secrets operator
secrets-store-csi-driver - Secrets Store CSI driver for Kubernetes secrets - Integrates secrets stores with Kubernetes via a CSI volume.
etcd - Distributed reliable key-value store for the most critical data of a distributed system
vault-creds - Sidecar container for requesting dynamic Vault database secrets
argocd-image-updater - Automatic container image update for Argo CD