jx VS flagger

Check out the https://jenkins-x.io/ project

Jenkins X (https://jenkins-x.io/) - standup k8s w gitops ci/cd around jenkins

Like: * Drone.io * GoCD * Github Actions * Gitlab CI * Circle CI * JenkinsX (not the same as old jenkins - it is from built from the ground up on kube with tekton)

You may want to checkout Jenkins X, it using Tekton underneath

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.

Argo has served us well, but our devops architect is currently building out a new ci/cd pipeline to replace Argo with Jenkins X. https://jenkins-x.io/

Jenkins

Flagger

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.

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.

flagger: Automated canary using istio/linkerd

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 :)

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.

Check https://argoproj.github.io/argo-rollouts/ and https://flagger.app/