argocd-vault-plugin
argocd-image-updater
Our great sponsors
argocd-vault-plugin | argocd-image-updater | |
---|---|---|
9 | 21 | |
757 | 1,104 | |
2.2% | 4.8% | |
7.1 | 6.3 | |
4 days ago | 6 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.
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
argocd-image-updater
- Helm or Kustomize for my situation?
-
How do you produce your images for argcd deployment
Use the ArgoCD image updater
-
What tool are you using to edit yaml graphically?
We already have software agents in GitOps ecosystem that modify the state in git. Ie, the image updater in ArgoCD. It watches the docker registry. When it sees a new image, it updates git on a user's behalf.
-
Is there a CD solution that can be (painlessly) fully automated between stages?
If you are using ArgoCD you might be able to use this: https://argocd-image-updater.readthedocs.io/en/stable/
-
How to keep track of 3d party applications helm chart on K8S?
I just found this in my travels, I have only gone so far as reading the introduction but seems to be a fit? https://github.com/argoproj-labs/argocd-image-updater
-
Is it possible that k8s updates image version on pod relaunch?
I've used Keel and more recently ArgoCD Image Updater (Using ArgoCD to manage deployments).
-
What do you use to update image tags?
https://argocd-image-updater.readthedocs.io/en/stable/ maybe?
-
Quite happy with my first 6 hour journey with ArgoCD
Use the image updater
-
How do you handle change management for a self-hosted CI/CD solution?
To answer your question you should promote docker images between environments. There are many ways to do this. Check https://argocd-image-updater.readthedocs.io/en/stable/ if you haven't seen it already.
-
What are you using for the CI part of GitOps?
For ArgoCD there’s argocd-image-updated, https://argocd-image-updater.readthedocs.io/en/stable/
What are some alternatives?
kubernetes-external-secrets - Integrate external secret management systems with Kubernetes
keel - Kubernetes Operator to automate Helm, DaemonSet, StatefulSet & Deployment updates
kustomize-sops - KSOPS - A Flexible Kustomize Plugin for SOPS Encrypted Resources
Pulumi - Pulumi - Infrastructure as Code in any programming language. Build infrastructure intuitively on any cloud using familiar languages 🚀
vault-secrets-operator - Create Kubernetes secrets from Vault for a secure GitOps based workflow.
helmfile - Deploy Kubernetes Helm Charts
sealed-secrets - A Kubernetes controller and tool for one-way encrypted Secrets
updatecli - A Declarative Dependency Management tool
secrets-store-csi-driver - Secrets Store CSI driver for Kubernetes secrets - Integrates secrets stores with Kubernetes via a CSI volume.
trivy - Find vulnerabilities, misconfigurations, secrets, SBOM in containers, Kubernetes, code repositories, clouds and more
vault-creds - Sidecar container for requesting dynamic Vault database secrets
applicationset - The ApplicationSet controller manages multiple Argo CD Applications as a single ApplicationSet unit, supporting deployments to large numbers of clusters, deployments of large monorepos, and enabling secure Application self-service.