Updates the Kubernetes version or AMI version of an Amazon EKS managed node group.
See https://www.paws-r-sdk.com/docs/eks_update_nodegroup_version/ for full documentation.
eks_update_nodegroup_version(
clusterName,
nodegroupName,
version = NULL,
releaseVersion = NULL,
launchTemplate = NULL,
force = NULL,
clientRequestToken = NULL
)
[required] The name of your cluster.
[required] The name of the managed node group to update.
The Kubernetes version to update to. If no version is specified, then
the Kubernetes version of the node group does not change. You can
specify the Kubernetes version of the cluster to update the node group
to the latest AMI version of the cluster's Kubernetes version. If you
specify launchTemplate
, and your launch template uses a custom AMI,
then don't specify version
, or the node group update will fail. For
more information about using launch templates with Amazon EKS, see
Customizing managed nodes with launch templates
in the Amazon EKS User Guide.
The AMI version of the Amazon EKS optimized AMI to use for the update. By default, the latest available AMI version for the node group's Kubernetes version is used. For information about Linux versions, see Amazon EKS optimized Amazon Linux AMI versions in the Amazon EKS User Guide. Amazon EKS managed node groups support the November 2022 and later releases of the Windows AMIs. For information about Windows versions, see Amazon EKS optimized Windows AMI versions in the Amazon EKS User Guide.
If you specify launchTemplate
, and your launch template uses a custom
AMI, then don't specify releaseVersion
, or the node group update will
fail. For more information about using launch templates with Amazon EKS,
see Customizing managed nodes with launch templates
in the Amazon EKS User Guide.
An object representing a node group's launch template specification. You can only update a node group using a launch template if the node group was originally deployed with a launch template.
Force the update if any Pod
on the existing node group can't be
drained due to a Pod
disruption budget issue. If an update fails
because all Pods can't be drained, you can force the update after it
fails to terminate the old node whether or not any Pod
is running on
the node.
A unique, case-sensitive identifier that you provide to ensure the idempotency of the request.