helm-monitor
argo-rollouts
helm-monitor | argo-rollouts | |
---|---|---|
1 | 9 | |
404 | 2,507 | |
0.0% | 3.0% | |
0.0 | 9.5 | |
8 months ago | 1 day 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.
helm-monitor
-
how do you auto deploy to kubernetes with auto rollbacks?
Example2: performance is bad or errors rate is up. Need auto rollback 1. Need to be rolledback because 500 erorrs are coming. 2. Solutions may varied from a cronjob that polls the monitoring system to compare and detect 500 errors after it reaches a threshold then apply a command like kubectl deployment undo (check https://github.com/ContainerSolutions/helm-monitor) an fully functional AB rolling release system like argocd or weaveworks flagger ....
argo-rollouts
-
Gateway API is now in Beta; new project formed for service mesh APIs
And support is on it's way for Argo Rollouts 🎉 https://github.com/argoproj/argo-rollouts/pull/2004
-
Progressive Delivery with Argo Rollouts : Blue-Green Deployment
curl -LO https://github.com/argoproj/argo-rollouts/releases/latest/download/kubectl-argo-rollouts-linux-amd64 chmod +x ./kubectl-argo-rollouts-linux-amd64 sudo mv ./kubectl-argo-rollouts-linux-amd64 /usr/local/bin/kubectl-argo-rollouts kubectl argo rollouts version
-
Progressive Delivery with Argo Rollouts: Canary Deployment
kubectl create namespace argo-rollouts kubectl apply -n argo-rollouts -f https://github.com/argoproj/argo-rollouts/releases/latest/download/install.yaml
-
how do you auto deploy to kubernetes with auto rollbacks?
You can see in why argo section here what are the limitations of rolling updates and how rollouts solves it: https://github.com/argoproj/argo-rollouts
-
Best Practices for Argo CD
Argo Rollouts
-
Canary deployments
Check the public users list https://github.com/argoproj/argo-rollouts/blob/master/USERS.md
-
argo-rollouts VS flagger - a user suggested alternative
2 projects | 25 Jan 2022
- argoproj/argo-rollouts: Progressive Delivery for Kubernetes
-
Automation assistants: GitOps tools in comparison
Supplementary GitOps operators can also be used for deployment strategies, such as canary releases, A/B tests, and blue/green deployments, which have now been grouped under the term “progressive delivery”. The resources of most GitOps operators are not sufficient for this. One solution is Flagger. The tool that was launched by Weaveworks is now being developed as part of the Flux project. The Argo project also has an operator for this use case: Argo Rollouts. Both offer CRs for implementing progressive delivery strategies in interaction with various ingress controllers and service meshes.
What are some alternatives?
helm-gcs - Manage Helm 3 repositories on Google Cloud Storage 🔐 **privately**
flagger - Progressive delivery Kubernetes operator (Canary, A/B Testing and Blue/Green deployments)
helm-push - Helm plugin to push chart package to ChartMuseum
Flux - Successor: https://github.com/fluxcd/flux2
helm-teller - Allows you to manage configuration and secrets from multiple provider while masking the secrets at the deployment
fleet - Deploy workloads from Git to large fleets of Kubernetes clusters
terraform-k8s - Terraform Cloud Operator for Kubernetes
flux2 - Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.
argo-cd - Declarative Continuous Deployment for Kubernetes
helm-secrets - A helm plugin that help manage secrets with Git workflow and store them anywhere
kubernetes-external-secrets - Integrate external secret management systems with Kubernetes
terraform-controller - Use K8s to Run Terraform