Skip to content

Commit 7798ce5

Browse files
sathvikkumar-octosathvikkumar-octo
authored
ArgoCD sync status updates (#3067)
* ArgoCD sync status updates * Fix lint error * PR feedback
1 parent fd699cb commit 7798ce5

File tree

2 files changed

+26
-14
lines changed

2 files changed

+26
-14
lines changed

‎public/docs/img/argo-cd/argo-cd-live-status-objects.png‎

-338 KB
Loading

‎src/pages/docs/argo-cd/live-object-status/index.md‎

Lines changed: 26 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
layout: src/layouts/Default.astro
33
pubDate: 2025-03-28
4-
modDate: 2025-05-16
4+
modDate: 2026-03-16
55
navSection: Live Object Status
66
title: Argo CD Live Object Status
77
navTitle: Live Object Status
@@ -22,7 +22,7 @@ However when used with Argo CD, neither the [Kubernetes agent](/docs/kubernetes/
2222

2323
Using Argo CD Live Object Status requires the following:
2424

25-
- Octopus Deploy 2025.4+
25+
- Octopus Deploy 2025.4+ (Sync Status requires 2026.1+)
2626
- A registered [Argo CD Instance](/docs/argo-cd/instances/)
2727
- [Annotations](/docs/argo-cd/annotations) on your Argo CD Applications, mapping them onto Octopus Deploy projects
2828
- A deployment process containing an Argo CD step (either [Update Argo CD Image Tags](/docs/argo-cd/steps/update-application-image-tags) or [Update Argo CD Application Manifests](/docs/argo-cd/steps/update-application-manifests))
@@ -41,20 +41,32 @@ Octopus populates the Live Status Table with content taken directly from Argo.
4141
![Octopus Argo CD Live Status Objects](/docs/img/argo-cd/argo-cd-live-status-objects.png)
4242
:::
4343

44-
### Project Live Status
44+
### Project Health Status
4545

46-
The project status is a roll-up of the status of all objects, in line with the following table:
46+
The project health status is a roll-up of the health of all objects:
4747

48-
| Label | Status Icon | Description |
49-
| :---------- | :------------------------------------------------: |:--------------------------------------------------------------------------------------------------------------------------|
50-
| Progressing | <i class="fa-solid fa-circle-notch blue"></i> | One or more objects of the mapped application are in a progressing state |
51-
| Healthy | <i class="fa-solid fa-heart green"></i> | The objects in the cluster match that specified in the applications' source git repositories, and are executing correctly |
52-
| Unknown | <i class="fa-solid fa-question grey"></i> | We’re having trouble getting live status updates for this application |
53-
| Degraded | <i class="fa-solid fa-heart-crack red"></i> | Your objects experienced errors after the deployment completed |
54-
| Out of Sync | <i class="fa-solid fa-arrow-up orange"></i> | Argo CD has detected differences between the application's git repository, and the manifest in the cluster. |
55-
| Missing | <i class="fa-solid fa-ghost grey"></i> | One or more desired objects are missing from the cluster |
56-
| Unavailable | <i class="fa-solid fa-circle-exclamation red"></i> | Application live status is unavailable because your last deployment failed |
57-
| Waiting | <i class="fa-solid fa-hourglass blue"></i> | Application live status will be available once the deployment completes |
48+
| Label | Status Icon | Description |
49+
| :---------- | :------------------------------------------------: |:-------------------------------------------------------------------------------------------------------------------------|
50+
| Progressing | <i class="fa-solid fa-circle-notch blue"></i> | One or more objects of the mapped application are in a progressing state |
51+
| Healthy | <i class="fa-solid fa-heart green"></i> | The objects in the cluster match that specified in the applications’ source git repositories, and are executing correctly|
52+
| Unknown | <i class="fa-solid fa-question grey"></i> | We’re having trouble getting live status updates for this application |
53+
| Degraded | <i class="fa-solid fa-heart-crack red"></i> | Your objects experienced errors after the deployment completed |
54+
| Missing | <i class="fa-solid fa-ghost grey"></i> | One or more desired objects are missing from the cluster |
55+
| Unavailable | <i class="fa-solid fa-circle-exclamation red"></i> | Application live status is unavailable because your last deployment failed |
56+
| Waiting | <i class="fa-solid fa-hourglass blue"></i> | Application live status will be available once the deployment completes |
57+
58+
### Project Sync Status
59+
60+
Sync Status tracks whether the changes Octopus pushed to git still match what Argo CD has synced. Octopus recalculates this after each deployment and whenever Argo CD reports a sync event.
61+
62+
| Label | Status Icon | Description |
63+
| :---------- | :------------------------------------------------: |:-----------------------------------------------------------------------------------------------------------------------------|
64+
| In Sync | <i class="fa-solid fa-check green"></i> | Argo CD reports the application is synced and the git configuration still matches what Octopus last applied |
65+
| Out of Sync | <i class="fa-solid fa-arrow-up orange"></i> | Argo CD has detected that the desired state in the cluster differs from the application’s git repository |
66+
| Git Drift | <i class="fa-solid fa-not-equal orange"></i> | Octopus has detected that the changes it applied to git have been modified since the last deployment (e.g. by a manual edit) |
67+
| Unknown | <i class="fa-solid fa-question grey"></i> | We’re having trouble getting sync status updates for this application |
68+
| Unavailable | <i class="fa-solid fa-circle-exclamation red"></i> | Application sync status is unavailable because your last deployment failed |
69+
| Waiting | <i class="fa-solid fa-hourglass blue"></i> | Application sync status will be available once the deployment completes |
5870

5971
### Object status
6072

0 commit comments

Comments
 (0)