argo-rollouts
fleet
argo-rollouts | fleet | |
---|---|---|
9 | 3 | |
2,499 | 1,449 | |
2.1% | 1.0% | |
9.5 | 9.8 | |
about 17 hours ago | 3 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.
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.
fleet
-
How to do multiple deployments with fleet within the same cluster but with different values & namespace?
Basically I'm looking for a workaround to this issue: https://github.com/rancher/fleet/issues/344.
-
Automation assistants: GitOps tools in comparison
A newer competitor is Fleet, which is developed by Rancher. Its special ability is that it is able to manage not just one, but a fleet of clusters. PipeCD is similarly young and has an even broader focus. Like Fleet, it promises the ability to manage multiple Kubernetes clusters, and it also offers a UI. In addition, it can handle Terraform and some services from the major cloud providers.
- Best way to manage kubernetes deployments/manifests?
What are some alternatives?
flagger - Progressive delivery Kubernetes operator (Canary, A/B Testing and Blue/Green deployments)
argocd-operator - A Kubernetes operator for managing Argo CD clusters.
Flux - Successor: https://github.com/fluxcd/flux2
argo-cd - Declarative Continuous Deployment for Kubernetes
terraform-k8s - Terraform Cloud Operator for Kubernetes
flux2 - Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.
sops-secrets-operator - Kubernetes SOPS secrets operator
werf - A solution for implementing efficient and consistent software delivery to Kubernetes facilitating best practices.
helm-secrets - A helm plugin that help manage secrets with Git workflow and store them anywhere
cluster-api - Home for Cluster API, a subproject of sig-cluster-lifecycle