Managing Argo CD applications

Application creation and deployment is one part of the continuous deployment/delivery process. An equally important part is optimizing deployed applications as and when needed.

There are two aspects to managing and optimizing Argo CD applications in Codefresh:

• Optimizing deployments through GitOps Environments and Products
• Managing individual applications

Optimizing application deployments

• GitOps Environments
  The GitOps Environments dashboard visualizes Argo CD applications within the context of their environments, allowing you to track their journey through the software development lifecycle.

• GitOps Products
  The GitOps Products dashboard displays applications grouped within a Product, with version, Git, and feature-tracking information.

Managing individual applications

NOTE
The actions you can perform depend on the permissions assigned to you.

• Edit Argo CD applications
  Optimize deployed applications by changing application definitions when needed.

• Manage Application Groups
  Add to and remove applications from Application Groups.

• Synchronize Argo CD applications
  Sync applications on-demand by manually applying sync options or by manually selecting the resources to sync.

• Configure sync-timeout for Argo CD applications
  Configure the sync-timeout through an annotation to be notified of long sync operations.

• Terminate sync for Argo CD applications
  With a single-click, terminate on-going sync processes when needed.

• Refresh Argo CD applications
  Manually refresh applications with a single-click, as an alternative to manually synchronizing them.

• Rollback Argo CD applications
  Rollback applications to previous deployment versions.

• Manage rollouts for deployments
  Control ongoing rollouts by resuming indefinitely paused steps, promoting rollouts, aborting, restarting and retrying rollouts.

• Rename an ApplicationSet
  Change the name of an existing ApplicationSet and point all its applications to the new ApplicationSet.

• Delete Argo CD applications
  Delete unused or legacy applications to avoid clutter and remove unnecessary resources.

  To delete specific resources within an application, see Delete application resources.

GitOps Environments & Argo CD applications

To track, optimize, and manage deployments at scale you need a way to visualize applications at every stage of their development and deployment lifecycle. Our custom Environment resource allows you to do just this without the need for complex configuration and maintenance overhead.

Create Environments by defining one or more pairs of clusters and namespaces for it. Codefresh collates the data on these Environments, populates them with the applications deployed to the target clusters and namespaces. Visualize the environments and their applications in the GitOps Environments dashboard to track promotions and view version and details on the most recent commits that caused the change.

Here’s a visualization of Argo CD applications in the GitOps Environments dashboard.

For detailed information on how to work with Argo CD applications and Environments in Codefresh, see GitOps Environments.

GitOps Products & Argo CD applications

The Product is another custom resource from Codefresh, also enhancing application management at scale. As teams expand and applications and services multiply, keeping track of deployments across various environments can become challenging, if not unmanageable.

Instead of having to switch between applications, or switch across multiple tools to track and manage different aspects of deployments, Products allow you to group applications into cohesive units, simplifying viewing, tracking, and management. Codefresh seamlessly collates the Environments where each application in the Product is deployed, along with insights into commits, contributors, and features deployed across versions.

Here’s a visualization of Argo CD applications grouped by Products in the GitOps Products dashboard.

For detailed information on how to work with Argo CD applications and Products in Codefresh, see GitOps Products.

Edit Argo CD application definitions

Update General or Advanced configuration settings for a deployed Argo CD application through the Configuration tab. Once the application is deployed to the cluster, the Configuration tab is available on selecting the application in the GitOps Apps dashboard.

NOTE
You cannot change application definitions (the application name and the selected runtime), and the Git Source selected for the application.

How to

1. In the Codefresh UI, from Ops in the sidebar, select GitOps Apps.
2. Do one of the following:
   • Select the application to update, and then from the context menu on the right, select Edit.

• Click the application and then select the Configuration tab.

3. Update the General or Advanced configuration settings as needed:
   General configuration
   Advanced configuration
   When you change a setting, the Commit and Discard Changes buttons are displayed.

4. Do one of the following:
   • To commit all changes, click Commit. This final commit screen is displayed with a diff view of the changes.

   • To undo all changes and return to the previous settings, click Discard Changes. This action removes all the changes you have made so far and returns you to the GitOps Apps dashboard.

     TIP
     If you change settings and then restore existing values for the same, Codefresh automatically removes the Commit and Discard Changes buttons as there are no new changes to commit or discard.

5. To confirm all changes, at the bottom-left, click Commit. The changes are committed to Git, and in a few moments also synced to the cluster.

Manage Application Groups

Clicking on an Application Group in the Group tab navigates to the list of applications in the Group. You can see the collective timelines for all applications within the group, instead of the individual source, health, or target information for each application.

