Container Service for Kubernetes (ACK) periodically detects the status of an ACK cluster. If the cluster meets specific anomaly conditions, the cluster is considered abnormal and the status of the cluster changes to Inactive or Unavailable. When your cluster changes to the Inactive or Unavailable state, ACK notifies you of the status change by sending a text message, email, or internal message.
State 1: Inactive
If your cluster is in the Inactive state, you can identify the cause based on the cluster status code.
Status code: KMSIndebtOverdue
Cause
Key Management Service (KMS)-based Secret encryption is enabled for the cluster. However, KMS is suspended for the Alibaba Cloud account due to reasons such as overdue payments. As a result, the control planes of the cluster cannot run as normal.
How to restore
Log on to the KMS console.
Identify the reason why KMS is suspended and resolve the issue. Then, resume KMS for the Alibaba Cloud account.
Choose ACK and submit a ticket to restore the cluster to the Running state.
Status code: NoPodCreatedForLongTime
Cause
No pod exists in the ACK Serverless cluster and no pod is created within the previous 30 days.
How to restore
Choose ACK and submit a ticket to restore the cluster to the Running state.
Status code: NoNodeForLongTime
Cause
No node exists in the ACK Basic cluster and no node is created within the previous 30 days.
How to restore
Choose ACK and submit a ticket to restore the cluster to the Running state.
Status code: ServiceIndebt
Cause
If your account balance is insufficient to pay a bill, your ACK Pro cluster enters the Inactive state. As a result, you cannot access the API server or perform any operations that involve the API server. However, your businesses on the cluster nodes can still run as normal. If your account remains overdue for more than 15 days, Alibaba Cloud will stop providing services to you. Nodes will be removed from your ACK Pro cluster and the cluster will be deleted. Other cloud resources used by your ACK Pro cluster are not released.
How to restore
Top up your account to pay the bill before your service is suspended. After you settle the overdue payment, your cluster is restored.
State 2: Unavailable
Cause
The Classic Load Balancer (CLB) instance that is used to expose the API server of the cluster is released due to the following reasons:
The CLB instance is manually released.
The subscription of the CLB instance expires.
The CLB instance is released because the Alibaba Cloud account has overdue payments.
How to restore
Clusters in the Unavailable state cannot be restored. You must recreate the cluster.
Impacts
Impacts on billing
When your cluster is in the Inactive or Unavailable state, you are still charged for cluster management and cloud resources. For more information about the billing, see Billing.
Impacts on cluster operations
When your cluster is in the Inactive or Unavailable state, you can perform only the following operations on the cluster:
Enable or disable deletion protection for the cluster.
Delete the cluster.
References
For more information about other cluster states, see Cluster lifecycle.
For more information about resource billing, see Resource billing. This topic provides answers to some frequently asked questions, such as whether the billing continues when a cluster is being deleted or the cluster fails to be deleted and in what cluster states no cluster management fee is charged.