logo

argoproj/argo-helm

ArgoProj Helm Charts

View on GitHub ↗Jump to charts ↓Open shareable report →

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

Summary Information

Updated 2 hours ago
Type:Template / ExampleCategory(s):Kubernetes & OperatorsInfrastructure as Code & ConfigCloud Native & Infrastructure
Added to GitGenius on September 1st, 2021
Created on October 10th, 2017
Open Issues & Pull Requests: 45 (+1)
GitHub issues: Enabled
Number of forks: 2,118
Total Stargazers: 2,378 (+0)
Total Subscribers: 26 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 39.5 hours
Mean response time: 87.7 days
90th percentile: 181.6 days
Tracked items: 351

Most active contributors

Sign in to see contributor activity.
Sign in

Related repositories by overlapping contributors

Maintainer activity

5 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

About 13% of issues opened in the past year have never received a reply. 95% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "question" is answered fastest, typically in about 5 hours, while "no-issue-activity" waits about 12 days. 88% of issues opened in the past year have been closed, leaving a working backlog. Three people close 55% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 21
New in 7 days: 0
Closed in 7 days: 2
Avg open age: 247 days
Stale 30+ days: 13
Stale 90+ days: 2

Recent activity

Opened in 7 days: 0
Closed in 7 days: 2
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (643)
  • argo-cd (538)
  • enhancement (407)
  • no-issue-activity (365)
  • argo-workflows (185)
  • question (76)
  • argo-rollouts (49)
  • awaiting-upstream (43)

Most active issues this week

Sign in to see which issues are moving.
Sign in
Explore full issue details

Detailed Description

Argo Helm is a collection of community-maintained Helm charts for deploying ArgoProj projects including Argo CD, Argo Workflows, Argo Events, and Argo Rollouts.

The charts address the need to deploy and configure complex Argo tools on Kubernetes clusters. They handle version-specific API compatibility through Helm's Capabilities object, detecting cluster features like ServiceMonitor availability and appropriate API versions for resources such as PodDisruptionBudgets. The charts allow users to manage custom resource definitions either within the chart or externally by setting the crds.install flag, and they handle CRD upgrades through templates rather than the crds folder to work around Helm's design limitations.

Teams running Argo tools on Kubernetes should adopt these charts if they want a standardized, tested deployment path. The project explicitly supports only the latest version of upstream projects, with no backported bug fixes or security patches for older chart versions. Users unable to upgrade the chart itself can override the image tag to pin a specific upstream version, though this approach is not guaranteed to work. The maintainers acknowledge the support limitation stems from a small team and invite contributors to help expand coverage.

The project sustains a substantial user base, with almost all open issues originating from outside users rather than the core team. Maintainers typically respond to new issues and pull requests within a few days. Work in the issue tracker centers on bug reports, Argo CD-specific issues, and inactive issues.