LKS

Update a node pool

Scales, renames, upgrades or re-labels a node pool. At least one attribute must be provided.

labels and taints are declarative replacements, not merges: omit the field to leave it untouched, send the whole map/list to replace it, or send {} / [] to clear it.

A newer kubernetes_version rolls a node-recreating upgrade; it must not be lower than the pool's current patch nor newer than the control-plane patch. max_pods_per_node is immutable — a PATCH that carries it is rejected with 422 even if the value is unchanged.

The node pool must be idle: one that is provisioning, updating, scaling, upgrading, paused or deleting rejects the request with 409.

patch/lks/clusters/{cluster_id}/nodepools/{id}

Path parameters

cluster_idstring required

The cluster ID (format: lksc_<hash>).

idstring required

The node pool ID (format: lksnp_<hash>).

Request body

Example request

{
  "data": {
    "attributes": {
      "taints": [
        {
          "key": "dedicated",
          "value": "gpu",
          "effect": "NoSchedule"
        }
      ]
    }
  }
}

Response

OK

Changes

Changed in 2 of the 41 revisions of this API.6

    • ○

      the request property //// became nullable (media type: application/json)

      request-property-became-nullable

    • ○

      the request property //// became nullable (media type: application/vnd.api+json)

      request-property-became-nullable

    • ○

      added the optional property //// to the response with the status

      response-optional-property-added

    • ○

      added the required property //// to the response with the status

      response-required-property-added

    • ○

      added the required property //// to the response with the status

      response-required-property-added

    • ○

      endpoint added

      endpoint-added