awesome-repositories.com
Blog
awesome-repositories.com

Entdecke die besten Open-Source-Repositories mit KI-gestützter Suche.

EntdeckenKuratierte SuchenOpen-Source-AlternativenSelf-hosted SoftwareBlogSitemap
ProjektÜber unsRanking-MethodikPresseMCP-Server
RechtlichesDatenschutzAGB
© 2026 Bringes Technology SRL·VAT RO45896025·hello@awesome-repositories.com
·
weaveworks avatar

weaveworks/flagger

0
View on GitHub↗
5,362 Stars·799 Forks·Go·Apache-2.0·8 Aufrufedocs.flagger.app/main↗

Flagger

Flagger is a Kubernetes operator designed to automate the lifecycle of application deployments through progressive delivery. It functions as a controller that monitors custom resource definitions to orchestrate complex release strategies, including canary, blue/green, and A/B testing. By continuously reconciling the desired cluster state with the actual environment, it ensures that deployments adhere to defined specifications while managing the underlying infrastructure required for traffic routing.

The project distinguishes itself through a sophisticated metric-driven analysis loop that evaluates real-time telemetry from external monitoring providers against predefined thresholds. This allows for automated promotion or rollback of releases based on actual performance data. Furthermore, it features extensive external webhook orchestration, enabling the integration of custom validation, load testing, and manual approval gating at specific deployment phases. This capability allows users to harden their release process by executing end-to-end tests or synthetic traffic generation before shifting production traffic.

Beyond its core analysis and traffic shifting capabilities, the project provides a comprehensive suite of operational tools for managing application lifecycles. This includes support for session affinity, header-based routing, and protocol-specific traffic management for non-HTTP services. It also integrates with notification systems to provide visibility into deployment events and status changes, ensuring teams remain informed throughout the automated release process.

The controller is designed to integrate into GitOps pipelines, allowing for declarative management of delivery workflows. It can be installed and managed directly on a cluster, with documentation and tooling available to support local development and testing of deployment configurations.

