[argocd] Upgrade to 2.8

We are a couple of versions late on our argocd.
A couple of bug/security fixes were released since the 2.5.2 we are currently using.

added activity::MRO argocd kubernetes labels

changed the description

changed title from [argocd] Upgrade to 2.5.7 to [argocd] Upgrade to {++}2.5.7{+ 2.6.x+}

marked this issue as related to #4999 (closed)

assigned to @vsellier

changed title from [argocd] Upgrade to {--}2.{-5.7 2.6.x-} to [argocd] Upgrade to 2.8

even if the documention doesn't forbid a direct upgrade from 2.5 to 2.8, a progressive upgrade will allow to detect issue more quickly.

So the upgrade plan will be: 2.5.2 -> 2.6.13 -> 2.7.11 -> 2.8.0

• 2.5.2 -> 2.6.13
• 2.6.13 -> 2.7.11
• 2.7.11 -> 2.8.0

mentioned in commit swh/infra/ci-cd/k8s-clusters-conf@32293dce

Argo upgraded to 2.6.13, all the applications recovered, looks like there is no issues

mentioned in commit swh/infra/ci-cd/k8s-clusters-conf@f2d5f7d9

Argo upgraded to 2.7.11, all the applications recovered, looks like there is no issues

mentioned in commit swh/infra/ci-cd/k8s-clusters-conf@dd2a6302

Argo upgraded to 2.8.0, all the applications recovered, looks like there is no issues

closed