Once you assign an application to a group, you can add it to or remove it from different Application Groups through the application’s Configuration settings. See also Application Groups for Argo CD applications.

1. In the Codefresh UI, from Ops in the sidebar, select GitOps Apps.
2. Select the application and then click the Configuration tab.
3. From Groups, do one of the following:
   • To add the application to one or more groups, select the group or groups.
   • To remove the application from a group, click the remove button for the group.

Manually synchronize an Argo CD application

Manually synchronize an application to expedite Git-to-cluster sync. The sync options selected for manual sync override the sync options defined for the application.
The sync options, grouped into Revision and Additional Settings, are identical to the Sync options in the General settings when you created the application.

Before you begin

• Review:
  Revision settings for application sync
  Additional Options for application sync
  Synchronize resources

How to

1. In the Codefresh UI, from Ops in the sidebar, select GitOps Apps.
2. To sync an application, select the application to sync, and do one of the following:
   • From the context menu on the right, select Synchronize.
   • On the top-right, click Synchronize.
3. To sync a resource:
   • Click the application with the resource to sync.
   • In the Current State tab, open the context menu of the resource, and then select Sync.
4. Select the Revision and Additional Options for the manual sync.
   Review
5. Click Next.
6. In the Synchronize Resources form, select the scope of the manual sync:
   • To sync only specific resources, search for the resources by any part of their names, or define a Regex to filter by the required resources.
   • All: Sync all resources regardless of their sync state.
   • Out of sync: Sync only resources that are Out of sync.

Revision settings for application sync

Revision settings determine the behavior for the branch you select.

Revision The branch in Git to synchronize with the cluster.

Prune When selected, removes legacy resources from the cluster that do not exist currently in the Git branch.

Apply only When selected, syncs only those resources in the application that have been changed and are OutOfSync, instead of syncing every resource regardless of their state. This option is useful to reduce load and save time when you have thousands of resources in an application. See Selective Sync.

Dry run When selected, allows you to preview the application before changes are made to the cluster.

Force
When selected, orphans the dependents of a deleted resource during the sync operation. This option is useful to prevent

Additional Options for application sync

Sync Options

• Skip schema validation
  When selected, bypasses validating the YAML schema.
• Auto-create namespace
  When selected, automatically creates the namespace if the specified namespace does not exist in the cluster. If the namespace already exists, this setting is ignored.
• Prune last
  When selected, removes those resources that do not exist in the currently deployed version during the final wave of the sync operation. See Prune last.
• Apply out of sync only When selected, syncs only those resources in the application that have been changed and are OutOfSync, instead of syncing every resource regardless of their state. This option is useful to reduce load and save time when you have thousands of resources in an application. See Selective Sync.
• Respect ignore differences
  When selected, Argo CD omits resources defined for the spec.ignoreDifferences attribute from the sync. Otherwise, Argo CD implements the desired state ad-hoc during the sync operation. See Respect ignore difference configs.

Prune propagation policy

Defines how resources are pruned, applying Kubernetes cascading deletion prune policies. Read more at Kubernetes - Cascading deletion.

• Foreground: The default prune propagation policy used by Argo CD. With this policy, Kubernetes changes the state of the owner resource to `deletion in progress`, until the controller deletes the dependent resources and finally the owner resource itself.
• Background: When selected, Kubernetes deletes the owner resource immediately, and then deletes the dependent resources in the background.
• Orphan: When selected, Kubernetes deletes the dependent resources that remain orphaned after the owner resource is deleted.

All Prune propagation policies can be used with:

Replace: When selected, Argo CD executes kubectl replace or kubectl create, instead of the default kubectl apply to enforce the changes in Git. This action will potentially recreate resources and should be used with care. See Replace Resource Instead Of Applying Change.

Retry: When selected, retries a failed sync operation, based on the retry settings configured:

• Maximum number of sync retries (Limit)
• Duration of each retry attempt in seconds, minutes, or hours (Duration)
• Maximum duration permitted for each retry (Max Duration)
• Factor by which to multiply the Duration in the event of a failed retry (Factor). A factor of 2 for example, attempts the second retry in 2 X 2 seconds, where 2 seconds is the Duration.

Synchronize resources in the application

Synchronize Resource options allow you to selectively sync application resources. You can bypass sync settings at the application level, and directly select the resources you want to sync, by state or otherwise.

• All resources regardless of their sync states
• Only out-of-sync resources
• Only selected resources

By default, Synchronize Resources displays and selects all resources in the application.

