Argo Helm is a community-maintained collection of Helm charts designed to deploy and manage ArgoProj projects within Kubernetes environments. The repository serves as the official packaging mechanism for Argo CD, Argo Workflows, Argo Events, and Argo Rollouts, enabling users to install and configure these GitOps and workflow orchestration tools through Helm, the Kubernetes package manager. The charts are written primarily in Mustache templating language and are hosted at argoproj.github.io/argo-helm.
The repository explicitly maintains a version support policy focused on the latest upstream versions only. The maintainers do not provide bug fixes or security patches for older versions, instead encouraging all users to upgrade to the latest release to benefit from recent features, bug fixes, and security patches. For users unable to immediately upgrade to the latest version, the documentation provides a workaround approach: first upgrade the Helm chart to the latest patch version within the same minor release, then override the image tag to use a specific application version if needed. The maintainers acknowledge this workaround does not always function reliably and continue to recommend full upgrades as the preferred solution.
A notable feature of these charts is their handling of custom resource definitions. Users can disable CRD installation for the four main charts by setting the crds.install flag to false during installation. The charts have moved CRDs from the traditional crds folder into templates to work around Helm's design limitation that prevents CRD upgrades in the crds folder. This architectural decision allows for more flexible CRD management and updates compared to standard Helm practices.
The charts leverage Helm's built-in Capabilities object to detect cluster features and adapt accordingly. They use Capabilities.APIVersions.Has primarily to determine whether ServiceMonitor CRDs from the prometheus-operator exist in the cluster, and Capabilities.KubeVersion.Version to select the correct API versions for resources like policies, handling differences between policy/v1 and policy/v1beta1. Users templating manifests without installing require the --api-versions parameter to helm template to ensure Helm receives available APIs from the Kubernetes cluster.
GitGenius activity tracking shows the repository maintains active engagement with a median issue and pull request response latency of zero hours and a mean latency of approximately 2927.7 hours across 361 tracked items. The most frequently applied issue labels are bug with 215 occurrences, argo-cd with 195 occurrences, and no-issue-activity with 120 occurrences. The most active contributors tracked are yu-croco with 406 events, mkilchhofer with 225 events, and jmeridth with 49 events. The repository shares overlapping contributors with microsoft/vscode, argoproj/argo-cd, and argoproj/argo-workflows, indicating cross-project collaboration within the ArgoProj ecosystem.
The project welcomes community contributions and provides detailed contribution guidelines. Releases are managed independently for each Helm chart with changelogs tracked on individual releases. The maintainers note their small team size and encourage interested contributors to join the team by reviewing the Community Membership Guide, indicating openness to expanding the project's support capabilities as the contributor base grows.
