ACS Pods expose custom status conditions that report creation progress, sandbox health, and resource-resizing state. This reference covers pods with general-purpose and performance computing types. Use it to identify what a condition value means and what action to take.
How to read the condition tables
Each condition entry contains two key fields:
| Field | Type | Example |
|---|---|---|
reason |
Machine-readable string. Matches the exact value returned by the Kubernetes API. | NoStock |
message |
Human-readable text. May contain a dynamic placeholder %s replaced with context-specific details at runtime. |
Create failed because the specified instance is out of stock. cn-hangzhou |
Conditions at a glance
| Condition | What it tracks |
|---|---|
| ContainerInstanceCreated | Pod creation status |
| SandboxReady | Sandbox availability and active O&M events |
| InPlacePodResourceResizing | Vertical Pod Autoscaler (VPA) upgrade and downgrade progress |
ContainerInstanceCreated
ContainerInstanceCreated reports the creation status of an ACS Pod.
reason |
message |
What it means | Action |
|---|---|---|---|
Creating |
Creating |
The ACS Pod is being created. | Wait for creation to complete. |
StockExhaust |
The stock of the specified zones will be used up. %s |
Computing resources in the current zone are nearly depleted. | Switch to another zone. |
NoStock |
Create failed because the specified instance is out of stock. %s |
Computing resources in the current zone are insufficient. | Create ACS Pods across multiple zones and with multiple specifications to increase the success rate. |
StockClose |
Create failed because current zone closed or limited without living instance. %s |
The current zone is unavailable. | Select another zone. |
FailedScheduling |
Unknown error occurred. |
Pod scheduling failed due to an unknown error. | Submit a ticket. |
FailedScheduling |
Schedule failed:%s |
Pod scheduling failed. | Try again. |
UnknownError |
The service is under heavy load while creating container group resources, please wait and try again later |
The ACS service is under heavy load. | Try again later. |
DiskCapacityQuotaFull |
Your disk capacity quota is exceeded |
Disk capacity has reached its quota limit. | Go to Quota Center to request a quota increase. |
UnknownError |
An unknown error occurred for %s |
An unknown error occurred. | Submit a ticket. |
SystemFailureReboot |
The Specified ContainerGroup is rebooting |
The ACS Pod is restarting. | Wait for the restart to complete. |
Throttling |
The request was denied due to system flow control, please wait and try again later |
The request was denied due to traffic throttling. | Try again later. |
SandboxReady
SandboxReady reports sandbox availability. A non-empty reason indicates an active O&M event. The message field contains the system event message.
reason |
message |
What it means |
|---|---|---|
SystemFailure.Reboot |
%s |
The ACS Pod restarted due to a system error. |
InstanceFailure.Reboot |
%s |
The ACS Pod restarted due to an operating system error. |
SystemFailure.Redeploy |
%s |
The ACS Pod was redeployed due to a system error. |
InPlacePodResourceResizing
InPlacePodResourceResizing tracks progress during a VPA upgrade or downgrade. In the message field, version is the resize request version and message is supplementary information.
reason |
message |
What it means | Action |
|---|---|---|---|
ResizingInProgress |
{"version":"%s","message":"%s"} |
The upgrade or downgrade request was accepted and is in progress. | Wait for the operation to complete. |
ResizingFailed |
{"version":"%s","message":"timeout"} |
The upgrade or downgrade operation timed out. | Retry the resize request. |
ResizingFailed |
{"version":"%s","message":"vm hot modify failed |
The VM-level upgrade or downgrade operation failed. | — |
ResizingSucceeded |
{"version":"%s","message":"%s"} |
The upgrade or downgrade operation succeeded. | No action required. |
该文章对您有帮助吗？