Skip to main content

Cluster Components

Reference for the components within the CKS Managed Control Plane and Managed Data Plane

Kubernetes versions

CoreWeave Kubernetes Service (CKS) supports multiple Kubernetes versions to ensure compatibility with a wide range of applications and workloads. This allows customers to choose a version that best fits their needs while also ensuring access to the latest features and security updates.

Supported versions

CKS can create clusters with these Kubernetes versions, which use the control group (cgroup) version listed.

Kubernetes VersionControl Group VersionNotes
v1.30cgroup v1
v1.31cgroup v1
v1.32cgroup v1Default version for new clusters
v1.33cgroup v2

Deprecated versions

These versions are no longer supported for new CKS clusters. Existing clusters can continue to operate until they are upgraded or decommissioned.

Kubernetes VersionControl Group VersionNotes
v1.29cgroup v1Deprecated

Managed Control Plane

To ensure security and stability, CoreWeave provides a Managed Control Plane for CKS clusters. Learn more about CKS cluster architecture.

Managed Data Plane components

The CKS Managed Data Plane comes with several preinstalled components, which allow customers to start running workloads immediately after deploying their CKS cluster. These components are configurable to allow for the desired state of a CKS cluster.

Info
  • Some older clusters' namespaces may not have the cw- prefix shown in the tables below.
  • Components and API versions change often. The versions deployed to your cluster may be newer than shown below.

Networking

ComponentNamespaceVersionDescription
ciliumcw-cilium-system1.16.1Container Network Interface (CNI) that uses eBPF for efficient load-balancing.
calico (deprecated)cw-calico-system3.29.1Container Network Interface (CNI) used on older clusters; no longer supported for new CKS clusters.
multus-cniEnables attaching multiple network interfaces to Pods. Used to configure InfiniBand as a secondary interface for workloads that require high throughput and low latency in HPC environments.
coredns1.11.1A flexible DNS server consisting of multiple plugins that manage in-cluster DNS and resolve service records inside clusters. This runs in the CKS Managed Control Plane.
konnectivity-agentkube-system0.30.3Isolates CKS Control Plane traffic from the cluster network and creates a TCP level proxy to konnectivity-server, which sits alongside the Control Plane to tunnel traffic from the Control Plane to in-cluster endpoints.
metallbcw-metallb-system0.13.4Handles IP Address Management (IPAM) for LoadBalancer services; is not used for advertisements. See How to: Expose a Service
node-local-dnskube-system1.22.28Improves cluster DNS performance and speeds up traffic between CoreDNS instances. The node-local-dns Pods run CoreDNS in local caching mode as a DaemonSet over TCP, avoiding dropped packets and reducing tail latency.

Networking notes

  • Cilium, like CKS, is a managed product. We deploy Cilium with a minimal feature set. If you require a feature that isn't enabled, or is only available in Cilium Enterprise, please contact support.
  • Argo CD has documented issues with Cilium when not using annotation tracking. To prevent issues, declare resource exclusions in the Argo CD ConfigMap.
  • Customers who require a specific CNI (such as Cilium Enterprise instead of Cilium Open Source) can bring their own. This manual process requires coordination with CoreWeave when deploying the cluster. Please contact support for more information.

Cluster management

ComponentNamespaceVersionDescription
hpc-verificationcw-hpc-verification1.8.0Validates the Node is in an optimal state. These tests only run on idle Nodes.
node-problem-detectorcw-node-problem-detector1.5.0Framework for running health checks for each Node run as a DaemonSet. It allows CoreWeave to quickly identify Nodes that are misbehaving and mark them as Unschedulable.
nfdcw-nfd0.9.0Node Feature Discovery. Detects hardware features and labels Nodes accordingly for use in scheduling decisions.
Info

Older clusters may have jspolicy installed in the jspolicy-policies-<Org ID>-<cluster ID> and tenant-<Org ID>-<cluster ID> namespaces. Newer clusters do not include JSPolicy.

Observability and security

ComponentNamespaceVersionDescription
victoria-metricscw-victoria-metrics0.45.0Collects metrics from inside the cluster and relays them to a logging solution.
vmagentcw-victoria-metricsGathers metrics for Victoria Metrics.
metrics-serverkube-system0.6.2Only installed on clusters deployed before July 7, 2025.
node-pci-exportercw-exporters1.5.0Extends the node-exporter running as part of the Prometheus stack, exposing additional metrics about deployed GPUs.
gpu-thermal-exportercw-exportersEmits hardware metrics for GPU thermal data for Node health monitoring.
nvlink-exportercw-exportersExports metrics for NVLink performance in GPU Nodes.
ping-exportercw-ping-exporterMeasures packet loss to configured network targets for connectivity checks.
promtailcw-promtailForwards Node logs centrally using Grafana's Promtail.
crowdstrikecw-crowdstrike7.19.0-17219-1.falcon-linux.Release.US-2CrowdStrike Falcon cybersecurity tooling.

Storage

ComponentNamespaceVersionDescription
vast-csicw-vast-csi2.3.1Container Storage Interface for Vast Storage.

Object Storage

ComponentNamespaceVersionDescription
lotacw-object-storagev1.25.1CoreWeave's Local Object Transfer Accelerator (LOTA) for AI Object Storage. Learn more about LOTA.

Hardware

ComponentNamespaceVersionDescription
k8s-device-plugincw-nvidia-device-plugin0.12.3NVIDIA's official device plugin for GPU-enabled containers in Kubernetes.
nvidia-imexcw-nvidia-imexEnables the NVIDIA Internode Memory Exchange (IMEX) service.
rdma-shared-dpcw-rdmaDevice plugin to support InfiniBand and RDMA hardware resources.
Warning

CKS does not require NVIDIA's GPU Operator. To avoid conflicts, customers should not attempt to install it.