TiloBox
Back to directory
Flagger project preview

Flagger

Progressive delivery Kubernetes operator for Canary, A/B Testing, and Blue/Green deployments.

LicenseApache-2.0
GitHub stars5.2k
Last commit1 weeks ago
Tags6 topics
Istio TrafficProgressive DeliveryDevops InfrastructureKubernetes OperatorCanary DeploymentsGolang
Overview

Why consider Flagger?

Flagger is a CNCF progressive delivery Kubernetes operator by the Flux project. It automates Canary releases, A/B testing, and Blue/Green deployments using service meshes (Istio, Linkerd) and metrics providers (Prometheus, Datadog).

Guided learning

Learn Flagger by building

Practical setup notes, real use cases, and copy-ready examples in one focused guide.

1 min read 2 sections
In this guide2 sections

Overview of Flagger

Flagger analyzes real-time HTTP success rates and latency percentiles during deployments, rolling back failed pods automatically.

Installation via Helm

bash
1helm repo add flagger https://flagger.app
2helm install flagger flagger/flagger --namespace=flagger-system

Flagger is licensed under the Apache License Version 2.0.

Related tools

More options with a similar category or technology profile.

Flagger FAQs

Flagger is listed as a Developer Tools tool on TiloBox. Review the overview, features, and official documentation on this page to decide whether it solves your specific workflow.

Start with the project's GitHub repository and official website for supported installation and deployment instructions. Test the setup with representative data or a small project before rolling it out more widely.

Flagger is listed under the Apache-2.0 license. Read the complete license text and the project's notices before using, modifying, or distributing the software.

Production readiness depends on your requirements. Review maintenance activity, security practices, documentation, backup and upgrade procedures, and compatibility with your stack; then validate it in a non-production environment.

Flagger is listed as an alternative to Argo Rollouts. Compare the core workflow, deployment model, integrations, and licensing against your must-have requirements before switching.