Features

  • Canary Deployment Controllers - Shifts traffic to new application versions incrementally while monitoring performance metrics and health for automated promotion or rollback.
  • Canary Release Managers - Performs canary releases by gradually shifting traffic while monitoring performance metrics to automate promotion or rollback.
  • Progressive Delivery Strategies - Shifts traffic to new application versions incrementally while monitoring performance metrics and health, automatically promoting or rolling back based on analysis.
  • Progressive Delivery Operators - Automates canary, blue/green, and A/B testing deployments by shifting traffic incrementally while monitoring health metrics.
  • Rollout Health Monitoring - Tracks HTTP success rates and latency during rollouts to automatically halt and revert changes if performance degrades.
  • Traffic-Based - Routes traffic to specific software versions based on HTTP match conditions to target user segments for experimentation.
  • Progressive Release Automators - Automates the incremental shifting of traffic between application versions to reduce production risk.
  • Blue-Green Deployments - Orchestrates blue/green deployments by switching traffic between identical environments using networking or service mesh.
  • Cluster State Reconciliation - Continuously aligns the actual state of a cluster with a desired configuration.
  • Custom Resource Controllers - Uses Kubernetes custom resource controllers to automate application lifecycle management and traffic routing configurations.
  • Deployment Automation - Supports canary releases, A/B testing, blue/green deployments, and traffic shadowing to manage production application introductions.
  • Metrics-Aware Rollbacks - Evaluates real-time telemetry against thresholds to automatically trigger rollbacks to the stable version.
  • Automated Rollout Managers - Manages application updates through incremental rollout procedures and automated rollback capabilities based on metric analysis.
  • Deployment Rollbacks - Reverts traffic to the stable version immediately when health checks or performance thresholds fail during a deployment.
  • Automated Canary Analysis - Evaluates real-time metrics against defined thresholds to automatically determine if a new release should be promoted or rolled back.
  • Automated Guardrail Rollbacks - Monitors real-time metrics during a rollout and automatically reverts traffic to the stable version if thresholds are breached.
  • Automated Metric Analysis - Integrates external monitoring queries to enforce performance or error rate requirements for new deployments.
  • GitOps Workflows - Reacts to cluster events and declarative configuration to automate delivery within continuous deployment workflows.
  • Automated Release Validation - Hardens the deployment process by executing custom metrics analysis, acceptance tests, and load tests during traffic shifting.
  • Rolling - Automatically rolls back failed deployments by reverting traffic to the stable version and scaling down canary instances.
  • Automated Rollback Mechanisms - Automatically routes traffic back to the primary version and scales down the canary when performance metrics cross a failure threshold.
  • Deployment Analysis Webhooks - Orchestrates external webhooks during deployment analysis to validate releases and gate promotions.
  • Progressive Traffic Shifters - Moves traffic to new versions gradually while monitoring performance metrics to decide whether to promote or roll back.
  • Service Traffic Routing - Automates service discovery and traffic routing strategies like canary or blue-green releases.
  • Traffic Routing - Directs network traffic to specific services using proxy configurations to manage canary and blue/green deployment routing.
  • Traffic Routing Controllers - Manages network request flow and routing logic to direct traffic between stable and canary application versions.
  • Weighted Traffic Splitting - Distributes network traffic among multiple versions of a service based on predefined weights.
  • External Monitoring Thresholds - Connect to external monitoring providers via templates to run specific queries and validate canary health against defined threshold ranges.
  • External Metrics Querying - Integrate external monitoring systems to validate canary releases against custom performance indicators using provider-specific query languages and threshold ranges.
  • Analysis Loops - Evaluates real-time telemetry from monitoring providers to automatically promote or roll back releases based on performance thresholds.
  • Custom Metric Scraping - Queries external monitoring tools to validate deployment health against custom thresholds.
  • Release Health Monitoring - Monitors metrics over defined intervals to automatically promote or roll back deployments based on health thresholds.
  • Deployment Configuration Synchronizers - Tracks updates to secrets and configuration maps to ensure stable versions remain consistent with application requirements.
  • Canary Rollout Hooks - Runs pre-rollout and analysis-time webhooks to perform acceptance tests or load generation during the canary deployment process.
  • A/B Testing - Routes traffic to canary versions based on HTTP headers or cookies to target specific user segments for feature testing.
  • Rollout - Provides logic injection points for executing custom tests or validation checks at specific stages of a deployment rollout.
  • Configuration Synchronization - Ensures stable and canary workloads maintain consistent configuration, including secrets and maps, during the deployment lifecycle.
  • Metric Triggers - Integrates with external alert managers to trigger notifications when performance metrics or deployment status indicate failure.
  • Automated Test Execution - Triggers pre-rollout and during-rollout webhooks for acceptance or load testing to verify application stability.
  • Deployment Load Testing Hooks - Triggers custom webhooks during the deployment analysis phase to generate synthetic traffic against the new version.
  • Event-Driven Workflow Triggers - Triggers automated deployment workflows and status notifications in response to cluster events and configuration changes.
  • Webhook Notification Systems - Sends deployment status updates and action payloads to a configured webhook via HTTP POST requests for integration with external notification or management tools.
  • Webhook-Triggered Workflows - Calls external HTTP endpoints during release stages to gate deployments, run pre-checks, or signal rollbacks.
  • Alert Provider Configurations - Defines specific alert providers and severity levels for individual canary deployments to override global notification settings and target relevant channels.
  • Service Mesh - Manipulates service mesh and ingress routing rules to incrementally shift traffic between application versions.
  • Auto-scaling Policies - Integrates with autoscalers to pause traffic shifts while workloads scale, optimizing resource usage during analysis.
  • Rollout Scaling Coordinators - Synchronizes traffic shifting with autoscalers to ensure primary and canary workloads scale appropriately during analysis.
  • Rollout-Aware Autoscalers - Adjusts replica counts dynamically based on custom metrics while shifting traffic to new application versions.
  • GitOps Deployment Management - Manages application rollouts declaratively through GitOps pipelines and automated reconciliation.
  • Release Reconciliation Pausing - Suspends all automation and traffic shifts for a specific workload to prevent new changes from triggering rollouts.
  • Pre-Rollout Hook Runners - Executes webhooks, scripts, or tests before starting a rollout to ensure the new version meets baseline requirements.
  • Delivery Pipeline Suspenders - Suspends the reconciliation of canary resources to stop traffic shifts and ignore changes to workloads or configurations.
  • TCP Canary Controllers - Performs progressive delivery for non-HTTP services by routing TCP traffic between application versions.
  • Alertmanager Alert Forwarders - Triggers external alerts via Prometheus Alertmanager when canary deployments fail based on status metrics.
  • Deployment Conformance Tests - Triggers external webhooks during the release process to perform acceptance checks or manual gating before finalizing a deployment.
  • Pod Traffic Mirroring - Copies incoming requests to the canary version for testing purposes while discarding responses to validate performance.
  • Validation Traffic Mirroring - Duplicates incoming requests to both primary and new versions to collect metrics and verify stability.
  • Test Execution Hooks - Triggers external traffic generation services during deployment rollouts to validate application performance and stability.
  • Ad-Hoc Hook Runs - Calls webhooks during the release process to perform load testing, conformance checks, or manual gating before increasing traffic.
  • Deployment Analysis Hooks - Triggers external HTTP requests at specific deployment stages to validate progress, perform manual approvals, or execute custom logic.
  • Mesh Traffic Policy Management - Orchestrates complex traffic routing, header-based A/B testing, and request mirroring for service mesh-managed applications.
  • Multi-Workload Scaling - Synchronizes autoscaling between primary and canary workloads to maintain resource efficiency during traffic shifts.
  • Rollout Scaling Coordination - Coordinates autoscalers for primary and canary deployments to optimize resource usage while shifting traffic.
  • Pod Autoscaling - Synchronizes autoscaling between primary and canary versions to optimize resource usage during traffic shifts.
  • Analysis Trigger Automators - Triggers analysis cycles automatically based on changes to container images, configuration maps, or secrets.
  • Create-or-Update Release Configurators - Publishes the outcome of a canary analysis and the reasons for promotion or failure to communication tools like Slack or MS Teams.
  • Deployment Rolling Restarts - Detects performance degradation during releases and automatically diverts traffic back to the stable version to minimize impact.
  • HTTP Scan Metric Exposers - Exports internal status and traffic weight data to monitoring systems for health analysis.
  • Service Mesh Control Planes - Integrates with service meshes and ingress controllers to perform incremental traffic shifting and request mirroring.
  • Webhook Integrations - Sends HTTP POST requests at specific deployment stages to automate manual approvals and validation checks.
  • Webhook Triggers - Executes external requests during the canary analysis phase to generate synthetic load or perform custom validation.
  • Alerting Integrations - Triggers external monitoring alerts when canary deployments fail by exposing status metrics.
  • Webhook Event Receivers - Receives and processes webhook callbacks during deployment stages to validate success or initiate rollbacks.
  • External Status Notifications - Publishes the results of a canary analysis to external communication tools to inform teams of successful promotions or failed rollouts.
  • Sticky Session Configurations - Combines weighted routing with sticky sessions to ensure a consistent user experience during a progressive rollout.
  • Request Routing - Modifies request headers, rewrites URLs, and enforces traffic policies during the deployment process to manage request routing.
  • User Affinity Routing - Combines weight-based traffic shifting with cookie routing to ensure users who have seen a new version are not routed back.
  • Component Affinity Routing - Combines weighted routing with session affinity to ensure users consistently reach the same application version.
  • Session Persistence - Ensures a consistent user experience by pinning sessions to specific application versions during progressive delivery.
  • Version Affinity - Maintains consistent user routing to specific application versions to avoid inconsistent experiences during rollouts.
  • Protocol-Specific Routing - Extends traffic shifting capabilities to TCP services by configuring protocol-specific routing rules.
  • Session and Traffic Routing - Combines weighted routing and session persistence to ensure a consistent user experience during canary releases.
  • Session-Specific Request Routing - Directs requests to canary versions based on HTTP match conditions to target specific user segments.
  • Deployment Validation Webhooks - Calls remote services during deployment to perform conformance checks and manual gating before increasing traffic.
  • Conditional Routing - Directs requests to specific application versions based on metadata or application-defined conditions.
  • Layer 4 TCP Routing - Performs progressive delivery for non-HTTP services by managing traffic routing at the transport layer.
  • Load Generation - Simulates traffic during canary analysis to validate application performance and stability under load.
  • Cookie-Based Session Management - Combines weight-based traffic shifting with cookie-based routing to ensure users stay on a specific version.
  • Canary Version Rollouts - Gradually shifts traffic to a new application version by detecting changes in container images, configuration, or secrets.
  • Stable Primary Deployments - Maintains a stable primary deployment and automatically updates it only after new versions pass analysis.
  • Lifecycle Event Watchers - Emits JSON payloads via HTTP POST to external services during the release process.
  • Manual Intervention Gates - Pauses or resumes the promotion process to allow a human operator to approve the transition to the next traffic stage.
  • Webhook Event Notifiers - Triggers external HTTP requests at specific stages of a deployment to validate status, perform manual gates, or notify external systems.
  • Webhook Event Notifications - Sends JSON payloads via HTTP POST requests whenever a release event occurs, enabling integration with external notification systems.
  • Test Execution Triggers - Executes external webhooks to generate synthetic traffic during the analysis phase of a rollout.
  • Canary Infrastructure Orchestrators - Generates the necessary service and routing objects to expose applications within a service mesh and drive automated promotion.
  • Workflow Approval Gates - Pauses automated rollout processes to await manual approval or confirmation from external services.
  • Release Validation Hooks - Runs webhooks for load testing and conformance checks to ensure stability before promoting a release.
  • Severity-Based Routing - Filters notification delivery based on severity levels to manage alerts for manual confirmations or deployment failures.
  • Real-Time Event Notifications - Sends real-time JSON notifications via HTTP POST during the canary process.
  • Alert Notification Management - Defines custom notification channels and severity thresholds globally or per individual deployment to manage operational visibility.
  • Alert Managers - Triggers external alerts through monitoring systems when canary deployments fail to meet analysis criteria.
  • Business-Level Performance Analyzers - Integrates external performance queries to validate releases against business or technical thresholds before promotion.
  • Custom Metric Autoscalers - Integrates external monitoring data to verify application health during deployment using custom success criteria.
  • Analysis-Time Autoscalers - Integrates with event-driven autoscalers to dynamically adjust replica counts based on custom metrics while shifting traffic.
  • Event Monitoring Systems - Sends JSON payloads via HTTP POST to notify external monitoring or communication tools of system events.
  • Analysis Metrics - Exposes Prometheus metrics to track the status of canary analysis and current traffic weight distribution.
  • Metrics Exporters - Exposes metrics that track the status of canary analysis and traffic weight distribution.
  • Metric and Performance Monitors - Evaluates release health using Prometheus queries to ensure key performance indicators stay within defined thresholds.
  • Performance Visualization - Displays real-time metrics for application workloads on a dashboard to help operators track traffic shifts and health during progressive delivery.
  • Query Templates - Create reusable query templates to measure specific operational indicators, such as error rates or latency, from a monitoring provider.
  • Evaluation Metric Monitors - Integrates external monitoring data to evaluate canary performance against specific latency, error rate, or custom business logic thresholds.
  • Application Health Monitors - Evaluates Prometheus queries during a rollout to ensure application performance indicators stay within defined limits.
  • Reconciliation Troubleshooting - Pauses the automated release process for specific workloads to prevent traffic shifting or configuration updates during maintenance.
  • Analysis Traffic Simulators - Triggers artificial request patterns for workloads lacking organic activity to ensure performance monitoring tools have enough data.
  • Prometheus Metrics Exporters - Exposes Prometheus metrics regarding analysis status and traffic weight values to enable external monitoring.
  • Prometheus Metric Ingestion - Evaluates application health against Prometheus thresholds during rollouts to automatically halt or revert deployments.
  • Prometheus Monitoring Practices - Integrates custom Prometheus queries to enforce performance thresholds during automated deployment analysis.
  • Service Level Objective Management - Monitors application metrics against service level objectives to automatically roll back releases if performance thresholds are violated.
  • Automated Rollback Triggers - Integrates with monitoring providers to automatically trigger rollbacks when service health thresholds are breached.
  • Metric Validation Tools - Executes Prometheus queries during a rollout to ensure specific business or technical metrics remain within defined thresholds.
  • Performance Goal Validation - Monitors service level objectives like error rates and response times to automatically roll back releases if performance drops.
  • Time-Series Performance Metrics - Exports internal analysis status and traffic weight values to time-series databases for performance tracking.
  • Webhook Notifications - Streams JSON payloads of deployment actions to HTTP endpoints for external integration.
  • Webhook Quality Gates - Triggers external tests via HTTP webhooks to validate application health and gate the promotion of new releases.
  • Integration Test Suites - Executes automated test suites to verify application stability and conformance in the target environment.
  • Test Automation Tools - Triggers webhooks for conformance and load testing to harden the validation process of a release.
  • Performance Testing - Generates synthetic traffic against a test workload to confirm performance metrics and stability thresholds.
  • Load Testing Tools - Simulates user traffic to evaluate application performance under stress during canary analysis.
  • Rollout Approval Gates - Provides mechanisms to manually pause, resume, or approve the progression of a workload rollout.
  • Rollout Lifecycle Hooks - Triggers external webhooks or scripts to perform acceptance tests and load tests before and during the traffic-shifting process.
  • Scaling-Aware Rollout Pausers - Integrates with autoscalers to pause traffic increases until the primary and canary workloads have scaled appropriately.
  • End-to-End Testing - Runs end-to-end test suites against local clusters to confirm functionality across service meshes and ingress controllers.
  • Smoke Testing - Executes custom test suites or commands before routing traffic to a new version to verify system integrity.
  • Synthetic Traffic Generators - Triggers webhooks to send simulated requests to canary releases during analysis to validate performance.
  • HTTP Header-Based - Route traffic to new versions based on HTTP headers or cookies to ensure consistent user sessions during analysis.
  • Traffic Generation Engines - Simulates high volumes of user traffic to evaluate application performance and stability during deployment analysis.
  • Header-Based Routing - Directs network traffic to specific service versions based on the presence and value of HTTP request headers.
  • Automation and CI/CD - Automates release processes for progressive delivery.
  • Continuous Delivery and GitOps - Operator for automating progressive delivery and canary releases.
  • Continuous Integration and Delivery - Progressive delivery operator for Kubernetes deployments.

