Live Status

Used to show the live status of Kubernetes applications after they have been deployed.

Stable

Show details

Anatomy

Anatomy summary lists and describes all the elements within a component (including nested components).

Element	Description	Optional?
1. Container	Round container that changes color depending on the status.	No
2. Status icon	Predefined icon communicating Live Status: - Progressing: some objects are in a progressing state. - Healthy: the application desired state was achieved. - Unknown: the application has objects in an unknown state. - Degraded: desired state not achieved; the application has encountered issues. - Missing: the application has missing objects. - Status unavailable: the last deployment failed; can’t show an accurate live status for this application. - Waiting: a deployment is in progress. - Stale: no up-to-date information about the live status. - Out of Sync: desired state on the cluster is different from the desired state applied (someone made manual changes). - In Sync: desired state on the cluster matches what was last deployed. - Git Drift: the application configuration in Git does not match what Octopus last applied	No

Variants

Variants contain different versions of the component depending on specific properties, such as state, size, colour, optional iconography, etc.

LiveStatus

Property	Values	Default
size Variant	large \| medium \| small	large
healthStatus Variant	healthy \| degraded \| status unavailable \| unknown \| missing \| stale \| waiting \| progressing \| out of sync \| git drift \| in sync	healthy

LiveStatus

size large healthStatus status unavailable

Use when the last deployment failed, so we can’t show an accurate live status for this app.

LiveStatus

size medium healthStatus git drift

Use when the application configuration in Git does not match what Octopus last applied.

LiveStatus

size small healthStatus out of sync

Use when the desired state on the cluster is different from the desired state applied (someone made manual changes).

LiveStatus

size large healthStatus degraded

Use when the desired state not achieved and the application has encountered issues.

LiveStatus

size large healthStatus out of sync

Use when the desired state on the cluster is different from the desired state applied (someone made manual changes).

LiveStatus

size large healthStatus stale

Use when we don’t have up-to-date information about the live status.

LiveStatus

size medium healthStatus degraded

Use when the desired state not achieved and the application has encountered issues.

LiveStatus

size small healthStatus git drift

Use when the application configuration in Git does not match what Octopus last applied.

LiveStatus

size large healthStatus healthy

Use when the application desired state was achieved.

LiveStatus

size medium healthStatus waiting

Use when a deployment is in progress.

LiveStatus

size small healthStatus unknown

Use when the app has objects in an unknown state.

LiveStatus

size large healthStatus missing

Use when the app has missing objects.

LiveStatus

size large healthStatus waiting

Use when a deployment is in progress.

LiveStatus

size medium healthStatus progressing

Use when some objects are in a progressing state.

LiveStatus

size medium healthStatus status unavailable

Use when the last deployment failed, so we can’t show an accurate live status for this app.

LiveStatus

size small healthStatus progressing

Use when some objects are in a progressing state.

LiveStatus

size small healthStatus stale

Use when we don’t have up-to-date information about the live status.

LiveStatus

size small healthStatus status unavailable

Use when the last deployment failed, so we can’t show an accurate live status for this app.

LiveStatus

size large healthStatus git drift

Use when the application configuration in Git does not match what Octopus last applied.

LiveStatus

size large healthStatus in sync

Use when desired state on the cluster matches what was last deployed.

LiveStatus

size medium healthStatus out of sync

Use when the desired state on the cluster is different from the desired state applied (someone made manual changes).

LiveStatus

size small healthStatus waiting

Use when a deployment is in progress.

LiveStatus

size small healthStatus missing

Use when the app has missing objects.

LiveStatus

size medium healthStatus unknown

Use when the app has objects in an unknown state.

LiveStatus

size large healthStatus progressing

Use when some objects are in a progressing state.

LiveStatus

size medium healthStatus in sync

Use when desired state on the cluster matches what was last deployed.

LiveStatus

size medium healthStatus missing

Use when the app has missing objects.

LiveStatus

size medium healthStatus stale

Use when we don’t have up-to-date information about the live status.

LiveStatus

size small healthStatus degraded

Use when the desired state not achieved and the application has encountered issues.

LiveStatus

size small healthStatus healthy

Use when the application desired state was achieved.

LiveStatus

size small healthStatus in sync

Use when desired state on the cluster matches what was last deployed.

LiveStatus

size medium healthStatus healthy

Use when the application desired state was achieved.

LiveStatus

size large healthStatus unknown

Use when the app has objects in an unknown state.

Component dependencies

This component is internally dependent on the following components:

System Icons

Help and support

Ask a question or submit a request

Find us in #team-frontend-foundations-requests Slack channel

Live Status

Anatomy

Variants

Component dependencies

Help and support

Design Resources

Engineering Resources

Slack Channels