Hypertune
Type-safe feature flags platform with A/B testing, analytics, and app configuration optimized for TypeScript
Open-Source Projects
Discover top open-source software, updated regularly with real-world adoption signals.
Discover top open-source software, updated regularly with real-world adoption signals.
Progressive delivery automation for Kubernetes with canary deployments
Flagger automates progressive delivery on Kubernetes by gradually shifting traffic to new versions while measuring metrics, running tests, and supporting canary, A/B, and blue/green strategies.
Flagger is a Cloud Native Computing Foundation progressive delivery tool that reduces production risk by automating the release process for Kubernetes applications. Instead of deploying new versions all at once, Flagger gradually shifts traffic while continuously measuring application metrics and running conformance tests.
Flagger supports canary releases, A/B testing, blue/green deployments, and traffic mirroring. It integrates with major service meshes (Istio, Linkerd, App Mesh, Kuma, OSM), ingress controllers (NGINX, Contour, Traefik, Gloo), and monitoring solutions. The tool tracks ConfigMaps and Secrets, automatically triggering analysis when configuration or code changes.
As part of the Flux family of GitOps tools, Flagger uses a declarative Canary custom resource to define deployment strategies, metric thresholds, webhooks for testing, and alerting rules. It creates and manages Kubernetes deployments, services, and routing objects automatically, synchronizing both container images and configuration during promotions. Teams can set traffic increment steps, success rate thresholds, latency limits, and custom metrics to ensure safe, automated rollouts.
When teams consider Flagger, these hosted platforms usually appear on the same shortlist.
Looking for a hosted option? These are the services engineering teams benchmark against before choosing open source.
Canary Deployment with Automated Rollback
Gradually shift 5% traffic increments to a new version, automatically rolling back if request success rate drops below 99% or latency exceeds thresholds
A/B Testing with Header-Based Routing
Route users with specific headers or cookies to a new application version for controlled feature testing before full rollout
Blue/Green Deployment with Load Testing
Deploy a new version alongside the current one, run automated load tests via webhooks, then switch traffic instantly upon success
Configuration Change Validation
Automatically trigger canary analysis when ConfigMaps or Secrets change, ensuring configuration updates are validated with the same rigor as code
Flagger requires a Kubernetes cluster and optionally integrates with service meshes (Istio, Linkerd, App Mesh, Kuma, OSM), ingress controllers (NGINX, Contour, Traefik, Gloo), or the Gateway API. Monitoring with Prometheus is recommended for metrics analysis.
Flagger measures metrics like request success rate and latency at defined intervals during traffic shifting. If metrics exceed thresholds for a configured number of checks, it rolls back automatically. Webhooks can run conformance or load tests to further validate deployments.
Yes. Flagger tracks ConfigMaps and Secrets referenced by deployments and triggers canary analysis when they change, synchronizing both container images and configuration during promotion.
Flagger supports canary releases (weighted traffic shifting), A/B testing (header/cookie-based routing), blue/green deployments (traffic switch), and traffic mirroring. Strategy availability depends on the service mesh or ingress provider.
Yes. Flagger is a Cloud Native Computing Foundation project and part of the Flux family of GitOps tools, designed to integrate with declarative, Git-driven Kubernetes workflows.
Project at a glance
ActiveLast synced 4 days ago
