Skip to content

Manage GitOps with Argo CD#

Lens premium subscription feature. See details on Lens Pricing.

These are the tasks you run on a GitOps cluster during a normal working day. For the manifests behind them, see GitOps patterns with Argo CD.

Before you begin#

  • Get a Plus, Pro, or Enterprise subscription plan, or a Personal subscription with an active trial.
  • Connect a cluster with Argo CD installed. See Configure Argo CD.

Find what needs attention#

  1. In the cluster navigator, select Argo CD > Dashboard.
  2. Read the health strip for the fleet totals.
  3. Select a row under Needs attention to open that Application.

Recover a degraded Application#

A Degraded Application means the deployed resources are failing, whatever Git says.

  1. Select the Application under Needs attention.
  2. Read its conditions and images in the detail panel to confirm the cause.
  3. Right-click the Application and select Sync.
  4. Confirm that Health returns to Healthy.

Pick up a new commit#

Argo CD polls Git on an interval. After pushing a commit, refresh instead of waiting.

  1. In Argo CD > Applications, right-click the Application.
  2. Select Refresh, then choose Normal.
  3. Choose Hard instead when a normal refresh does not show the change you expect.

Sync a batch after a release#

Prune deletes resources

Leave Prune resources not in Git off unless the release intentionally removes resources. Pruning deletes live resources that no longer exist in the target revision.

  1. Open Argo CD > Dashboard.
  2. On the Applications summary card, select Sync.
  3. Review the selection. Lens K8S IDE preselects the out-of-sync Applications and lists them first.
  4. Confirm. Lens K8S IDE reports one notification covering the whole batch.

To review a GitOps rollout with our team, contact us.