reliza-cli
argocd-image-updater
Our great sponsors
reliza-cli | argocd-image-updater | |
---|---|---|
10 | 21 | |
4 | 1,110 | |
- | 5.3% | |
7.1 | 6.3 | |
8 days ago | 12 days ago | |
Go | Go | |
MIT License | 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.
reliza-cli
- Track all software deployments across all instances at any point in time with Reliza Hub
- Reliza Hub manages bundles of microservices - especially when you feel you have too many. Know what is and should be deployed on every instance at any time.
- Reliza Hub - Take Control Of All Your Software Changes
- Reliza Hub - Revolutionary Platform to Manage All Your Software Releases
-
How are you measuring DevOps performance?
We currently provide accurate lead time and deployment frequency calculation capability via Reliza Hub - https://relizahub.com (operating in public preview). Since we track when each piece of code gets deployed to each environment and each instance. Other metrics are on our roadmap.
-
Best Practices for managing parent docker images used by several services
You then either leverage getlatestrelease functionality of reliza-cli - https://github.com/relizaio/reliza-cli#6-use-case-request-latest-release-per-project-or-product to request approved image or you can use replacetags functionality over your Dockerfile which would replace base image with the one approved - https://github.com/relizaio/reliza-cli#74-use-case-replace-tags-on-deployment-templates-to-inject-correct-artifacts-for-gitops-using-environment
- Ask HN: How do you keep track of releases/deployments of dozens micro-services?
-
How do you manage multiple environments with GitOps?
Note, we have recently released a new replacetags functionality (https://github.com/relizaio/reliza-cli#74-use-case-replace-tags-on-deployment-templates-to-inject-correct-artifacts-for-gitops-using-environment - going to add tutorial soon) so that you don't need to use templating language inside your helm charts or manifests and instead it would just parse raw base yamls into correct images per each environment.
-
Service Config Management tools
We're building Reliza Hub for this purpose - https://relizahub.com
-
Full CI/CD pipeline delivered via ArgoCD
Note, it's somewhat outdated and we're working on a new one based on new replacetags functionality - https://github.com/relizaio/reliza-cli#72-use-case-replace-tags-on-deployment-templates-to-inject-correct-artifacts-for-gitops-using-instance-and-revision
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?
flux2-kustomize-helm-example - A GitOps workflow example for multi-env deployments with Flux, Kustomize and Helm.
keel - Kubernetes Operator to automate Helm, DaemonSet, StatefulSet & Deployment updates
DevOpsMetrics - A project to extract and process high performing DevOps metrics (DORA) from GitHub and Azure DevOps
Pulumi - Pulumi - Infrastructure as Code in any programming language. Build infrastructure intuitively on any cloud using familiar languages 🚀
backstage - Backstage is an open platform for building developer portals
helmfile - Deploy Kubernetes Helm Charts
flux2-multi-tenancy - Manage multi-tenant clusters with Flux
updatecli - A Declarative Dependency Management tool
zim - A caching build system for teams using monorepos
trivy - Find vulnerabilities, misconfigurations, secrets, SBOM in containers, Kubernetes, code repositories, clouds and more
shipit-engine - Deployment coordination
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.