Skip to main content

Updating the application

During the development lifecycle, there are new container images or the development team may want to change the configuration of the application. You need to update the application to reflect the latest changes following the GitOps workflow.

In this lab excerise, we'll update the catalog application to increase replicas to handle higher traffic with Argo CD.

info

Normally, you should update the configuration files in the Git repository and commit the changes. Argo CD will then detect the changes and reconcile that in the cluster. In this lab exercise, we provide you with a new version of the file in a different path to simulate that we have made a change. Therefore, we'll instead update the path for our argocd-demo application with the new file.

Update replicas of the catalog application in the kustomization file to 3:

/workspace/modules/automation/gitops/argocd/update-app/kustomization.yaml
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
namespace: argocd-demo
resources:
  - ../../../../../manifests/catalog/
replicas:
  - count: 3
    name: catalog

Update Argo CD app to reflect the latest changes:

~$argocd app set argocd-demo --path environment/workspace/modules/automation/gitops/argocd/update-app
Flip back to the Argo CD UI and you should see the application is in OutOfSync state.
Click on the Sync button to sync the application with the latest changes.
After a few seconds, you should see the application is in Synced state. Your application is now updated with the latest changes and the replicas is increased to 3.
We're now successfully updated the application with the latest changes using Argo CD and GitOps workflow.