eks.nodegroups.upgrade

Upgrade a node group to the cluster’s Kubernetes minor

PUT /eks/api/clusters/{cluster}/nodegroups/{name}/versionIAM eks:UpdateNodegroupVersionChanges stateDestructive

Surge replacement: one extra node at the new minor, then one node behind is drained and removed, until none is behind. PodDisruptionBudgets are respected for the group’s drainTimeoutMinutes (default 60) per node; then the upgrade pauses at that node, or with forceAfterTimeout the node goes anyway. Never above the control plane’s minor.

Request syntax

PUT /eks/api/clusters/{cluster}/nodegroups/{name}/version
{
  "version": "enum"
}

Path parameters

  • clusterRequired

    string

    Constraints: /^(ewk-[0-9a-f]{12}|[a-z]([a-z0-9-]{0,38}[a-z0-9])?)$/

  • nameRequired

    string

    Constraints: /^[a-z]([a-z0-9-]{0,30}[a-z0-9])?$/

Request body

  • versionOptional

    enum

    Kubernetes minor for the nodes; default the cluster’s, never above it

    One of: 1.36, 1.37

Response

200 with the node group, status `updating` and version the new minor: id, name, instanceType, minSize, desiredSize, maxSize, labels, taints, version, nodeRoleId, autoscaling, zones, drainTimeoutMinutes, forceAfterTimeout, status, reconcileError, readyNodes, nodes (name, instanceId, status, version, zone, drainMessage, privateIpv4, publicIpv4, createdAt), createdAt. On a `paused` group already at that minor it resumes the upgrade (the held node’s drain starts over). 400 above the control plane’s minor or for a downgrade; 409 unless the cluster is active (while the control plane upgrades too), while the group is being deleted, or when it already runs that minor; 404 for an unknown cluster or node group, 403 without the permission.

A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.

Errors

  • 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
  • 401No credentials, or an access key that is unknown, revoked or expired.
  • 403The caller's policies do not allow eks:UpdateNodegroupVersion on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
  • 404The resource does not exist in your organization.

Examples

The required parameters only, with example values. Replace id and the other placeholders with your own.

dcloud eks nodegroups upgrade cluster name

Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_eks_nodegroups_upgrade.