update_nodegroup_config
¶
update_nodegroup_config(
cluster_name: String,
nodegroup_name: String,
*,
config_overrides: Optional[EKSClientConfig] = 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/eks.py
5045 5046 5047 5048 5049 5050 5051 5052 5053 5054 5055 5056 5057 5058 5059 5060 5061 5062 5063 5064 5065 5066 5067 5068 5069 5070 5071 5072 5073 5074 5075 5076 5077 5078 5079 5080 5081 5082 5083 5084 5085 5086 5087 5088 5089 5090 5091 5092 5093 5094 5095 5096 5097 5098 5099 5100 5101 5102 5103 5104 5105 5106 5107 5108 5109 5110 5111 5112 5113 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 | |