Skip to main content
Don’t modify CoreWeave-managed resources on CoreWeave Kubernetes Service (CKS), even though your cluster-admin access permits it. CoreWeave automation reverts your changes, and those changes can disrupt cluster networking, scheduling, and Node health.

​
Resources to leave unchanged

Leave the following resources unchanged:
  • Managed workloads: Don’t patch, delete, evict, or reschedule resources in CoreWeave-managed Control Plane namespaces, including kube-system and CoreWeave-managed cw-* namespaces.
  • Managed scheduling configuration: Don’t remove tolerations or change affinity or nodeSelector settings on CoreWeave-managed Deployments and DaemonSets.
  • Managed Node metadata: Don’t modify labels or taints that CoreWeave sets, including node.coreweave.cloud/* labels.

​
Identify managed namespaces

CKS labels the cw-* Control Plane namespaces with ns.coreweave.cloud/org=control-plane. To list them, run:
Treat this command as a way to find the cw-* namespaces, not as the complete list of what CoreWeave manages.
For the components CoreWeave manages and their namespaces, see Cluster components. For the responsibility boundary, see What CoreWeave manages.

​
Request a change

If you need a change to a managed resource, contact support and describe the problem you’re trying to solve. If you’ve already changed a resource, then alongside the details every ticket needs, listed in Support ticket templates, include the resource name and the command you ran. Administrator
Last modified on October 13, 2026