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
·
fluxcd avatar

fluxcd/flagger

0
View on GitHub↗
5,366 Stars·802 Forks·Go·Apache-2.0·9 Aufrufedocs.flagger.app/main↗

Flagger

Flagger ist ein Kubernetes-Operator für Progressive Delivery, der die schrittweise Veröffentlichung neuer Softwareversionen automatisiert. Er fungiert als Canary-Release-Manager und Traffic-Shifter, der sich in Service Meshes und Ingress-Controller integriert, um die Anfragenverteilung zwischen Anwendungsversionen zu steuern.

Das Projekt zielt darauf ab, das Produktionsrisiko durch Canary-Releases, Blue-Green-Deployments und A/B-Tests zu minimieren. Es nutzt eine metrikbasierte Analyseschleife, um Erfolgsraten und Antwortzeiten zu überwachen und Releases automatisch zu fördern oder bei Nichterfüllung der Gesundheitskriterien ein zustandsbasiertes Rollback einzuleiten.

Das Tool bietet zusätzliche Validierung durch Webhook-basierte Testausführung und synthetische Lasttests zur Stabilitätsprüfung. Zudem enthält es Mechanismen für manuelle Rollout-Gates, Konfigurationssynchronisation und Benachrichtigungen an externe Kommunikationsdienste.

Der Controller wird mittels Standard-Paketmanagern im Cluster bereitgestellt und unterstützt gängige Service Meshes und Ingress-Controller.

Features

  • Progressive Delivery Strategies - Automates progressive delivery strategies, including canary and blue-green updates, to reduce production risk.
  • A/B Testing - Performs A/B testing by splitting traffic between different versions to compare performance and user behavior.
  • Blue-Green Deployments - Executes blue-green deployments by routing traffic between two identical environments to ensure version stability.
  • Change Rollback Mechanisms - Automatically reverts traffic to the stable version when health metrics fail to meet required thresholds.
  • Custom Resource Controllers - Provides a custom resource controller that monitors the Kubernetes API to automate progressive delivery workflows.
  • Automated Rollout Managers - Manages application updates through incremental rollouts with automated rollback capabilities based on metric analysis.
  • Deployment Strategies - Implements varied release patterns using weighted traffic, header-based routing, and traffic mirroring.
  • Deployment Strategy Mappings - Implements a declarative system to map configuration files to specific deployment patterns like canary or blue-green.
  • Automated Canary Analysis - Automates canary analysis by comparing real-time metrics against a stable baseline to decide on promotion.
  • Automated Metric Analysis - Continuously compares real-time performance metrics between stable and canary versions to automate release decisions.
  • Canary Release Managers - Acts as a canary release manager by gradually routing traffic and monitoring health to prevent outages.
  • Kubernetes Operators - Implements the Kubernetes operator pattern using custom resources to automate progressive delivery workflows.
  • Kubernetes Traffic Controllers - Integrates with service meshes and ingress controllers to automate network traffic routing within Kubernetes.
  • Automated Release Validation - Provides automated promotion and rollback based on webhook-driven tests and real-time health metrics.
  • Weighted Traffic Splitting - Updates service mesh and ingress configurations to incrementally shift request percentages between application versions.
  • Release Health Monitoring - Monitors request success rates and durations to automatically promote or roll back releases based on health.
  • Automated Test Execution - Executes automated test suites via webhooks during the rollout to verify delivery process stability.
  • Release Quality Validation - Triggers external acceptance and load tests to ensure new versions meet established quality standards before full promotion.
  • Workflow Approval Gates - Provides manual approval steps to pause or resume the promotion process for human oversight.
  • Webhook Quality Gates - Triggers external HTTP endpoints to execute acceptance or load tests as quality gates during the rollout process.
  • Rollout Approval Gates - Enables manual oversight of a release through a pause-and-resume approval mechanism for workload promotion.
  • Synthetic Traffic Generators - Generates synthetic traffic against application versions to verify stability and performance during rollout.
  • Kubernetes Ecosystem - Automates progressive delivery and canary deployments.

Star-Verlauf

Star-Verlauf für fluxcd/flaggerStar-Verlauf für fluxcd/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

Häufig gestellte Fragen

Was macht fluxcd/flagger?

Flagger ist ein Kubernetes-Operator für Progressive Delivery, der die schrittweise Veröffentlichung neuer Softwareversionen automatisiert. Er fungiert als Canary-Release-Manager und Traffic-Shifter, der sich in Service Meshes und Ingress-Controller integriert, um die Anfragenverteilung zwischen Anwendungsversionen zu steuern.

Was sind die Hauptfunktionen von fluxcd/flagger?

Die Hauptfunktionen von fluxcd/flagger sind: Progressive Delivery Strategies, A/B Testing, Blue-Green Deployments, Change Rollback Mechanisms, Custom Resource Controllers, Automated Rollout Managers, Deployment Strategies, Deployment Strategy Mappings.

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

Open-Source-Alternativen zu fluxcd/flagger sind unter anderem: weaveworks/flagger — Flagger is a Kubernetes operator designed to automate the lifecycle of application deployments through progressive… alibaba/higress — Higress is an AI API gateway and cloud-native traffic manager that functions as a Kubernetes ingress controller. It… kube-logging/logging-operator — The logging operator is a Kubernetes-native controller designed to automate the deployment, configuration, and… growthbook/growthbook — GrowthBook is a feature flagging and experimentation platform that utilizes a warehouse-native approach to data… spinnaker/spinnaker — Spinnaker is a multi-cloud continuous delivery platform designed to automate software releases and deployment… kserve/kserve — KServe is a Kubernetes-native platform for deploying and serving machine learning models as scalable inference…

Open-Source-Alternativen zu Flagger

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

    weaveworks/flagger

    5,362Auf GitHub ansehen↗

    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 eval

    Go
    Auf GitHub ansehen↗5,362
  • 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
  • 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
  • kube-logging/logging-operatorAvatar von kube-logging

    kube-logging/logging-operator

    1,696Auf GitHub ansehen↗

    The logging operator is a Kubernetes-native controller designed to automate the deployment, configuration, and lifecycle management of log collection and routing infrastructure. By utilizing custom resource definitions, it provides a declarative framework for standardizing how container logs are captured, processed, and forwarded across distributed cluster environments. The project distinguishes itself through its support for multi-tenant logging architectures, allowing administrators to enforce namespace-scoped isolation for log collection and routing configurations. It employs a sidecar inj

    Gocloud-nativekuberneteskubernetes-operator
    Auf GitHub ansehen↗1,696
  • Alle 30 Alternativen zu Flagger anzeigen→