All Products
Search
Document Center

Container Service for Kubernetes:ModifyNodePoolNodeConfig

Last Updated:Nov 07, 2024
This topic is generated by a machine translation engine without any human intervention. ALIBABA CLOUD DOES NOT GUARANTEE THE ACCURACY OF MACHINE TRANSLATED CONTENT. To request a human-translated version of this topic or provide feedback on this translation, please include it in the feedback form.

Modifies the configuration of a node pool, such as the kubelet configuration and node rolling update configuration. After you modify the node pool configuration, nodes are batch updated and the kubelet on each node is restarted. This may adversely affect the nodes and workloads. We recommend that you perform this operation during off-peak hours.

Operation description

Note Container Service for Kubernetes (ACK) allows you to modify the kubelet configuration of nodes in a node pool. After you modify the kubelet configuration, the new configuration immediately takes effect on existing nodes in the node pool and is automatically applied to newly added nodes.

Debugging

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

Authorization information

The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:

  • Operation: the value that you can use in the Action element to specify the operation on a resource.
  • Access level: the access level of each operation. The levels are read, write, and list.
  • Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
    • The required resource types are displayed in bold characters.
    • If the permissions cannot be granted at the resource level, All Resources is used in the Resource type column of the operation.
  • Condition Key: the condition key that is defined by the cloud service.
  • Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
OperationAccess levelResource typeCondition keyAssociated operation
cs:ModifyNodePoolNodeConfigupdate
  • Cluster
    acs:cs:{#regionId}:{#accountId}:cluster/{#ClusterId}
    none
none

Request syntax

PUT /clusters/{ClusterId}/nodepools/{NodepoolId}/node_config HTTP/1.1

Request parameters

ParameterTypeRequiredDescriptionExample
ClusterIdstringYes

The ID of the cluster.

c23421cfa74454bc8b37163fd19af****
NodepoolIdstringYes

The node pool ID.

np8d8c9c2cd0f64e89884f82a5fbcd****
bodyobjectNo

The request body.

kubelet_configkubelet_configNo

The parameters of the kubelet.

rolling_policyobjectNo

The rotation configurations.

max_parallelismlongNo

The maximum number of unavailable nodes.

3
os_configobjectNo

Operating system parameter configuration.

sysctlobjectNo

sysctl parameter configuration

anyNo

sysctl parameter configuration

fs.aio-max-nr

Response parameters

ParameterTypeDescriptionExample
object

The response body.

request_idstring

The request ID.

D7631D83-6E98-1949-B665-766A62xxxxxx
task_idstring

The task ID.

T-5fd211e924e1d00787xxxxxx
nodepool_idstring

The node pool ID.

np737c3ac1ac684703b9e10673aa2c****

Examples

Sample success responses

JSONformat

{
  "request_id": "D7631D83-6E98-1949-B665-766A62xxxxxx",
  "task_id": "T-5fd211e924e1d00787xxxxxx",
  "nodepool_id": "np737c3ac1ac684703b9e10673aa2c****"
}

Error codes

For a list of error codes, visit the Service error codes.

Change history

Change timeSummary of changesOperation
2024-04-17The internal configuration of the API is changed, but the call is not affectedView Change Details
2023-08-23The internal configuration of the API is changed, but the call is not affectedView Change Details
2022-08-30Add OperationView Change Details