Skip to main content

Viewing Status Details

This topic describes how to view the status of an application on the Replicated admin console dashboard. It also describes how Replicated KOTS collects and aggregates the application status.

View Status Details

The application status displays on the dashboard of the admin console. Viewing the status details can be helpful for troubleshooting.

There are two ways to view the status details, depending on your admin console version:

  • (Version 1.51.0 and later) Click Details next to the status on the dashboard. For information about how to update the admin console to view the Details link, see Updating KOTS.

    Status Details

  • (Version 1.50.2 and earlier) Review the diagnostic information in kots/admin_console/kotsadm-/kotsadm.log in the support bundle. For more information about generating a support bundle, see Generating Support Bundles.

About Application Status

To display application status on the admin console dashboard, KOTS aggregates the status of specific Kubernetes resources for the application.

The following resource types are supported for displaying application status:

  • Deployment
  • StatefulSet
  • Service
  • Ingress
  • PersistentVolumeClaims (PVC)
  • DaemonSet

Applications can specify one or more of the supported Kubernetes workloads listed above. KOTS watches all specified workloads for state changes.

For more information about how to interpret the application status displayed on the admin console dashboard, see Resource Statuses and Aggregate Application Status below.

Resource Statuses

Possible application statuses are Ready, Updating, Degraded, Unavailable, and Missing.

The following table lists the supported Kubernetes resources and the conditions that contribute to each status:

ReadyReady replicas equals desired replicasReady replicas equals desired replicasAll desired endpoints are ready, any load balancers have been assignedAll desired backend service endpoints are ready, any load balancers have been assignedClaim is boundReady daemon pods equals desired scheduled daemon pods
UpdatingThe deployed replicas are from a different revisionThe deployed replicas are from a different revisionN/AN/AN/AThe deployed daemon pods are from a different revision
DegradedAt least 1 replica is ready, but more are desiredAt least 1 replica is ready, but more are desiredAt least one endpoint is ready, but more are desiredAt least one backend service endpoint is ready, but more are desiredN/AAt least one daemon pod is ready, but more are desired
UnavailableNo replicas are readyNo replicas are readyNo endpoints are ready, no load balancer has been assignedNo backend service endpoints are ready, no load balancer has been assignedClaim is pending or lostNo daemon pods are ready
MissingMissing is an initial deployment status indicating that informers have not reported their status because the application has just been deployed and the underlying resource has not been created yet. After the resource is created, the status changes. However, if a resource changes from another status to Missing, then the resource was either deleted or the informers failed to report a status.

Aggregate Application Status

When you provide more than one Kubernetes resource, Replicated aggregates all resource statuses to display a single application status.

Replicated uses the least available resource status to represent the aggregate application status. For example, if at least one resource has an Unavailable status, then the aggregate application status is Unavailable.

The following table describes the resource statuses that define each aggregate application status:

Resource StatusesAggregate Application Status
No status available for any resourceMissing
One or more resources UnavailableUnavailable
One or more resources DegradedDegraded
One or more resources UpdatingUpdating
All resources ReadyReady