Star-Verlauf

Star-Verlauf für weaveworks/flaggerStar-Verlauf für weaveworks/flagger

KI-Suche

Entdecke weitere awesome Repositories

Beschreibe in einfachen Worten, was du brauchst — die KI bewertet tausende kuratierte Open-Source-Projekte nach Relevanz.

Start searching with AI

Open-Source-Alternativen zu Flagger

Ähnliche Open-Source-Projekte, sortiert nach der Anzahl der gemeinsamen Funktionen mit Flagger.
  • fluxcd/flaggerAvatar von fluxcd

    fluxcd/flagger

    5,366Auf GitHub ansehen↗

    Flagger is a Kubernetes progressive delivery operator that automates the gradual release of new software versions. It functions as a canary release manager and traffic shifter, integrating with service meshes and ingress controllers to control request distribution between application versions. The project focuses on reducing production risk by implementing canary releases, blue-green deployments, and A/B testing. It utilizes a metric-driven analysis loop to monitor request success rates and durations, automatically promoting a release or triggering a state-based rollback if health criteria ar

    Go
    Auf GitHub ansehen↗5,366
  • alibaba/higressAvatar von alibaba

    alibaba/higress

    7,558Auf GitHub ansehen↗

    Higress is an AI API gateway and cloud-native traffic manager that functions as a Kubernetes ingress controller. It provides a centralized system for routing, securing, and optimizing traffic directed toward large language models, AI agents, and microservice architectures. The project distinguishes itself through deep AI orchestration, including the ability to host and manage Model Context Protocol servers that transform REST APIs into tools for AI agents. It features specialized AI infrastructure for model request proxying, protocol translation across multiple providers, and semantic-based c

    Goai-gatewayai-nativeapi-gateway
    Auf GitHub ansehen↗7,558
  • fluxcd/flux2Avatar von fluxcd

    fluxcd/flux2

    7,888Auf GitHub ansehen↗

    Flux is a Kubernetes GitOps delivery tool used to automate application deployments by synchronizing cluster state with configurations stored in Git, OCI, or Helm repositories. It functions as a set of controllers that monitor desired state in external sources and continuously reconcile the live cluster to match those definitions. The system distinguishes itself through a multi-cluster management plane that coordinates application delivery across fleets of remote clusters from a central hub. It provides a dedicated mechanism for automated image updates, which scans container registries for new

    Gocontinuous-deliverygitopsgitops-toolkit
    Auf GitHub ansehen↗7,888
  • growthbook/growthbookAvatar von growthbook

    growthbook/growthbook

    7,351Auf GitHub ansehen↗

    GrowthBook is a feature flagging and experimentation platform that utilizes a warehouse-native approach to data analysis. It serves as a system for managing feature rollouts and conducting A/B tests by executing SQL queries directly against existing data warehouses to calculate experiment results. The platform is distinguished by its integration of a Model Context Protocol server, which allows AI coding assistants and IDEs to manage flags and query analytics using natural language. It also provides specialized capabilities for AI model optimization, enabling the testing of prompts and models

    TypeScriptab-testingabtestabtesting
    Auf GitHub ansehen↗7,351
