Conditions of Elastic Container Instance-based pods - Elastic Container Instance

ECI-based pods expose two custom conditions — ContainerInstanceCreated and SandboxReady — in addition to the standard Kubernetes pod conditions. Each condition includes a reason field and a message field that describe what is happening or what went wrong.

Field	Format	Purpose
`reason`	UpperCamelCase (machine-readable)	Identifies the specific event or error. Use this field when writing monitoring alerts or automation scripts.
`message`	Human-readable string	Provides detail about the event. Some messages contain a `%s` placeholder that the system replaces at runtime with context-specific information, such as a zone name, instance type, or error detail.

View pod conditions

Run the following command to inspect the conditions of an ECI-based pod:

kubectl describe pod <pod-name>

Look for the Conditions section in the output. For example:

Conditions:
  Type                     Status
  ContainerInstanceCreated True
  SandboxReady             True
  Initialized              True
  Ready                    True
  ContainersReady          True
  PodScheduled             True

To retrieve a specific condition programmatically:

kubectl get pod <pod-name> -o jsonpath='{.status.conditions[?(@.type=="ContainerInstanceCreated")]}'

ContainerInstanceCreated

The ContainerInstanceCreated condition describes the creation status of a pod. The following table lists the reasons and their meanings.

Reasons marked with [Preemptible only] apply exclusively to preemptible instances.

Reason	Message	Description
`Creating`	`Creating`	The pod is being created. No action required.
`StockExhaust`	`The stock of the specified zones will be used up. %s`	Resources in the current zone are almost exhausted. Select another zone.
`NoStock`	`Create ECI failed because the specified instance is out of stock. %s`	The current zone has insufficient resources. Configure multiple zones and multiple instance types to improve the success rate.
`StockClose`	`Create ECI failed because current zone closed or limited without living instance. %s`	The current zone is unavailable. Select another zone.
`FailedScheduling`	`Unknown error occurred.`	Scheduling failed due to an unknown error. Submit a ticket to resolve the issue.
`FailedScheduling`	`Schedule eci failed:%s`	Scheduling failed. Retry the operation.
`UnknownError`	`The ECI service is under heavy load while creating container group resources, please wait and try again later`	The Elastic Container Instance service is overloaded. Retry later.
`SpotToBeReleased`	`Spot ECI will be released in %s minutes`	[Preemptible only] The preemptible instance is about to expire. Handle this event in your application immediately.
`DiskCapacityQuotaFull`	`Your disk capacity quota is exceeded`	Disk capacity has reached the quota limit. Apply for a quota increase in the Quota Center console.
`UnknownError`	`An unknown error occurred for %s`	An unknown error occurred. Submit a ticket to resolve the issue.
`CpuOptionsNotSupported`	`The cpu options is not supported for your instanceType[%s] in current region`	The instance type does not support custom CPU options in this zone. Select an instance type that supports custom CPU options.
`CpuOptionsNotValid`	`The cpu options is not valid for your instanceType[%s]`	The specified CPU options are invalid for this instance type. Correct the CPU option configuration.
`SystemFailureReboot`	`The Specified ContainerGroup is rebooting`	The pod is restarting due to a system event. No action required.
`SystemReboot`	`It is strongly recommended that you re-create this instance within 48 hours because of %s, otherwise, the pod will be forced to restart.`	Re-create the pod within 48 hours. If you do not, the system forces a restart.
`Throttling`	`The request was denied due to system flow control, please wait and try again later`	The request was rejected due to throttling. Retry later.
`SpotDegraded`	`Spot [%s] will be degraded because the specified instance is out of stock`	[Preemptible only] No preemptible inventory is available. The system automatically creates a pay-as-you-go instance instead.
`AutoInstanceTypeMatch`	`The most-matched instanceType for current eci instance is %s`	The system adjusted the pod specifications upward.
`MultiZoneRecommendations`	`%s`	Configure multiple zones to improve pod creation reliability.

SandboxReady

The SandboxReady condition describes the availability of the sandbox runtime. In this condition, reason indicates an active O&M event and message contains the system event detail.

Reason	Message	Description
`SystemFailure.Reboot`	`%s`	The pod restarted due to a system error. Check system logs for details.
`InstanceFailure.Reboot`	`%s`	The pod restarted due to an operating system error. Check instance logs for details.
`SystemFailure.Redeploy`	`%s`	The pod was redeployed due to a system error. Verify that the pod is running correctly after redeployment.