Upgrade Additional Argo from v4.1.1 to v4.1.2
This document describes how to upgrade Additional Argo(Argo CD and Argo Rollouts) from v4.1.1 to v4.1.2 on a Kubernetes cluster.
Following are the sequence of activities to perform the upgrade.
Pre-requisites
Cloning the Repo and update values file
Helm upgrade
Post Installation Steps
If an upgrade fails
Pre-requisites:
Users need to have access to the Kubernetes Cluster and namespace where Additional Argo(Argo CD,Argo Rollouts) are running i.e v4.1.1 is running.
Users need to have access to Github and be able to clone enterprise-argo repo.
Cloning the Repo and update values file:
Clone the enterprise-argo repo by using the below command:
You need to use argocd-rollouts-values.yaml file for upgrading to v4.1.2. Update the argocd-rollouts-values.yaml file with specifically ArgoCD URL, Argo Rollouts URL by using the below commands.
Full values.yaml is available at: https://github.com/OpsMx/enterprise-argo/blob/main/charts/isdargo/values.yaml. If you need any additional clarifications with respect to values.yaml for installation, please contact OpsMx support.
Helm upgrade
Go to the cloned repo, For eg: cd enterprise-argo and execute the below command:
Wait for 10 minutes till the helm upgrade completes.
Post Installation Steps
Login to Argo CD UI and check whether the Argo CD Version is updated on the left side of pannel.
Please check if all the applications are reflecting in Argo CD.
If an upgrade fails
If anything goes wrong during upgrade, please Rollback to the previous version using the below command:
Last updated