EKS Update Nodegroup Config - BlinkOps Documentation

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. Currently you can update the Kubernetes labels for a node group or the scaling configuration.

External DocumentationTo learn more, visit the AWS documentation.

Basic Parameters

Parameter	Description
AWS Region(s)	Enter the desired AWS Region(s). To execute the action in multiple regions, provide a comma-separated list. For example: `us-east-1,eu-west-2`. If you wish to run the action in all available regions, use the asterisk symbol (`*`) instead.
Cluster Name	The name of the Amazon EKS cluster that the managed node group resides in.
Nodegroup Name	The name of the managed node group to update.

Advanced Parameters

Parameter	Description
Add Or Update Labels	Kubernetes labels to be added or updated.
Add Or Update Taints	Kubernetes taints to be added or updated.
Client Request Token	Unique, case-sensitive identifier that you provide to ensure the idempotency of the request.
Disable XML To JSON Auto Convert	When checked, XML responses are not automatically converted into JSON format.
Remove Labels	Kubernetes labels to be removed.
Remove Taints	Kubernetes taints to be removed.
Scaling Config Desired Size	The current number of nodes that the managed node group should maintain.
Scaling Config Max Size	The maximum number of nodes that the managed node group can scale out to. For information about the maximum number that you can specify, see Amazon EKS service quotas in the Amazon EKS User Guide.
Scaling Config Min Size	The minimum number of nodes that the managed node group can scale in to.
Update Config Max Unavailable	The maximum number of nodes unavailable at once during a version update. Nodes will be updated in parallel. This value or `maxUnavailablePercentage` is required to have a value.The maximum number is 100.
Update Config Max Unavailable Percentage	The maximum percentage of nodes unavailable during a version update. This percentage of nodes will be updated in parallel, up to 100 nodes at once. This value or `maxUnavailable` is required to have a value.

Example Output

{
	"update": {
		"createdAt": "date-time",
		"errors": [
			{
				"errorCode": "string",
				"errorMessage": "string",
				"resourceIds": [
					"string"
				]
			}
		],
		"id": "string",
		"params": [
			{
				"type": "string",
				"value": "string"
			}
		],
		"status": "string",
		"type": "string"
	}
}