Upgrade kustomize to 2.5.3

Author: AndreaGiardini

argocd_deploy/apps/argocd.yaml

@@ -11,7 +11,7 @@ spec:
     targetRevision: HEAD
     path: argocd_deploy
     kustomize:
-      version: v4.2.0
+      version: v4.5.3
 
   destination:
     server: https://kubernetes.default.svc

argocd_deploy/overlays/argocd-cm.yaml

@@ -3,4 +3,4 @@ kind: ConfigMap
 metadata:
   name: argocd-cm
 data:
-  kustomize.version.v4.2.0: /custom-tools/kustomize_4_2_0
+  kustomize.version.v4.5.3: /custom-tools/kustomize_4_5_3

argocd_deploy/overlays/argocd-repo-server-deploy.yaml

@@ -16,8 +16,8 @@ spec:
         image: busybox:stable
         command: [sh, -c]
         args:
-        - wget -qO- https://github.com/kubernetes-sigs/kustomize/releases/download/kustomize%2Fv4.2.0/kustomize_v4.2.0_linux_amd64.tar.gz | tar -xvzf - &&
-          mv kustomize /custom-tools/kustomize_4_2_0
+        - wget -qO- https://github.com/kubernetes-sigs/kustomize/releases/download/kustomize%2Fv4.5.3/kustomize_v4.5.3_linux_amd64.tar.gz | tar -xvzf - &&
+          mv kustomize /custom-tools/kustomize_4_5_3
         volumeMounts:
         - mountPath: /custom-tools
           name: custom-tools

docs/argo_upgrade.md

@@ -15,6 +15,9 @@ If the waiting is too long, you can force Argo to refresh the definition
 manually by opening the web interface and pressing the `Refresh` button
 under the `argocd` application.
 
+You might have to restart the `kubectl proxy` command in order to see the
+new interface. That's because a new Argo Pod will be created.
+
 It is possible for Argo to receive webhook from Github whenever a new
 commit is pushed
 ([docs](https://argoproj.github.io/argo-cd/operator-manual/webhook/)).