Alle 30 Alternativen zu Flagger anzeigen→

Häufig gestellte Fragen

Was macht weaveworks/flagger?

Flagger is a Kubernetes operator designed to automate the lifecycle of application deployments through progressive delivery. It functions as a controller that monitors custom resource definitions to orchestrate complex release strategies, including canary, blue/green, and A/B testing. By continuously reconciling the desired cluster state with the actual environment, it ensures that deployments adhere to defined specifications while managing the underlying infrastructure…

Was sind die Hauptfunktionen von weaveworks/flagger?

Die Hauptfunktionen von weaveworks/flagger sind: Canary Deployment Controllers, Canary Release Managers, Progressive Delivery Strategies, Progressive Delivery Operators, Rollout Health Monitoring, Traffic-Based, Progressive Release Automators, Blue-Green Deployments.

Welche Open-Source-Alternativen gibt es zu weaveworks/flagger?

Open-Source-Alternativen zu weaveworks/flagger sind unter anderem: fluxcd/flagger — Flagger is a Kubernetes progressive delivery operator that automates the gradual release of new software versions. It… alibaba/higress — Higress is an AI API gateway and cloud-native traffic manager that functions as a Kubernetes ingress controller. It… fluxcd/flux2 — Flux is a Kubernetes GitOps delivery tool used to automate application deployments by synchronizing cluster state with… kubernetes/ingress-nginx — This project is a Kubernetes Ingress Controller that functions as a layer 7 traffic router and NGINX reverse proxy. It… growthbook/growthbook — GrowthBook is a feature flagging and experimentation platform that utilizes a warehouse-native approach to data… agones-dev/agones — Agones is a Kubernetes game server orchestrator designed for hosting, scaling, and managing dedicated multiplayer game…