Skip to content

Commit a04b7a0

Browse files
flin-8flin-8
authored
Add stale state for live status (#3069)
1 parent 2918a06 commit a04b7a0

3 files changed

Lines changed: 76 additions & 45 deletions

File tree

‎public/docs/img/bolt-slash.svg‎

Lines changed: 1 addition & 0 deletions
Loading

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

Lines changed: 31 additions & 22 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: 2026-03-16
4+
modDate: 2026-03-19
55
navSection: Live Object Status
66
title: Argo CD Live Object Status
77
navTitle: Live Object Status
@@ -45,15 +45,16 @@ Octopus populates the Live Status Table with content taken directly from Argo.
4545

4646
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-
| 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 |
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+
| Stale | <img src="/docs/img/bolt-slash.svg" alt="stale icon" width="16px" height="16px"> | Status information is stale. No data has been received in the last 10 minutes |
5758

5859
### Project Sync Status
5960

@@ -68,18 +69,26 @@ Sync Status tracks whether the changes Octopus pushed to git still match what Ar
6869
| Unavailable | <i class="fa-solid fa-circle-exclamation red"></i> | Application sync status is unavailable because your last deployment failed |
6970
| Waiting | <i class="fa-solid fa-hourglass blue"></i> | Application sync status will be available once the deployment completes |
7071

71-
### Object status
72-
73-
| Label | Status Icon | Description |
74-
| :---------- | :-------------------------------------------: |:------------------------------------------------------------------------------------------------------------|
75-
| Progressing | <i class="fa-solid fa-circle-notch blue"></i> | Object is attempting to reach the desired state |
76-
| Healthy | <i class="fa-solid fa-heart green"></i> | Object is in sync and reporting that it is running as expected |
77-
| Unknown | <i class="fa-solid fa-question grey"></i> | We don't have information about the live status of this object |
78-
| Degraded | <i class="fa-solid fa-heart-crack red"></i> | Object has run into a problem, check the logs or events to find out more |
79-
| Out of Sync | <i class="fa-solid fa-arrow-up orange"></i> | Object manifest in the cluster is different from that specified in the Argo CD application's git repository |
80-
| Missing | <i class="fa-solid fa-ghost grey"></i> | Object is missing from the cluster |
81-
| In Sync | <i class="fa-solid fa-check green"></i> | Object manifest matches what was applied, but does not report any additional health status |
82-
| Suspended | <i class="fa-solid fa-pause grey"></i> | Job is not currently running |
72+
### Object Health Status
73+
74+
| Label | Status Icon | Description |
75+
| :---------- | :------------------------------------------------------------------------------: |:------------------------------------------------------------------------------|
76+
| Progressing | <i class="fa-solid fa-circle-notch blue"></i> | Object is attempting to reach the desired state |
77+
| Healthy | <i class="fa-solid fa-heart green"></i> | Object is in sync and reporting that it is running as expected |
78+
| Unknown | <i class="fa-solid fa-question grey"></i> | We don't have information about the live status of this object |
79+
| Degraded | <i class="fa-solid fa-heart-crack red"></i> | Object has run into a problem, check the logs or events to find out more |
80+
| Missing | <i class="fa-solid fa-ghost grey"></i> | Object is missing from the cluster |
81+
| Suspended | <i class="fa-solid fa-pause grey"></i> | Job is not currently running |
82+
| Stale | <img src="/docs/img/bolt-slash.svg" alt="stale icon" width="16px" height="16px"> | Status information is stale. No data has been received in the last 10 minutes |
83+
84+
### Object Sync Status
85+
86+
| Label | Status Icon | Description |
87+
| :---------- | :-------------------------------------------: |:-----------------------------------------------------------------------------------------------------------------------------|
88+
| In Sync | <i class="fa-solid fa-check green"></i> | Argo CD reports the object is synced and the git configuration still matches what Octopus last applied |
89+
| 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. |
90+
| 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) |
91+
| Unknown | <i class="fa-solid fa-question grey"></i> | We don't have information about the live status of this object |
8392

8493
### Detailed object information
8594

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

Lines changed: 44 additions & 23 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-19
55
navSection: Live Object Status
66
title: Kubernetes Live Object Status
77
navTitle: Overview
@@ -38,31 +38,52 @@ Octopus display individual status at an object level as well as summarized statu
3838
![Live status page](/docs/img/kubernetes/live-object-status/live-status-page.png)
3939
:::
4040

41-
### Application status
41+
### Application Health Status
42+
43+
The application health status is a roll-up of the health of all objects:
44+
45+
| Label | Status Icon | Description |
46+
| :---------- | :----------------------------------------------------------------------------------: | :-------------------------------------------------------------------------- |
47+
| Progressing | <i class="fa-solid fa-circle-notch blue"></i> | Objects in your application are currently in a progressing state |
48+
| Healthy | <i class="fa-solid fa-heart green"></i> | The objects in your cluster match what was specified in the last deployment |
49+
| Unknown | <i class="fa-solid fa-question grey"></i> | We're having trouble getting live status updates for this application |
50+
| Degraded | <i class="fa-solid fa-heart-crack red"></i> | Your objects experienced errors after the deployment completed |
51+
| Missing | <i class="fa-solid fa-ghost grey"></i> | Objects in your application are currently in a missing state |
52+
| Unavailable | <i class="fa-solid fa-circle-exclamation red"></i> | Application live status is unavailable because your last deployment failed |
53+
| Waiting | <i class="fa-solid fa-hourglass blue"></i> | Application live status will be available once the deployment completes |
54+
| Stale | <img src="/docs/img/bolt-slash.svg" alt="stale icon" width="16px" height="16px">. | Status information is stale. No data has been received in the last 10 minutes|
55+
56+
### Application Sync Status
57+
58+
Sync Status tracks whether the changes Octopus deployed still matches the resources in the cluster.
4259

