argoproj/argo-workflows

Workflow Engine for Kubernetes

View on GitHub ↗Jump to charts ↓

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 15 minutes ago
Added to GitGenius on August 31st, 2021
Created on August 21st, 2017
Open Issues & Pull Requests: 1,325 (+0)
GitHub issues: Enabled
Number of forks: 3,687
Total Stargazers: 17,026 (+0)
Total Subscribers: 203 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 10.9 days
Mean response time: 328.3 days
90th percentile: 1100.1 days
Tracked items: 1,575

Maintainer activity

20 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 7, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits.

How this project is maintained

Roughly one issue in four opened in the past year never receives a reply. 85% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "type/regression" is answered fastest, typically in about 27 hours, while "area/templating" waits about 12 months. 53% of tracked open issues have had no activity in three months. Only 52% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 995
New in 7 days: 7
Closed in 7 days: 3
Avg open age: 968 days
Stale 30+ days: 957
Stale 90+ days: 891

Recent activity

Opened in 7 days: 5
Closed in 7 days: 3
Comments in 7 days: 5
Events in 7 days: 10

Top labels

  • area/ui (396)
  • area/controller (362)
  • type/regression (341)
  • solution/workaround (329)
  • P3 (326)
  • area/artifacts (274)
  • good first issue (266)
  • type/support (254)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Argo Workflows is a container-native workflow engine for Kubernetes that orchestrates parallel jobs as a Kubernetes Custom Resource Definition.

The tool addresses the need to define and execute complex multi-step workloads on Kubernetes by letting developers model workflows either as sequences of tasks or as directed acyclic graphs that capture task dependencies. Each step in a workflow runs as a container, making it straightforward to express compute-intensive jobs for machine learning, data processing, infrastructure automation, and CI/CD pipelines. The engine handles parallel execution and scales across Kubernetes clusters without the overhead of legacy VM-based workflow systems.

Argo Workflows suits teams already committed to Kubernetes who need to orchestrate batch jobs, machine learning pipelines, or data processing workflows. It works well for organizations seeking a cloud-agnostic solution that runs on any Kubernetes cluster. The tool is particularly valuable for Python users through the Hera SDK, which provides a programmatic interface to define workflows. Anyone evaluating this tool should know it is designed specifically for container-native environments and assumes Kubernetes as the underlying platform.

The project receives almost all of its issue reports from outside users rather than the core team, reflecting a substantial base of adopters running it in production. Responses to issues and pull requests typically arrive within one to two weeks. Work in the issue tracker concentrates on the controller implementation, UI improvements, and lower-priority items, suggesting the core engine remains stable while development effort focuses on operational tooling and user experience.