To improve the stability of the API, Container Service for Kubernetes (ACK) will launch an API update on November 18, 2024. This update does not impact the features or availability of the API. When you call certain API operations, a data update delay or performance fluctuation may occur. To address these issues, read this topic.
Scope of impact
When you call the DescribeClusters or DescribeClustersV1 API operation to query clusters after you create, modify, or delete a cluster, the cluster update may be updated with a delay of 1 to 10 seconds.
When you call the DescribeEvents API operation to query cluster events, the event data may be updated with a delay of 1 to 10 seconds.
When you call the GrantPermissions or UpdateUserPermissions API operation to modify the cluster access permissions of a RAM user or RAM role, the Kubernetes API-related permission data may be updated with a delay of 1 to 10 seconds. If you use the kubeconfig file to query Kubernetes API-related permissions, the data is updated without any delay.
When you use an endpoint that does not match the region of the cluster to call a cluster-related API operation, the availability of the API is not affected. However, the time consumption of the API call will slightly increase. To address this issue, read the following section.
Solutions
Use the right endpoint
Container Service for Kubernetes provides a separate endpoint for each supported region. For more information, see Endpoints. Using an endpoint that matches the region of the cluster can greatly improve the performance and availability of each API call. We recommend that you check and modify the code of existing API calls to ensure that the endpoints match the region of the cluster.
For different API operations, we recommend that you choose endpoints based on the following table.
You can select a Container Service for Kubernetes API operation in the OpenAPI Explorer console and then view the method for configuring endpoints for SDKs of different versions and languages on the SDK Sample Code tab.
API operation | Example | Suggested endpoint |
Create, query, modify, and delete clusters, relevant resources (such as node pools and components), and relevant objects (such as jobs, events, and applications). |
| Endpoint that matches the region of the cluster. |
Query the metadata of cluster operations. |
| Endpoint that matches the region of the cluster. |
Manage user-level configurations. |
| Non-region-level endpoint (cs.aliyuncs.com). |
Use single-cluster API operations to query the status of operations
After this update, the data returned by API operations that involve more than one cluster, such as DescribeClusters, DescribeClustersV1, and DescribeEvents, will be updated with a delay of 1 to 10 seconds. Call the API operations suggested in the following table.
Scenario | API operation | Suggest API operation |
Query the status of a cluster after you perform an operation on the cluster. | DescribeClusters and DescribeClustersV1 | |
Query the corresponding event after you perform an operation on a cluster. | DescribeEvents |
Use region-level API operations
To enhance data isolation among different regions and ensure the availability of all API operations, Container Service for Kubernetes provides region-level versions for partial API operations. The following table describes these API operations.
Before you call a region-level API operation, grant the identity that you use RAM permissions to use the API operation. For more information, see RAM authorization.
Current API operation | Region-level API operation | Action in a RAM policy |
DescribeClusters and DescribeClustersV1 | DescribeClustersForRegion | cs:DescribeClustersForRegion |
DescribeEvents | DescribeEventsForRegion | cs:DescribeEventsForRegion |
References
You can log on to the OpenAPI Explorer console to debug API operations.
For more information about the API reference for Container Service for Kubernetes, see List of operations by function.