argoproj
/
argo-helm
mirror of https://github.com/argoproj/argo-helm.git
1
0
Fork 1
Code Issues Packages Projects Releases Wiki Activity
ArgoProj Helm Charts
1,113 Commits
4 Branches
1,048 Tags
77 MiB
Smarty 71.7%
Python 23.3%
Shell 4.4%
Dockerfile 0.6%
 
 
 
 
Go to file
Tal Yitzhak 2fbc856637
feat(argo-rollouts): Fix cluster role missing access in argo rollouts dashboard (#2081) 
* docs(github): comment out notational pieces of PR template (#1969)

github: comment out notational pieces of PR template

- the DCO and publishing sentences are not filled out during PRs
  and are purely notational
  - comment them out with HTML comments, as is common practice
    - example from a repo I maintain: f6db59613a/.github/issue_template.md?plain=1#L2
      - I copied that from other repos too
  - these comments are still visible to the PR author, just not visible
    when rendered, keeping the PR more concise

Signed-off-by: Anton Gilgur <agilgur5@gmail.com>
Co-authored-by: Marco Kilchhofer <mkilchhofer@users.noreply.github.com>
Signed-off-by: Tal Yitzhak <talyi@jfrog.com>

* Added missing permissions for argo rollouts dashboard cluster role - for config map, should be able to get

Signed-off-by: Tal Yitzhak <talyi@jfrog.com>

* Added missing permissions for argo rollouts dashboard cluster role - for config map, should be able to get

Signed-off-by: Tal Yitzhak <talyi@jfrog.com>

---------

Signed-off-by: Anton Gilgur <agilgur5@gmail.com>
Signed-off-by: Tal Yitzhak <talyi@jfrog.com>
Signed-off-by: Tal Yitzhak <yitzhtal@gmail.com>
Co-authored-by: Anton Gilgur <4970083+agilgur5@users.noreply.github.com>
Co-authored-by: Marco Kilchhofer <mkilchhofer@users.noreply.github.com>
Co-authored-by: Tal Yitzhak <talyi@jfrog.com>
 		2023-05-27 23:51:41 +09:00
.github chore(deps): bump helm/kind-action from 1.5.0 to 1.7.0 (#2067) 2023-05-21 11:07:08 +09:00
charts feat(argo-rollouts): Fix cluster role missing access in argo rollouts dashboard (#2081) 2023-05-27 23:51:41 +09:00
scripts fix(argo-cd): Update CONTRIBUTING docs (#1782) 2023-01-20 08:33:55 -06:00
.clomonitor.yml chore(github): Added CLOMoitor exclusions related to dependency tracking (#1543) 2022-10-12 02:29:44 -05:00
.editorconfig chore(argo-rollouts): Upgrade argo-rollouts to 1.3.1 (#1500) 2022-10-01 00:29:03 +02:00
.gitignore feat: imagePullSecrets for servers and controllers (#361) 2020-08-30 13:10:09 -04:00
CODEOWNERS chore(github): Add tico24 to codeowners (#2047) 2023-05-10 23:30:17 +09:00
CODE_OF_CONDUCT.md chore(github): Update repo files (#2006) 2023-05-05 21:23:04 +01:00
CONTRIBUTING.md chore(argo-workflows): Update docs to mention why CRDs are in templates folder (#1857) 2023-02-23 11:44:01 -06:00
EMERITUS.md chore(github): Update repo files (#2006) 2023-05-05 21:23:04 +01:00
LICENSE Add readme file 2018-09-03 07:23:49 -07:00
README.md fix(github): fix error in codeowners file and update README about security (#2015) 2023-05-06 08:18:37 -05:00
SECURITY.md chore(github): Update repo files (#2006) 2023-05-05 21:23:04 +01:00

README.md

Argo Helm Charts

Slack License Chart Publish Artifact HUB CLOMonitor OpenSSF Scorecard

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 Workflows 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.