update_nodegroup_config
async
¶
update_nodegroup_config(
cluster_name: String,
nodegroup_name: String,
*,
config_overrides: Optional[AsyncEKSClientConfig] = None,
labels: Optional[UpdateLabelsPayload] = None,
taints: Optional[UpdateTaintsPayload] = None,
scaling_config: Optional[NodegroupScalingConfig] = None,
update_config: Optional[NodegroupUpdateConfig] = None,
node_repair_config: Optional[NodeRepairConfig] = None,
warm_pool_config: Optional[WarmPoolConfig] = None,
client_request_token: Optional[String] = None,
) -> UpdateNodegroupConfigResponse
Updates an Amazon EKS managed node group configuration. Your node group continues to function during the update. The response output includes an update ID that you can use to track the status of your node group update with the DescribeUpdate API operation. You can update the Kubernetes labels and taints for a node group and the scaling and version update configuration.
Parameters:
-
cluster_name(String) –The name of your cluster.
-
nodegroup_name(String) –The name of the managed node group to update.
-
labels(Optional[UpdateLabelsPayload], default:None) –The Kubernetes
labelsto apply to the nodes in the node group after the update. -
taints(Optional[UpdateTaintsPayload], default:None) –The Kubernetes taints to be applied to the nodes in the node group after the update. For more information, see Node taints on managed node groups.
-
scaling_config(Optional[NodegroupScalingConfig], default:None) –The scaling configuration details for the Auto Scaling group after the update.
-
update_config(Optional[NodegroupUpdateConfig], default:None) –The node group update configuration.
-
node_repair_config(Optional[NodeRepairConfig], default:None) –The node auto repair configuration for the node group.
-
warm_pool_config(Optional[WarmPoolConfig], default:None) –The warm pool configuration to apply to the node group. You can use this to add a warm pool to an existing node group or modify the settings of an existing warm pool.
-
client_request_token(Optional[String], default:None) –A unique, case-sensitive identifier that you provide to ensure the idempotency of the request.
Raises:
-
ClientException–These errors are usually caused by a client action. Actions can include using an action or resource on behalf of an IAM principal that doesn't have permissions to use the action or resource or specifying an identifier that is not valid.
-
InvalidParameterException–The specified parameter is invalid. Review the available parameters for the API request.
-
InvalidRequestException–The request is invalid given the state of the cluster. Check the state of the cluster and the associated operations.
-
ResourceInUseException–The specified resource is in use.
-
ResourceNotFoundException–The specified resource could not be found. You can view your available clusters with
ListClusters. You can view your available managed node groups withListNodegroups. Amazon EKS clusters and node groups are Amazon Web Services Region specific. -
ServerException–These errors are usually caused by a server-side issue.
-
UnknownServiceError–The service returned an error code this client does not model.
Source code in docs_src/capo_eks/_services/async_eks.py
5114 5115 5116 5117 5118 5119 5120 5121 5122 5123 5124 5125 5126 5127 5128 5129 5130 5131 5132 5133 5134 5135 5136 5137 5138 5139 5140 5141 5142 5143 5144 5145 5146 5147 5148 5149 5150 5151 5152 5153 5154 5155 5156 5157 5158 5159 5160 5161 5162 5163 5164 5165 5166 5167 5168 5169 5170 5171 5172 5173 5174 5175 5176 5177 5178 5179 5180 5181 5182 5183 5184 5185 5186 5187 5188 5189 5190 5191 5192 5193 5194 5195 5196 5197 5198 5199 5200 5201 5202 5203 5204 5205 5206 5207 5208 5209 | |