CoreWeave Release Notes

Organization administrators can now control how users authenticate to the CoreWeave Cloud Console using login methods. Enable or turn off each method organization-wide, and set per-user overrides for individual users. CoreWeave supports four login methods: email and password, Google, GitHub, and SAML SSO. This feature is in limited availability. See the login methods release notes for more information.

CoreWeave IAM now includes CoreWeave-managed default access policies for baseline Admin and Viewer access patterns. Default policies are marked with a Default badge. CoreWeave manages their role membership as the platform evolves, and you cannot delete them. See the Default access policies in IAM release notes for details.

CoreWeave AI Object Storage now supports direct API token exchange for temporary S3-compatible credentials.

You can exchange a CoreWeave API access token directly for short-lived credentials without creating a separate static access key.

You can also use group attributes in bucket policy conditions.

See the AI Object Storage direct API token exchange release notes for more information.

Effective July 29, 2026, CoreWeave is deprecating several operating system, kernel, and driver versions that are deprecated upstream and no longer receive security fixes. CoreWeave handles all updates and migrations to supported versions, so no action is required on your part. See Upcoming deprecations for the full list of affected operating systems, NVIDIA GPU drivers, and networking components.

You can now set targetRacks directly in the Cloud Console when creating a Node Pool for rack-based instance types such as GB200 and GB300. The Node Pool creation page includes a Target Racks field, so you no longer need to edit the manifest by hand to request capacity at the rack level. See Create a Node Pool for more information.

Default storage quotas for CoreWeave AI Object Storage and Distributed File Storage have been reduced.

The default AI Object Storage quota is now 20 TiB per availability zone, and the default DFS quota is now 10 TiB per CKS cluster.

See AI Object Storage quotas and DFS quotas for current values.

You can now configure CoreWeave Telemetry Relay yourself, without contacting Support. Use the Cloud Console or the Telemetry Relay API to forward CoreWeave audit logs to an HTTPS endpoint. See the Telemetry Relay self-service release notes for more information.

A new NodePools and Cluster Autoscaler dashboard is now available in CoreWeave Grafana.

The dashboard gives you a single place to inspect Node Pool capacity and conditions, read Node Pool events, and track Cluster Autoscaler scaling activity, errors, and logs without querying metrics or logs directly.

You can now browse, upload, download, rename, and delete objects in CoreWeave AI Object Storage buckets directly from the Cloud Console, with no CLI tools or third-party software required. Navigate folder hierarchies, search for buckets and objects by name, and drag files from your desktop to upload them. See the release notes for the full list of supported operations and required permissions.

CKS Node Pools now support targetRacks for NVL72-powered instances, letting you request GB200 and GB300 capacity at the rack level instead of counting individual Nodes. Each rack provisions a full set of 18 Nodes, so you no longer need to set targetNodes to a multiple of 18 to deploy complete racks.

CKS Node Pools now support prefill, which provisions a replacement Node before a triaged Node is drained and removed.

With prefill enabled, the pool stays at or above spec.targetNodes during maintenance, so workloads do not see a capacity gap while the replacement is delivered.

See Enable Node Pool Prefill to configure the timeout and maxNodes fields.

New AI Object Storage documentation covers bucket lifecycle policies, aborting incomplete multipart uploads, and emptying and deleting buckets. The S3 reference now consolidates API compatibility notes, and the Terraform guide documents a known issue with NoncurrentVersionTransitions in CoreWeave provider v0.7.0. See the release notes for more information.

CKS now supports Kubernetes v1.36.

All new CKS clusters use v1.36 as the default version.

Support for v1.33 for new clusters has been deprecated, but existing clusters running v1.33 will continue to work. See Cluster Components for the full list of supported versions.

The supported GPU drivers have changed. See Supported driver versions for the full compatibility table.

GB200 NVL72-powered instances

Drivers removed: 570

A100

Drivers removed: 570

H100 (InfiniBand)

Drivers removed: 570

H200 (InfiniBand)

Drivers removed: 570

L40

Drivers removed: 570

L40S

Drivers removed: 570

RTX Pro 6000 Blackwell Server Edition

Drivers removed: 570

The supported GPU drivers have changed. See Supported driver versions for the full compatibility table.

B200 (InfiniBand)

New default: 580 → 595

B300 (InfiniBand)

Drivers added: 595

GB200 NVL72-powered instances

New default: 580 → 595

GH200

New default: 580 → 595

H100 (InfiniBand)

New default: 580 → 595

H200 (InfiniBand)

New default: 580 → 595

L40

New default: 580 → 595

L40S

New default: 580 → 595

Drivers added: 535, 570, 595