Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.coreweave.com/llms.txt

Use this file to discover all available pages before exploring further.

Node Pool configuration management improvements with enhanced visibility, staged updates, and rollback capabilities.

​
Overview

CoreWeave introduces Node Pool configuration management capabilities in CKS. Node Pool configurations define the desired state for Nodes, including ncore image versions, GPU driver versions, and Kubernetes versions. These improvements provide full visibility into active configurations, pending updates, and configuration history, enabling more informed decisions about Node Pool upgrades and rollbacks.

​
What’s new

​
Node Profile tracking

Node Pool configurations are now referenced by a unique identifier called a nodeProfile. The active configuration is exposed through the status.nodeProfile field, providing a clear view of the current state of Nodes in the Node Pool.

​
Configuration revisions history

Node Pools now maintain a nodeConfigurationRevisions list in the status that tracks all configurations that have been applied to the Node Pool. Each revision includes:
  • The count of Nodes currently running each configuration (activeNodes)
  • Creation timestamp
  • Configuration summary with ncore version, GPU driver version, and Kubernetes version
  • Disabled status if a configuration experienced boot failures
This history enables rollback to previous configurations and provides visibility into which Nodes are running which configurations.

​
Staged configuration updates

The new pendingNodeConfiguration field provides visibility into staged configurations that are ready to be applied. CKS automatically generates and stages new configurations when:
  • Node Pool spec changes require a new configuration (updating spec.image or spec.gpu fields)
  • Updates become available for your Node Pool, such as newer ncore images
The pendingNodeConfiguration includes a detailed summary of what will change, allowing you to review updates before applying them. This stage-then-apply pattern ensures that Node Pool changes are user-controlled and require an explicit upgrade action.

​
Apply configurations with cwic

Use the CoreWeave Intelligent CLI (cwic) to manage Node Pool configurations:
  • Check for pending configurations: cwic nodepool get NODEPOOL_NAME shows which Node Pools have pending configurations
  • Apply pending configurations: cwic nodepool upgrade NODEPOOL_NAME stages the new configuration to the Node Pool
  • Identify Nodes requiring updates: cwic nodepool nodes get NODEPOOL_NAME -r shows which existing Nodes need reconfiguration
After applying a configuration, newly created Nodes use the new configuration automatically. Existing Nodes require a reconfigure reboot to update their configuration.

​
Rollback to previous configurations

Node Pools now support rolling back to previous configurations using cwic nodepool rollback:
  • Roll back to the previous configuration: cwic nodepool rollback NODEPOOL_NAME
  • Roll back to a specific configuration: cwic nodepool rollback NODEPOOL_NAME NODEPROFILE
When you perform a rollback, the active status.nodeProfile is set to the desired configuration. New Nodes boot into the rolled back configuration, and existing Nodes may require a reconfigure reboot. The nodeConfigurationRevisions list maintains up to 5 inactive configurations for rollback purposes, with older configurations subject to garbage collection.

​
Additional resources

For detailed information about Node Pool configuration management, see Manage Node Pool configuration.
Last modified on February 5, 2026