Update a node pool
All fields are optional. Changes to the Kubernetes version, release or other node configuration create a new NodeSet and roll the pool’s nodes to it.
Returns 400 for, among others: sending a field that is fixed at
creation (for example instanceTypeID); nico.release: "".
Authentication
A JWT from an issuer the Operator has configured, carried as Authorization: Bearer <token>.
Path parameters
Request
Disables auto-mode (automatic node recycling).
Free-text description.
The desired number of nodes in the pool. Increasing aggregate control-plane capacity above 1 requires controlPlaneVIP on the cluster.
Nodes allowed above desiredNodeCount during a rollout. 0 means sequential: each node is torn down before its replacement is provisioned.
Fields fixed at creation (instanceTypeID, partitions, sshKeyGroupIDs) cannot be sent: a request carrying one is rejected with 400. A body echoed from GET must have them stripped.
All LaunchLayer node-pool fields (instanceType, hostOSProfile, vmProfile, fulfillmentStrategy, securityGroupRefs) are fixed at creation: a request carrying one is rejected with 400. A body echoed from GET must have them stripped.
Response
Node names are <cluster>-<prefix>-<NNNN> (four-digit suffix), at most 63 characters in total.
Lifecycle conditions: provisioning, provisioned, deleting.
Disables auto-mode (automatic node recycling).
Annotations set on CAPI Machines only when they are created, including Machines created during scale-out or replacement. Fixed at node-pool creation. Not reconciled after provisioning. Keys under nke.nvidia.com, nke.io, nvke.nvidia.com, kubernetes.io, k8s.io, cluster.x-k8s.io and their subdomains require an explicit deployment allowlist entry for this metadata type.
Labels set on CAPI Machines only when they are created, including Machines created during scale-out or replacement. Fixed at node-pool creation. Not reconciled after provisioning. Keys under nke.nvidia.com, nke.io, nvke.nvidia.com, kubernetes.io, k8s.io, cluster.x-k8s.io and their subdomains require an explicit deployment allowlist entry for this metadata type.
Free-text description.
Nodes allowed above desiredNodeCount during a rollout. 0 means sequential: each node is torn down before its replacement is provisioned.