This topic tells you how to monitor Space readiness for hosting applications on Tanzu Platform for Kubernetes.
The Space status provides actionable feedback through improved status indicators to help with debugging. Monitoring Space readiness helps make Spaces easier to manage and more consistently ready to host applications.
Status | Conditions Met |
---|---|
Pending | The back-end system has not yet detected the Space for scheduling. Constraints on back-end resources might delay detecting the Space for scheduling. |
Not Ready | The Traits, Profiles, or Availability Target in the Space are not found or not ready. The replicas created for the Space are not scheduled. |
Ready | All replicas are scheduled. The Space is scheduled on the resolved clusters. The Traits are installed. |
Deleting | The Space and its resources, including the Availability Target, Profiles, and Traits, are being deleted. |
To view the status within Tanzu Platform hub, go to Application Spaces > Spaces > Recent Spaces.
To view the status within the CLI, run:
tanzu space get <space-name>
For example:
$ tanzu space get ingress-tls-3
📡 Overview
name: ingress-tls-3
description: <empty>
status: Not Ready
replicas: 1/1
update strategy: Recreate
last updated: 10m ago
The following sections describe the statuses in more detail.
Pending
is a system-generated status. that shows that the back-end system has not detected the Space yet. Constraints on back-end resources might delay detecting the Space for scheduling.
Pending
appears when a Space was created with a manifest YAML file, by using the upload manifest workflow or guided workflow, and the back-end system has not detected the Space yet for scheduling criteria.
Various issues can cause the Not Ready
status and these are described in the following sections.
The Space was created with a manifest YAML file by using the upload manifest workflow, and the Profile within the spec
section of the YAML file was not found. The error message displayed in Tanzu Platform hub is Profile <name> not found
.
A Profile was created by using the upload manifest YAML workflow, and a Trait name in the spec
section of the YAML file does not exist. A platform engineer used the step-by-step workflow to create a Space by using the non-resolved Profile from the drop-down menu.
The error message displayed in Tanzu Platform hub is Profile <profile-name> not ready and unable to find trait <trait-name>
.
A Space was created by using a Space YAML manifest file, and an Availability Target name in the spec
section of the YAML file does not exist. The error message displayed in Tanzu Platform hub is Unable to find Availability Target <availability-target-name>
.
An Availability Target was created by the guided workflow, and a key-value pair does not exist or a selected region in the Cluster Match Expressions drop-down menu does not exist. The error message displayed in Tanzu Platform hub is Availability Target <availability-target-name> is not ready
.
The replicas requested as part of Space creation are not scheduled. Typically this is because clusters are not available or have run out of resources.
In the Recent Spaces section in Tanzu Platform hub you can count actual and requested replicas resolved in a Space, with respect to each Availability Target where they are deployed. The Space status is Not Ready
and the replica count is not colored green.
All replicas requested as part of Space creation are scheduled.
In the Recent Spaces section in Tanzu Platform hub, the count of actual replicas matches the count of requested replicas. The Space health status is green.
Within the CLI, if you run:
tanzu space list <space-name>
Output similar to the following appears:
NAME STATUS PROFILES RESOLVED REPLICAS AGE
ingress-tls-3 READY 2/2 1/1 3h47m
To see the Deleting
status:
Deleting
and there is a message is Deletion In Progress
message. The Profile, Availability Target, and replicas for the Space appear in gray while deletion is in progress.