feat(infra-apps): update argo-cd from 4.10 to 5.4

[hairmare]

Description

Updates the Argo CD Helm chart from 4.10 to 5.4. The changes are summarized below.

The most important change that affects us is the one leading to the 5.x release. YOu can check if you need to do anything with the following steps:

• Check if kubectl -n infra-argocd get deployments returns argocd-server, if it does this deployment will change it to a StatefulSet for HA purposes.
• Check if configs.repositories is set, if it is, some manual intervention will be needed
• Check if configs.repositoryCredentials is set, if it is, some manual intervention will be needed
• Check if server.additionalApplications or server.additionalProjects are used, if they are, intervention is needed. I will prepare a follow-up PR that prepares to use argocd-apps in cases where we are affected.

A complete list of the changes may be found in the README: https://github.com/argoproj/argo-helm/tree/main/charts/argo-cd#upgrading

Issues

• Fixes Version 5.4.4 of argocd is available! #788

5.0

• chore(argo-cd)!: Remove apps, appprojs and deprecated features argoproj/argo-helm#1417
  • [Removed]: Legacy support to run controller as a Deployment
  • [Removed]: Legacy support to use old format of repository secrets
  • [Removed]: Parameters server.additionalApplications and server.additionalProjects are moved to a separate chart - argocd-apps

5.1

• feat(argo-cd): Added spec.behavior in HPA argoproj/argo-helm#1376
  • [Added]: Ability to customize HPAs spec.behavior field

5.2

• feat(argo-cd): manage CRD by Helm argoproj/argo-helm#1342
  • [Changed]: manage CRD by Helm (uses the charts crd/ directory like it's supposed to)
• feat(argo-cd): update redis-ha to v4.20.0 argoproj/argo-helm#1421
  • [Changed]: Update redis-ha

5.3

• chore(argo-cd): Move notification configs argoproj/argo-helm#1419
  • [Changed]: Move notification configs to config folder
  • [Changed]: Use default names for notification configs
• feat(argo-cd): Set ARGOCD_CONTROLLER_REPLICAS automatically argoproj/argo-helm#1413
  • [Changed]: Env variable ARGOCD_CONTROLLER_REPLICAS is now automatically set by replica count
• fix(argo-cd): invalid yaml with topologySpreadConstraints argoproj/argo-helm#1423
  • [Fixed]: Invalid yaml for controller topologySpreadConstraints
• fix(argo-cd): Removal of duplicate mapping key annotations in crds argoproj/argo-helm#1424
  • [Fixed]: Removal of duplicate mapping key annotations in crds
• chore: Change helm chart maintainers to argoproj argoproj/argo-helm#1426
  • [Changed]: Helm chart maintainers standardized to argoproj
• chore(argo-cd): Upgrade redis-ha chart argoproj/argo-helm#1429
  • [Changed]: Upgrade Redis HA to 4.22.1
• feat(argo-cd): Add appHardResyncPeriod option for controller argoproj/argo-helm#1320
  • [Added]: Add appHardResyncPeriod option for application controller

5.4

• fix(argo-cd): Remove version labels to avoid invalid characters argoproj/argo-helm#1432
  • [Changed]: Remove version labels to avoid invalid characters
• fix(argo-cd): add automountServiceAccountToken to repoServer argoproj/argo-helm#1436
  • [Fixed]: Template existing value automountServiceAccountToken into repo-server
• feat(argo-cd): Add priorityClassName to notifications argoproj/argo-helm#1439
  • [Added]: Add priorityClassName to notifications controller
• fix(argo-cd): Duplicated dex init containers argoproj/argo-helm#1442
  • [Fixed]: Additional initContainers are handled correctly in the dex deployment

Checklist

• This PR contains a description of the changes I'm making
• I updated the version in Chart.yaml
• I updated applicable README.md files using pre-commit run
• I documented any high-level concepts I'm introducing in docs/
• CI is currently green and this is ready for review
• I am ready to test changes after they are applied and released

[eyenx]

I will create an issue on our board for this. especially the repositorysecrets are used here and there.

[eyenx]

Fixes #788

[hairmare]

I've also started to prepare some internal docs.

Please reach out if you run into any issues with this update.