yawyd313 f1ed1fab88 init 11 months ago
..
.github f1ed1fab88 init 11 months ago
charts f1ed1fab88 init 11 months ago
scripts f1ed1fab88 init 11 months ago
.clomonitor.yml f1ed1fab88 init 11 months ago
.editorconfig f1ed1fab88 init 11 months ago
.gitignore f1ed1fab88 init 11 months ago
CODE_OF_CONDUCT.md f1ed1fab88 init 11 months ago
CONTRIBUTING.md f1ed1fab88 init 11 months ago
EMERITUS.md f1ed1fab88 init 11 months ago
LICENSE f1ed1fab88 init 11 months ago
README.md f1ed1fab88 init 11 months ago
SECURITY-INSIGHTS.yml f1ed1fab88 init 11 months ago
SECURITY.md f1ed1fab88 init 11 months ago
renovate.json f1ed1fab88 init 11 months ago

README.md

Argo Helm Charts

Slack License Chart Publish Artifact HUB CLOMonitor OpenSSF Scorecard OpenSSF Best Practices

Argo Helm is a collection of community maintained charts for https://argoproj.github.io projects. The charts can be added using following command:

helm repo add argo https://argoproj.github.io/argo-helm

Contributing

We'd love to have you contribute! Please refer to our contribution guidelines for details.

Custom resource definitions

Some users would prefer to install the CRDs outside of the chart. You can disable the CRD installation of the main four charts (argo-cd, argo-workflows, argo-events, argo-rollouts) by using --set crds.install=false when installing the chart.

Helm cannot upgrade custom resource definitions in the <chart>/crds folder by design. Our CRDs have been moved to <chart>/templates to address this design decision.

If you are using versions of a chart that have the CRDs in the root of the chart or have elected to manage the Argo CRDs outside of the chart, please use kubectl to upgrade CRDs manually from templates/crds folder or via the manifests from the upstream project repo:

Example:

kubectl apply -k "https://github.com/argoproj/argo-cd/manifests/crds?ref=<appVersion>"

# Eg. version v2.4.9
kubectl apply -k "https://github.com/argoproj/argo-cd/manifests/crds?ref=v2.4.9"

Security Policy

Please refer to SECURITY.md for details on how to report security issues.

Changelog

Releases are managed independently for each helm chart, and changelogs are tracked on each release. Read more about this process here.