From a99ec4ed756c3ce131d3b3bc9caf8f80e531bd67 Mon Sep 17 00:00:00 2001 From: Frank Lin Date: Wed, 18 Mar 2026 21:47:23 +1000 Subject: [PATCH 1/6] Add "Stale" to Argo CD live status and also split object sync status table --- .../docs/argo-cd/live-object-status/index.md | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/src/pages/docs/argo-cd/live-object-status/index.md b/src/pages/docs/argo-cd/live-object-status/index.md index 6f3156a982..8248baa451 100644 --- a/src/pages/docs/argo-cd/live-object-status/index.md +++ b/src/pages/docs/argo-cd/live-object-status/index.md @@ -54,6 +54,7 @@ The project health status is a roll-up of the health of all objects: | Missing | | One or more desired objects are missing from the cluster | | Unavailable | | Application live status is unavailable because your last deployment failed | | Waiting | | Application live status will be available once the deployment completes | +| Stale | | Status information is stale. No data has been received in the last 10 minutes | ### Project Sync Status @@ -68,7 +69,7 @@ Sync Status tracks whether the changes Octopus pushed to git still match what Ar | Unavailable | | Application sync status is unavailable because your last deployment failed | | Waiting | | Application sync status will be available once the deployment completes | -### Object status +### Object Health Status | Label | Status Icon | Description | | :---------- | :-------------------------------------------: |:------------------------------------------------------------------------------------------------------------| @@ -76,10 +77,18 @@ Sync Status tracks whether the changes Octopus pushed to git still match what Ar | Healthy | | Object is in sync and reporting that it is running as expected | | Unknown | | We don't have information about the live status of this object | | Degraded | | Object has run into a problem, check the logs or events to find out more | -| Out of Sync | | Object manifest in the cluster is different from that specified in the Argo CD application's git repository | | Missing | | Object is missing from the cluster | -| In Sync | | Object manifest matches what was applied, but does not report any additional health status | | Suspended | | Job is not currently running | +| Stale | | Status information is stale. No data has been received in the last 10 minutes | + +### Object Sync Status + +| Label | Status Icon | Description | +| :---------- | :-------------------------------------------: |:------------------------------------------------------------------------------------------------------------| +| In Sync | | Argo CD reports the object is synced and the git configuration still matches what Octopus last applied | +| Out of Sync | | Argo CD has detected that the desired state in the cluster differs from the application’s git repository. | +| Git Drift | | Octopus has detected that the changes it applied to git have been modified since the last deployment (e.g. by a manual edit) | +| Unknown | | We don't have information about the live status of this object | ### Detailed object information From 62f9f2606f9403982df217ea6709c69ed548c293 Mon Sep 17 00:00:00 2001 From: Frank Lin Date: Thu, 19 Mar 2026 10:30:57 +1000 Subject: [PATCH 2/6] Add bolt slash svg --- public/docs/img/bolt-slash.svg | 1 + src/pages/docs/argo-cd/live-object-status/index.md | 4 ++-- 2 files changed, 3 insertions(+), 2 deletions(-) create mode 100644 public/docs/img/bolt-slash.svg diff --git a/public/docs/img/bolt-slash.svg b/public/docs/img/bolt-slash.svg new file mode 100644 index 0000000000..80ca5829b9 --- /dev/null +++ b/public/docs/img/bolt-slash.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/src/pages/docs/argo-cd/live-object-status/index.md b/src/pages/docs/argo-cd/live-object-status/index.md index 8248baa451..689816851d 100644 --- a/src/pages/docs/argo-cd/live-object-status/index.md +++ b/src/pages/docs/argo-cd/live-object-status/index.md @@ -54,7 +54,7 @@ The project health status is a roll-up of the health of all objects: | Missing | | One or more desired objects are missing from the cluster | | Unavailable | | Application live status is unavailable because your last deployment failed | | Waiting | | Application live status will be available once the deployment completes | -| Stale | | Status information is stale. No data has been received in the last 10 minutes | +| Stale | | Status information is stale. No data has been received in the last 10 minutes | ### Project Sync Status @@ -79,7 +79,7 @@ Sync Status tracks whether the changes Octopus pushed to git still match what Ar | Degraded | | Object has run into a problem, check the logs or events to find out more | | Missing | | Object is missing from the cluster | | Suspended | | Job is not currently running | -| Stale | | Status information is stale. No data has been received in the last 10 minutes | +| Stale | | Status information is stale. No data has been received in the last 10 minutes | ### Object Sync Status From 07a86f425b024c92c0e9f1630378683ba487e77a Mon Sep 17 00:00:00 2001 From: Frank Lin Date: Thu, 19 Mar 2026 10:43:02 +1000 Subject: [PATCH 3/6] Add stale to K8s live status and split object health/sync status table --- .../kubernetes/live-object-status/index.md | 46 ++++++++++++++----- 1 file changed, 34 insertions(+), 12 deletions(-) diff --git a/src/pages/docs/kubernetes/live-object-status/index.md b/src/pages/docs/kubernetes/live-object-status/index.md index 0b48e58108..85cdda0171 100644 --- a/src/pages/docs/kubernetes/live-object-status/index.md +++ b/src/pages/docs/kubernetes/live-object-status/index.md @@ -38,7 +38,10 @@ Octopus display individual status at an object level as well as summarized statu ![Live status page](/docs/img/kubernetes/live-object-status/live-status-page.png) ::: -### Application status +### Application Health Status + +The application health status is a roll-up of the health of all objects: + | Label | Status Icon | Description | | :---------- | :------------------------------------------------: | :-------------------------------------------------------------------------- | @@ -46,23 +49,42 @@ Octopus display individual status at an object level as well as summarized statu | Healthy | | The objects in your cluster match what was specified in the last deployment | | Unknown | | We're having trouble getting live status updates for this application | | Degraded | | Your objects experienced errors after the deployment completed | -| Out of Sync | | The objects on your cluster no longer match what you last deployed | | Missing | | Objects in your application are currently in a missing state | | Unavailable | | Application live status is unavailable because your last deployment failed | | Waiting | | Application live status will be available once the deployment completes | +| Stale | | Status information is stale. No data has been received in the last 10 minutes | -### Object status +### Application Sync Status -| Label | Status Icon | Description | -| :---------- | :-------------------------------------------: | :----------------------------------------------------------------------------------------- | -| Progressing | | Object is attempting to reach the desired state | -| Healthy | | Object is in sync and reporting that it is running as expected | -| Unknown | | We don't have up-to-date information about the live status of this object | -| Degraded | | Object has run into a problem, check the logs or events to find out more | +Sync Status tracks whether the changes Octopus deployed still matches the resources in the cluster. + +| Label | Status Icon | Description | +| :---------- | :------------------------------------------------: |:-----------------------------------------------------------------------------------------------------------------------------| +| In Sync | | The objects on your cluster match what you last deployed | +| Out of Sync | | The objects on your cluster no longer match what you last deployed | +| Unknown | | We’re having trouble getting sync status updates for this application | +| Unavailable | | Application sync status is unavailable because your last deployment failed | +| Waiting | | Application sync status will be available once the deployment completes + +### Object Health Status + +| Label | Status Icon | Description | +| :---------- | :-------------------------------------------: |:------------------------------------------------------------------------------------------------------------| +| Progressing | | Object is attempting to reach the desired state | +| Healthy | | Object is in sync and reporting that it is running as expected | +| Unknown | | We don't have information about the live status of this object | +| Degraded | | Object has run into a problem, check the logs or events to find out more | +| Missing | | Object is missing from the cluster | +| Suspended | | Job is not currently running | +| Stale | | Status information is stale. No data has been received in the last 10 minutes | + +### Object Sync Status + +| Label | Status Icon | Description | +| :---------- | :-------------------------------------------: |:------------------------------------------------------------------------------------------------------------| +| In Sync | | Object manifest matches what was applied | | Out of Sync | | Object manifest is not the same as what was applied | -| Missing | | Object is missing from the cluster | -| In Sync | | Object manifest matches what was applied, but does not report any additional health status | -| Suspended | | Job is not currently running | +| Unknown | | We don't have information about the live status of this object | Take a look at our [troubleshooting guide](/docs/kubernetes/live-object-status/troubleshooting) for details on why you may see some object statuses From b164fdb558fa319979e5d2416926085a11164c9b Mon Sep 17 00:00:00 2001 From: Frank Lin Date: Thu, 19 Mar 2026 21:03:59 +1000 Subject: [PATCH 4/6] lint --- .../docs/argo-cd/live-object-status/index.md | 32 +++++----- .../kubernetes/live-object-status/index.md | 61 +++++++++---------- 2 files changed, 46 insertions(+), 47 deletions(-) diff --git a/src/pages/docs/argo-cd/live-object-status/index.md b/src/pages/docs/argo-cd/live-object-status/index.md index 689816851d..59bae9ee6f 100644 --- a/src/pages/docs/argo-cd/live-object-status/index.md +++ b/src/pages/docs/argo-cd/live-object-status/index.md @@ -45,16 +45,16 @@ Octopus populates the Live Status Table with content taken directly from Argo. The project health status is a roll-up of the health of all objects: -| Label | Status Icon | Description | -| :---------- | :------------------------------------------------: |:-------------------------------------------------------------------------------------------------------------------------| -| Progressing | | One or more objects of the mapped application are in a progressing state | -| Healthy | | The objects in the cluster match that specified in the applications’ source git repositories, and are executing correctly| -| Unknown | | We’re having trouble getting live status updates for this application | -| Degraded | | Your objects experienced errors after the deployment completed | -| Missing | | One or more desired objects are missing from the cluster | -| Unavailable | | Application live status is unavailable because your last deployment failed | -| Waiting | | Application live status will be available once the deployment completes | -| Stale | | Status information is stale. No data has been received in the last 10 minutes | +| Label | Status Icon | Description | +| :---------- | :------------------------------------------------------------------------------: |:-------------------------------------------------------------------------------------------------------------------------| +| Progressing | | One or more objects of the mapped application are in a progressing state | +| Healthy | | The objects in the cluster match that specified in the applications’ source git repositories, and are executing correctly| +| Unknown | | We’re having trouble getting live status updates for this application | +| Degraded | | Your objects experienced errors after the deployment completed | +| Missing | | One or more desired objects are missing from the cluster | +| Unavailable | | Application live status is unavailable because your last deployment failed | +| Waiting | | Application live status will be available once the deployment completes | +| Stale | stale icon | Status information is stale. No data has been received in the last 10 minutes | ### Project Sync Status @@ -79,16 +79,16 @@ Sync Status tracks whether the changes Octopus pushed to git still match what Ar | Degraded | | Object has run into a problem, check the logs or events to find out more | | Missing | | Object is missing from the cluster | | Suspended | | Job is not currently running | -| Stale | | Status information is stale. No data has been received in the last 10 minutes | +| Stale | stale icon | Status information is stale. No data has been received in the last 10 minutes | ### Object Sync Status -| Label | Status Icon | Description | -| :---------- | :-------------------------------------------: |:------------------------------------------------------------------------------------------------------------| -| In Sync | | Argo CD reports the object is synced and the git configuration still matches what Octopus last applied | -| Out of Sync | | Argo CD has detected that the desired state in the cluster differs from the application’s git repository. | +| Label | Status Icon | Description | +| :---------- | :-------------------------------------------: |:-----------------------------------------------------------------------------------------------------------------------------| +| In Sync | | Argo CD reports the object is synced and the git configuration still matches what Octopus last applied | +| Out of Sync | | Argo CD has detected that the desired state in the cluster differs from the application’s git repository. | | Git Drift | | Octopus has detected that the changes it applied to git have been modified since the last deployment (e.g. by a manual edit) | -| Unknown | | We don't have information about the live status of this object | +| Unknown | | We don't have information about the live status of this object | ### Detailed object information diff --git a/src/pages/docs/kubernetes/live-object-status/index.md b/src/pages/docs/kubernetes/live-object-status/index.md index 85cdda0171..ebce94ef50 100644 --- a/src/pages/docs/kubernetes/live-object-status/index.md +++ b/src/pages/docs/kubernetes/live-object-status/index.md @@ -42,49 +42,48 @@ Octopus display individual status at an object level as well as summarized statu The application health status is a roll-up of the health of all objects: - -| Label | Status Icon | Description | -| :---------- | :------------------------------------------------: | :-------------------------------------------------------------------------- | -| Progressing | | Objects in your application are currently in a progressing state | -| Healthy | | The objects in your cluster match what was specified in the last deployment | -| Unknown | | We're having trouble getting live status updates for this application | -| Degraded | | Your objects experienced errors after the deployment completed | -| Missing | | Objects in your application are currently in a missing state | -| Unavailable | | Application live status is unavailable because your last deployment failed | -| Waiting | | Application live status will be available once the deployment completes | -| Stale | | Status information is stale. No data has been received in the last 10 minutes | +| Label | Status Icon | Description | +| :---------- | :----------------------------------------------------------------------------------: | :-------------------------------------------------------------------------- | +| Progressing | | Objects in your application are currently in a progressing state | +| Healthy | | The objects in your cluster match what was specified in the last deployment | +| Unknown | | We're having trouble getting live status updates for this application | +| Degraded | | Your objects experienced errors after the deployment completed | +| Missing | | Objects in your application are currently in a missing state | +| Unavailable | | Application live status is unavailable because your last deployment failed | +| Waiting | | Application live status will be available once the deployment completes | +| Stale | stale icon. | Status information is stale. No data has been received in the last 10 minutes| ### Application Sync Status Sync Status tracks whether the changes Octopus deployed still matches the resources in the cluster. -| Label | Status Icon | Description | -| :---------- | :------------------------------------------------: |:-----------------------------------------------------------------------------------------------------------------------------| -| In Sync | | The objects on your cluster match what you last deployed | +| Label | Status Icon | Description | +| :---------- | :------------------------------------------------: |:----------------------------------------------------------------------------| +| In Sync | | The objects on your cluster match what you last deployed | | Out of Sync | | The objects on your cluster no longer match what you last deployed | -| Unknown | | We’re having trouble getting sync status updates for this application | -| Unavailable | | Application sync status is unavailable because your last deployment failed | -| Waiting | | Application sync status will be available once the deployment completes +| Unknown | | We’re having trouble getting sync status updates for this application | +| Unavailable | | Application sync status is unavailable because your last deployment failed | +| Waiting | | Application sync status will be available once the deployment completes | ### Object Health Status -| Label | Status Icon | Description | -| :---------- | :-------------------------------------------: |:------------------------------------------------------------------------------------------------------------| -| Progressing | | Object is attempting to reach the desired state | -| Healthy | | Object is in sync and reporting that it is running as expected | -| Unknown | | We don't have information about the live status of this object | -| Degraded | | Object has run into a problem, check the logs or events to find out more | -| Missing | | Object is missing from the cluster | -| Suspended | | Job is not currently running | -| Stale | | Status information is stale. No data has been received in the last 10 minutes | +| Label | Status Icon | Description | +| :---------- | :-------------------------------------------------------------------------------: |:-------------------------------------------------------------------------------| +| Progressing | | Object is attempting to reach the desired state | +| Healthy | | Object is in sync and reporting that it is running as expected | +| Unknown | | We don't have information about the live status of this object | +| Degraded | | Object has run into a problem, check the logs or events to find out more | +| Missing | | Object is missing from the cluster | +| Suspended | | Job is not currently running | +| Stale | stale icon | Status information is stale. No data has been received in the last 10 minutes | ### Object Sync Status -| Label | Status Icon | Description | -| :---------- | :-------------------------------------------: |:------------------------------------------------------------------------------------------------------------| -| In Sync | | Object manifest matches what was applied | -| Out of Sync | | Object manifest is not the same as what was applied | -| Unknown | | We don't have information about the live status of this object | +| Label | Status Icon | Description | +| :---------- | :-------------------------------------------: |:-----------------------------------------------------------------| +| In Sync | | Object manifest matches what was applied | +| Out of Sync | | Object manifest is not the same as what was applied | +| Unknown | | We don't have information about the live status of this object | Take a look at our [troubleshooting guide](/docs/kubernetes/live-object-status/troubleshooting) for details on why you may see some object statuses From 4856e1d4c1a7675d490d600da276c237986a853a Mon Sep 17 00:00:00 2001 From: Frank Lin Date: Thu, 19 Mar 2026 21:17:39 +1000 Subject: [PATCH 5/6] more lint --- .../docs/argo-cd/live-object-status/index.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/src/pages/docs/argo-cd/live-object-status/index.md b/src/pages/docs/argo-cd/live-object-status/index.md index 59bae9ee6f..a8f214873e 100644 --- a/src/pages/docs/argo-cd/live-object-status/index.md +++ b/src/pages/docs/argo-cd/live-object-status/index.md @@ -71,15 +71,15 @@ Sync Status tracks whether the changes Octopus pushed to git still match what Ar ### Object Health Status -| Label | Status Icon | Description | -| :---------- | :-------------------------------------------: |:------------------------------------------------------------------------------------------------------------| -| Progressing | | Object is attempting to reach the desired state | -| Healthy | | Object is in sync and reporting that it is running as expected | -| Unknown | | We don't have information about the live status of this object | -| Degraded | | Object has run into a problem, check the logs or events to find out more | -| Missing | | Object is missing from the cluster | -| Suspended | | Job is not currently running | -| Stale | stale icon | Status information is stale. No data has been received in the last 10 minutes | +| Label | Status Icon | Description | +| :---------- | :------------------------------------------------------------------------------: |:------------------------------------------------------------------------------| +| Progressing | | Object is attempting to reach the desired state | +| Healthy | | Object is in sync and reporting that it is running as expected | +| Unknown | | We don't have information about the live status of this object | +| Degraded | | Object has run into a problem, check the logs or events to find out more | +| Missing | | Object is missing from the cluster | +| Suspended | | Job is not currently running | +| Stale | stale icon | Status information is stale. No data has been received in the last 10 minutes | ### Object Sync Status From 1016cf2c2cc2009fd5f66b1f6bab27bc28c918b4 Mon Sep 17 00:00:00 2001 From: Frank Lin Date: Thu, 19 Mar 2026 21:18:07 +1000 Subject: [PATCH 6/6] mod date --- src/pages/docs/argo-cd/live-object-status/index.md | 2 +- src/pages/docs/kubernetes/live-object-status/index.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/pages/docs/argo-cd/live-object-status/index.md b/src/pages/docs/argo-cd/live-object-status/index.md index a8f214873e..5b3a29f4ea 100644 --- a/src/pages/docs/argo-cd/live-object-status/index.md +++ b/src/pages/docs/argo-cd/live-object-status/index.md @@ -1,7 +1,7 @@ --- layout: src/layouts/Default.astro pubDate: 2025-03-28 -modDate: 2026-03-16 +modDate: 2026-03-19 navSection: Live Object Status title: Argo CD Live Object Status navTitle: Live Object Status diff --git a/src/pages/docs/kubernetes/live-object-status/index.md b/src/pages/docs/kubernetes/live-object-status/index.md index ebce94ef50..2b08a0a755 100644 --- a/src/pages/docs/kubernetes/live-object-status/index.md +++ b/src/pages/docs/kubernetes/live-object-status/index.md @@ -1,7 +1,7 @@ --- layout: src/layouts/Default.astro pubDate: 2025-03-28 -modDate: 2025-05-16 +modDate: 2026-03-19 navSection: Live Object Status title: Kubernetes Live Object Status navTitle: Overview