You can search/filter resources using part of the resource names or regex strings, and then select the resources you want to sync. For example, if you made changes to api resources or audit resources, type api or audit to locate the resources and then selectively sync those resources.

Configure sync-timeout for Argo CD applications

Add an annotation with the timeout threshold for the application to get notified when an ongoing sync exceeds the defined timeout.
Codefresh uses Argo CD’s default duration of 30 minutes which you can customize as needed.

Instead of waiting indefinitely for syncs to complete and then navigating through the GitOps Apps dashboard, get timely warnings from Codefresh.

• Add the following annotation to the application’s YAML with the timeout you need:

  annotation:
  codefresh.io/app-sync-warning-threshold: "35"
  

  Codefresh displays a warning in the Warnings/Errors button at the top right of the Applications tab in the GitOps Apps dashboard, when the sync duration exceeds the timeout specified.

You can view more details on the sync or terminate it.

Terminate on-going sync for Argo CD applications

Manually terminate an on-going synchronization process for the application. You may need to terminate an on-going sync that remains indefinitely as Syncing, or because you have detected problems in the current deployment Terminating a sync operation reverts the deployment to the previously deployed version or image.

1. In the Codefresh UI, from Ops in the sidebar, select GitOps Apps.
2. If needed, filter by Status Syncing to view applications with active sync operations.
3. Select the application and then from the application header, click Terminate Sync.

Refresh/hard refresh Argo CD applications

As an alternative to manually syncing an application, either refresh or hard refresh the application. Both options are always available in the application toolbar.

1. In the Codefresh UI, from Ops in the sidebar, select GitOps Apps.
2. Select the application, and then from the top-right, select the required action:
   • Refresh: Retrieve desired (Git) state, compare with the live (cluster) state, and refresh the application to sync with the desired state.
   • Hard Refresh: Refresh the application to sync with the Git state, while removing the cache.

Rollback Argo CD applications

Rollback to a previously deployed version of active Argo CD applications. You may want to rollback a newly deployed version due to errors in your code or misconfigurations, etc.

Prerequisites for rollback

Rollback can be disabled for the following reasons:

• Auto-sync ON for applications
  If auto-sync is ON, the default behavior for GitOps is to sync the cluster with the desired state in Git. The Rollback button is disabled with a tooltip.

  For application rollback, auto-sync must be OFF. The quickest and easiest way to identify auto-sync status is through the Application Header.
  To change the setting, edit the application’s General configuration settings.

• Deployment version for rollback older than history limit
  By default, you can rollback to any the previous ten deployments (same as Argo CD). If you try to rollback to a deployment older than ten of the most recent deployments, the Rollback option is disabled with a tooltip, that the ‘Release is not in history’.

  TIP
  To configure a different number, edit the application manifest and add RevisionHistoryLimit set to the number of previous deployments you need in the spec section.

• Deleted version of application
  You can activate rollback only for new and currently active application versions that are deployed.
  If you deleted an application and then recreated it with the same name, you cannot rollback to the deleted version or to any version prior to the deletion. The Rollback button is disabled with a tooltip.

How to rollback an application

1. In the Codefresh UI, from Ops in the sidebar, select GitOps Apps.
2. Select the application to rollback and then click the Timeline tab.
3. In the Application Header, verify that Auto-sync is OFF for the application.
4. Mouse over the deployment version to rollback to view the Rollback option.

5. To start, click Rollback and confirm.
   • The ‘Rollout process started’ notification is displayed.
   • The application’s Health status changes to Progressing and the Sync status changes to out-of-sync.
   • A deployment record is created for the rollout with Progressing.

Once completed, the application’s statuses are updated.

Manage rollouts for Argo CD application deployments

Control ongoing rollouts by resuming indefinitely paused steps, promoting rollouts, aborting, restarting and retrying rollouts.

Pause/resume ongoing rollouts

Pause and resume ongoing rollouts directly from the Timeline tab in the GitOps Apps dashboard.
If the rollout is already automatically paused as result of a step definition, this action pauses the rollout even after the pause duration.

1. In the Codefresh UI, from Ops in the sidebar, select GitOps Apps.
2. Select the application and go to the Timelines tab.
3. In the deployment record for the ongoing rollout, expand Updated Services.
4. Based on the current state of the rollout, click Pause or Resume, as relevant.

Manage an ongoing rollout with the Rollout Player

Manage an ongoing rollout using the controls in the Rollout Player to skip steps, and promote rollouts.

1. In the Codefresh UI, from Ops in the sidebar, select GitOps Apps.
2. Select the application and go to the Timelines tab.
3. In the deployment record for the ongoing rollout, click the name of the rollout.
4. Select the required option in the Rollout Player.