4360
| Label | Status Icon | Description |
44-
| :---------- | :------------------------------------------------: | :-------------------------------------------------------------------------- |
45-
| Progressing | <i class="fa-solid fa-circle-notch blue"></i> | Objects in your application are currently in a progressing state |
46-
| Healthy | <i class="fa-solid fa-heart green"></i> | The objects in your cluster match what was specified in the last deployment |
47-
| Unknown | <i class="fa-solid fa-question grey"></i> | We're having trouble getting live status updates for this application |
48-
| Degraded | <i class="fa-solid fa-heart-crack red"></i> | Your objects experienced errors after the deployment completed |
61+
| :---------- | :------------------------------------------------: |:----------------------------------------------------------------------------|
62+
| In Sync | <i class="fa-solid fa-check green"></i> | The objects on your cluster match what you last deployed |
4963
| Out of Sync | <i class="fa-solid fa-arrow-up orange"></i> | The objects on your cluster no longer match what you last deployed |
50-
| Missing | <i class="fa-solid fa-ghost grey"></i> | Objects in your application are currently in a missing state |
51-
| Unavailable | <i class="fa-solid fa-circle-exclamation red"></i> | Application live status is unavailable because your last deployment failed |
52-
| Waiting | <i class="fa-solid fa-hourglass blue"></i> | Application live status will be available once the deployment completes |
53-
54-
### Object status
55-
56-
| Label | Status Icon | Description |
57-
| :---------- | :-------------------------------------------: | :----------------------------------------------------------------------------------------- |
58-
| Progressing | <i class="fa-solid fa-circle-notch blue"></i> | Object is attempting to reach the desired state |
59-
| Healthy | <i class="fa-solid fa-heart green"></i> | Object is in sync and reporting that it is running as expected |
60-
| Unknown | <i class="fa-solid fa-question grey"></i> | We don't have up-to-date information about the live status of this object |
61-
| Degraded | <i class="fa-solid fa-heart-crack red"></i> | Object has run into a problem, check the logs or events to find out more |
62-
| Out of Sync | <i class="fa-solid fa-arrow-up orange"></i> | Object manifest is not the same as what was applied |
63-
| Missing | <i class="fa-solid fa-ghost grey"></i> | Object is missing from the cluster |
64-
| In Sync | <i class="fa-solid fa-check green"></i> | Object manifest matches what was applied, but does not report any additional health status |
65-
| Suspended | <i class="fa-solid fa-pause grey"></i> | Job is not currently running |
64+
| Unknown | <i class="fa-solid fa-question grey"></i> | We’re having trouble getting sync status updates for this application |
65+
| Unavailable | <i class="fa-solid fa-circle-exclamation red"></i> | Application sync status is unavailable because your last deployment failed |
66+
| Waiting | <i class="fa-solid fa-hourglass blue"></i> | Application sync status will be available once the deployment completes |
67+
68+
### Object Health Status
69+
70+
| Label | Status Icon | Description |
71+
| :---------- | :-------------------------------------------------------------------------------: |:-------------------------------------------------------------------------------|
72+
| Progressing | <i class="fa-solid fa-circle-notch blue"></i> | Object is attempting to reach the desired state |
73+
| Healthy | <i class="fa-solid fa-heart green"></i> | Object is in sync and reporting that it is running as expected |
74+
| Unknown | <i class="fa-solid fa-question grey"></i> | We don't have information about the live status of this object |
75+
| Degraded | <i class="fa-solid fa-heart-crack red"></i> | Object has run into a problem, check the logs or events to find out more |
76+
| Missing | <i class="fa-solid fa-ghost grey"></i> | Object is missing from the cluster |
77+
| Suspended | <i class="fa-solid fa-pause grey"></i> | Job is not currently running |
78+
| Stale | <img src="/docs/img/bolt-slash.svg" alt="stale icon" width="16px" height="16px"> | Status information is stale. No data has been received in the last 10 minutes |
79+
80+
### Object Sync Status
81+
82+
| Label | Status Icon | Description |
83+
| :---------- | :-------------------------------------------: |:-----------------------------------------------------------------|
84+
| In Sync | <i class="fa-solid fa-check green"></i> | Object manifest matches what was applied |
85+
| Out of Sync | <i class="fa-solid fa-arrow-up orange"></i> | Object manifest is not the same as what was applied |
86+
| Unknown | <i class="fa-solid fa-question grey"></i> | We don't have information about the live status of this object |
6687

6788
Take a look at our [troubleshooting guide](/docs/kubernetes/live-object-status/troubleshooting) for details on why you may see some object statuses
6889

0 commit comments

Comments
 (0)