Skip to main content

​
Overview

SUNK v8.1.0 was released on September 23, 2026, and the v8.1.1 patch release followed on September 24, 2026. Both ship with Slurm 25.11.8-coreweave.1 by default, up from 25.11.6-coreweave.2 in SUNK 8.0. See SUNK to Slurm version mapping. The main change in 8.1 is per-job isolation: each job now gets its own PID namespace, /tmp, and /dev/shm by default. The release also tightens validation of the SlurmCluster resource, runs slurmctld as a non-root user, and adds two SUNK Pod Scheduler annotations. New SUNK Self-Service clusters default to SUNK 8.1.1. Patch releases for 8.1 are listed on this page under Patch releases.

​
Upgrade to 8.1

Set sunkVersion on the SunkCluster resource. To also take the Slurm build that ships with 8.1, set slurmVersion in the same change. The following command upgrades a cluster in the tenant-slurm namespace, the namespace the Cloud Console uses, to SUNK 8.1.1 and its default Slurm build:
slurmVersion needs the leading v. sunkVersion works with or without it. For how the rollout treats running jobs, see Upgrade a SUNK Self-Service cluster.SUNK Self-Service copies spec.slurmConfig from the SunkCluster onto the SlurmCluster resource, so before you upgrade, check your spec.slurmConfig for the StateSaveLocation and PrologFlags=NoHold settings in Changes to check before you upgrade.

​
Changes to check before you upgrade

​
New in 8.1

  • SUNK Pod Scheduler annotations. sunk.coreweave.com/wckey sets the Slurm workload characterization key, and sunk.coreweave.com/segment sets the topology segment size. See the annotations reference.
  • Block topology labels. The operator now resolves each node’s block-topology label per node. It uses the ds.coreweave.com/nvlink.domain label, and falls back to the nvidia.com/gpu.clique label when the domain label isn’t set.
  • Database cleanup on deletion. Deleting a SlurmCluster that uses the moco or cwdb backend now waits for its managed MySQL cluster to finish cleaning up, through a sunk.coreweave.com/database finalizer. Before 8.1, compute nodes could be torn down first, which could leave the MySQL cluster stuck in Terminating.

​
Fixes

  • Changes to nsscache.sudoGroups now reach running login and compute Pods without a Pod restart. Before 8.1, removing a group didn’t revoke its passwordless sudo grant on running Pods.
  • The node health check epilog skips its exclusive tests when the node is already allocated to another job, so a stale epilog no longer drains a node in use.
  • A custom topology.conf is preserved when compute.generateTopology is false.
  • Disabling slurmrestd, for example by removing rest.enabled: true from your slurm chart values, now deletes it. Before 8.1, it kept running. The SlurmCluster status now reports the status of slurmrestd.
  • SlurmCluster conditions report errors from child resources, and the DatabaseAvailable condition includes failure details from the CWDBCluster.
  • A login Pod’s default memory limit no longer caps a larger request. Before 8.1, a request above the default limit failed validation and blocked the login Pod from being created.
  • SUNK scripts match slurm.conf keys case-insensitively.
  • Compute Pods now carry the labels that the [CLUSTER-NAME]-compute headless Service selects on. Before 8.1, NodeSets that SUNK Self-Service created, and hand-written NodeSet resources, lacked them, so the Service had no endpoints and per-Pod DNS names didn’t resolve. This broke distributed setups that rely on node hostnames. On upgrade, the affected NodeSets roll once.

​
Patch releases

​
8.1.1

Released September 24, 2026. Ships with Slurm 25.11.8-coreweave.1 by default, the same as 8.1.0.
  • GPU Straggler Detection installs after all other one-shot s6 services finish, so it no longer contends with packages you install for the apt lock.
  • nsscache runs full updates instead of incremental ones, so updates no longer depend on the modifytimestamp filter.
Last modified on October 22, 2026