flagger
Progressive delivery Kubernetes operator (Canary, A/B Testing and Blue/Green deployments) (by fluxcd)
werf
A solution for implementing efficient and consistent software delivery to Kubernetes facilitating best practices. (by werf)
flagger | werf | |
---|---|---|
14 | 15 | |
4,735 | 3,912 | |
0.7% | 0.6% | |
8.7 | 9.8 | |
8 days ago | 6 days ago | |
Go | Go | |
Apache License 2.0 | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
flagger
Posts with mentions or reviews of flagger.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-09-26.
- A K8s progressive delivery tool
-
Progressive Delivery on AKS: A Step-by-Step Guide using Flagger with Istio and FluxCD
Flagger
-
API release strategies with API Gateway
Where appropriate, canary releases are an excellent option, as the percentage of traffic exposed to the canary is highly controlled. The trade-off is that the system must have good monitoring in place to be able to quickly identify an issue and roll back if necessary (which can be automated). This guide shows you how to use Apache APISIX and Flagger to quickly implement a canary release solution.
-
GitOps using Flux and Flagger
What is Flagger? Flagger is a Progressive Delivery tool that automates the release process for applications running on Kubernetes. Under the hood, both tools are built on top of a modular GitOps toolkit. It is the main reason why Flagger compliments Flux.
- RollingUpdate but with testing the new pods first for a few minutes
-
Interesting tools?
flagger: Automated canary using istio/linkerd
-
How to rebalance underutilized nodes with CA without single replica Pod downtime?
I would suggest trying a-b deployment in this case using flagger. It will spin up a new instance and gradually rotate out old ones. Maybe that can be helpful in this weird situation :)
-
argo-rollouts VS flagger - a user suggested alternative
2 projects | 25 Jan 2022
ArgoRollouts offers Canary and BlueGreen deployment strategies for Kubernetes Pods. It's a drop-in replacement for the v1.Deployment object. Flagger is similar what it offers, extending Kubernetes to support Canary and BlueGreen deployment strategies.
-
How do you implement blue/green deployments ?
Check https://argoproj.github.io/argo-rollouts/ and https://flagger.app/
- ISO kubernetes tool or operator that automatically rolls over to a backup repo on failures
werf
Posts with mentions or reviews of werf.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-09-08.
-
Is there a CD solution that can be (painlessly) fully automated between stages?
I am looking as well for this kind of tool. I just took a look today by exploring the CNCF landscape this tool : https://werf.io/ , I haven't used it, but it seems to take care of painful stuff like automatic versioning for example. (If someone here tried it, I will be happy to listen to your feedbacks)
-
Phabricator replacement? | Or OpenProject alternative? | issue tracking/code
Werf - um ok
-
Top 200 Kubernetes Tools for DevOps Engineer Like You
HybridK8s Droid - Intelligence foor your favourite Delivery Platform Devtron - Software Delivery Workflow for Kubernetes Skaffold - Easy and Repeatable Kubernetes Development Apollo - Apollo - The logz.io continuous deployment solution over kubernetes Helm Cabin - Web UI that visualizes Helm releases in a Kubernetes cluster flagger - Progressive delivery Kubernetes operator (Canary, A/B Testing and Blue/Green deployments) Kubeform - Kubernetes CRDs for Terraform providers https://kubeform.com Spinnaker - Spinnaker is an open source, multi-cloud continuous delivery platform for releasing software changes with high velocity and confidence. http://www.spinnaker.io/ werf - GitOps tool to deliver apps to Kubernetes and integrate this process with GitLab and other CI tools Flux - GitOps Kubernetes operator Argo CD - Declarative continuous deployment for Kubernetes Tekton - A cloud native continuous integration and delivery (CI/CD) solution Jenkins X - Jenkins X provides automated CI+CD for Kubernetes with Preview Environments on Pull Requests using Tekton, Knative, Lighthouse, Skaffold and Helm KubeVela - KubeVela works as an application delivery control plane that is fully decoupled from runtime infrastructure ksonnet - A CLI-supported framework that streamlines writing and deployment of Kubernetes configurations to multiple clusters CircleCI - A cloud-based tool that helps build continuous integration and continuous delivery pipelines to Kubernetes.
-
Deployment Watching Tool
Check out https://werf.io/ tool. It features giterminism which is somewhat similar to gitops, but it does not require pull model. Giterminism aims to improve reproducibility of your build and deploy configuration. werf also features content-based-tagging out of the box, which allows creating immutable images, stored in the container-registry, shared between multiple runners (werf uses distributed locking to prevent overriding image which is already published). Giterminism and content-based-tagging enables easy rollbacks to any git-commit in the history of your project. By design werf could be embedded into any ci/cd system.
-
werf is a CLI tool for implementing CI/CD with Kubernetes; its v1.2 became stable
Rename of dapp to werf was in Jan'19 to be precise (https://github.com/werf/werf/pull/1213).
- Werf
-
11 Open Source Kubernetes Ci Cd Tools To Improve Your Devops
Werf
-
Alternative to helmfile that works well with Github Actions
You can try werf, it has Helm under the hood and there are github actions available for it: https://github.com/werf/actions
-
werf as [yet another] way to build Docker images
As you know, there's plenty of tools that can be used to build your Docker images, besides the docker build itself. werf is an Open Source project with a long history (started in 2016 as a simple wrapper around Docker CLI). Still being a CLI tool, today it is focused not just on the building but also delivering these images to Kubernetes — and this is what makes it really different.
- Podman: A tool for managing OCI containers and pods
What are some alternatives?
When comparing flagger and werf you can also consider the following projects:
argo-rollouts - Progressive Delivery for Kubernetes
argo-cd - Declarative Continuous Deployment for Kubernetes
flux2 - Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.
spinnaker - Spinnaker is an open source, multi-cloud continuous delivery platform for releasing software changes with high velocity and confidence.
terraform-controller - Use K8s to Run Terraform
Flux - Successor: https://github.com/fluxcd/flux2
kaniko - Build Container Images In Kubernetes
terraform-k8s - Terraform Cloud Operator for Kubernetes
Fabric - Simple, Pythonic remote execution and deployment.
fleet - Deploy workloads from Git to large fleets of Kubernetes clusters