chore(deps): update dependency argoproj/argo-cd to v2.4.3
This MR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
argoproj/argo-cd | Kustomization | patch |
v2.4.0 -> v2.4.3
|
Release Notes
argoproj/argo-cd
v2.4.3
Quick Start
Non-HA:
kubectl create namespace argocd
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/v2.4.3/manifests/install.yaml
HA:
kubectl create namespace argocd
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/v2.4.3/manifests/ha/install.yaml
Bug fixes
- fix: respect OIDC providers' supported token signing algorithms (#9433) (#9761)
- fix websockets for terminal not working on subPath (#9795)
- fix: avoid closing and re-opening port of api server settings change (#9778)
- fix: [ArgoCD] Fixing webhook typo in case of error in GetManifests (#9671)
- fix: overrides should not appear in the manifest cache key (#9601)
v2.4.2
Quick Start
Non-HA:
kubectl create namespace argocd
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/v2.4.2/manifests/install.yaml
HA:
kubectl create namespace argocd
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/v2.4.2/manifests/ha/install.yaml
Bug fixes
- fix: project filter (#9651) (#9709)
- fix: broken symlink in Dockerfile (#9674)
- fix: updated baseHRefRegex to perform lazy match (#9724)
- fix: updated config file permission requirements for windows (#9666)
Other
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.yaml
HA:
kubectl create namespace argocd
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/v2.4.1/manifests/ha/install.yaml
Security 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.size
config 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)
Configuration
-
If you want to rebase/retry this MR, click this checkbox.
This MR has been generated by Renovate Bot.