The table describes the controls in the Rollout Player.

Rollback player option	Description
Rollback	Not available currently.
Pause	Pause the rollout. If the rollout is already automatically paused as the result of a step definition, clicking Pause pauses the rollout also after the pause duration.
Resume	Resume a rollout that was paused either manually by clicking Pause, or automatically through the step’s definition.
Skip step	Skip execution of current step. Such steps are marked as Skipped in the rollout visualization.
Promote full	Skip all remaining steps, and deploy the current image.

Manually rollback completed rollout to previous revision

Manually rollback a completed rollout to a previous revision when and if needed. If after a successful analysis run and rollout, your application is not functioning as it should, you can rollback to a prior revision from the Rollout’s revision history. The revision depth is determined by the spec.revisionHistoryLimit parameter in the Rollout Specification. Manual rollback changes the live state of the rollout resource to the state in the previous commit that you select.

1. In the Codefresh UI, from Ops in the sidebar, select GitOps Apps.
2. Select the application and select the Timeline tab.
3. Click the name of the rollout to rollback.
4. From the Choose version to Rollabck dropdown, select the revision to rollback to.
5. Review the changes in the revision.
6. In the Rollout Player, click Rollback to.

Manage the rollout resource

Control the rollout through the options available for the Rollout resource.

1. In the Codefresh UI, from Ops in the sidebar, select GitOps Apps.
2. Select the application and go to the Current State tab.
3. Open the context menu of the Rollout resource, and select the relevant option.

The table describes the options for the Rollout resource.

Option	Description
Abort	Terminate the current rollout.
Pause	Pause the current rollout.
Promote-full	Promote the current rollout by skipping all remaining stages in the rollout, and deploy the current image.
Restart	Manually restart the pods of the rollout.
Resume	Resume a rollout that has been paused.
Retry	Retry a rollout that has been aborted. Available only when a rollout has been aborted.
Skip-current-step	Skip executing the current step, and continue with the next step.

Rename an Application Set

Rename an Application Set and point all existing applications to the Application Set.

1. In the Codefresh UI, from the sidebar, select GitOps Apps.
2. Click the Git Source application with the Application Set.

3. From the Application Header, click the link in Source to go the repo in your Shared Configuration Repository.

4. In Git, open the appset.yaml, click Edit, and do the following:
   • Rename the ApplicationSet as needed.
   • Disable auto-sync by commenting out the lines with sync options.
   • Commit the changes.

5. Go back to the GitOps Apps dashboard in the Codefresh UI, and verify that the Current State tab displays the renamed ApplicationSet.
   As you can see in the picture below, the Current State tab displays the new ApplicationSet, but the applications still point to the old ApplicationSet.

6. Go to the cluster with the applications, and change Owner Reference of the existing applications to point them to the new ApplicationSet by running:

     kubectl get applications -o=json -n <namespace> | jq -r '.items[] | select(.metadata.ownerReferences[0].name == "<orginal-appset-name>") | .metadata.name' | xargs -I {} kubectl patch application {} --type="json" -p='[{"op": "replace", "path": "/metadata/ownerReferences/0/name", "value": "<new-appset-name>"}]' -n <namespace>
   

   where:

   • <namespace> is the namespace on the cluster where the applications are deployed, for example, argocd.
   • <orginal-appset-name> is the old name of the ApplicationSet, for example, "example-appset-v4".
   • <new-appset-name> is the new name of the renamed ApplicationSet, for example, "example-appset-v5".

7. Go back to the GitOps dashboard in the Codefresh UI, and in the Current State tab make sure that the applications are now linked to the renamed (new) ApplicationSet.

8. Click Synchronize and wait for the synchronization to complete.
9. Delete the old ApplicationSet, as described in Delete Argo CD applications in this article.

Delete Argo CD applications

Delete an Argo CD application from Codefresh. Deleting an application deletes the manifest from the Git repository, and then from the cluster where it is deployed. When deleted from the cluster, the application is removed from the GitOps Apps dashboard in Codefresh.

1. In the Codefresh UI, from Ops in the sidebar, select GitOps Apps.
2. Select the application to delete.
3. Click the three dots for additional actions, and select Delete.

Pay attention to the impact of the delete action for the selected application that Codefresh displays.

4. To confirm, click Commit & Delete.

Related articles

Creating Argo CD applications
Monitoring Argo CD applications
GitOps Environments dashboard
GitOps Products dashboard
Home Dashboard
DORA metrics