devtron
devtron copied to clipboard
Bump github.com/argoproj/argo-cd/v2 from 2.4.0 to 2.4.1
Bumps github.com/argoproj/argo-cd/v2 from 2.4.0 to 2.4.1.
Release notes
Sourced from github.com/argoproj/argo-cd/v2's releases.
v2.4.1
Quick Start
Non-HA:
kubectl create namespace argocd kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/v2.4.1/manifests/install.yamlHA:
kubectl create namespace argocd kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/v2.4.1/manifests/ha/install.yamlSecurity fixes
- CRITICAL: External URLs for Deployments can include javascript (GHSA-h4w9-6x78-8vrj)
- HIGH: Insecure entropy in PKCE/Oauth2/OIDC params (GHSA-2m7h-86qq-fp4v)
- MODERATE: DoS through large directory app manifest files (GHSA-jhqp-vf4w-rpwq)
- MODERATE: Symlink following allows leaking out-of-bounds YAML files from Argo CD repo-server (GHSA-q4w5-4gq2-98vm)
Potentially-breaking changes
From the GHSA-2m7h-86qq-fp4v description:
The patch introduces a new
reposerver.max.combined.directory.manifests.sizeconfig parameter, which you should tune before upgrading in production. It caps the maximum total file size of .yaml/.yml/.json files in directory-type (raw manifest) Applications. The default max is 10M per Application. This max is designed to keep any single app from consuming more than 3G of memory in the repo-server (manifests consume more space in memory than on disk). The 300x ratio assumes a maliciously-crafted manifest file. If you only want to protect against accidental excessive memory use, it is probably safe to use a smaller ratio.If your organization uses directory-type Applications with very many manifests or very large manifests then check the size of those manifests and tune the config parameter before deploying this change to production. When testing, make sure to do a "hard refresh" in either the CLI or UI to test your directory-type App. That will make sure you're using the new max logic instead of relying on cached manifest responses from Redis.
Other
- test: directory app manifest generation (#9503)
- chore: Implement tests to validate aws auth retry (#9627)
- chore: Implement a retry in aws auth command (#9618)
- test: Remove temp directories from repo server tests (#9501)
- test: Make context tests idempodent (#9502)
- test: fix plugin var test for OSX (#9590)
- docs: Document how to deploy from the root of the git repository (#9632)
- docs: added environment variables documentation (#8680)
Commits
52e6025Bump version to 2.4.1b121b89Bump version to 2.4.112149c0chore: fix docs gen9d67469Merge pull request from GHSA-jhqp-vf4w-rpwq04c3053Merge pull request from GHSA-q4w5-4gq2-98vm17f7f4fMerge pull request from GHSA-2m7h-86qq-fp4v8bc3ef6Merge pull request from GHSA-h4w9-6x78-8vrj8fe9a58test: directory app manifest generation (#9503)269c61achore: Implement tests to validate aws auth retry (#9627)9a08c12chore: Implement a retry in aws auth command (#9618)- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)@dependabot use these labelswill set the current labels as the default for future PRs for this repo and language@dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language@dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language@dependabot use this milestonewill set the current milestone as the default for future PRs for this repo and language
You can disable automated security fix PRs for this repo from the Security Alerts page.
@kartik-579 Can we do these suggested changes?
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version.
If you change your mind, just re-open this PR and I'll resolve any conflicts on it.