Create cluster
Create a new CoreWeave CKS cluster with optional OIDC, webhook, kubelet, and Tailscale configuration.
- The API server is
https://api.coreweave.com. - Replace
{API_ACCESS_TOKEN}with your CoreWeave API access token. - For required permissions, see IAM Access Policies.
vpcId. The cluster id is assigned by the server and
returned in the response. Do not set it on the request.
The following fields are required:
namezonevpcIdversionnetwork.podCidrNamenetwork.serviceCidrNamenetwork.internalLbCidrNames
Optional advanced configuration
oidc: configure an OpenID Connect provider for authentication to the api-server.authzWebhook/authnWebhook: configure authorization and authentication webhook servers for the api-server.auditPolicy: a base64-encoded JSON or YAML audit policy.kubelet: a JSON object of selective overrides applied to every cluster Node’s kubelet configuration. A Node reboot is required for changes to take effect. Unknown options are stored but ignored. See the Kubernetes kubelet configuration reference for supported options.additionalServerSans: up to 10 additional Subject Alternative Names to include on the Kubernetes API server certificate.tailscale: Tailscale configuration for the cluster.sharedStorageClusterId: the cluster ID (not name) of an existing CKS cluster whose shared storage this cluster should join.disableOidcInfoPublication: whentrue, suppresses publication of/.well-known/openid-configurationand/openid/v1/jwkstooidc.cks.coreweave.com/id/[CLUSTER-ID], so the cluster cannot be used as a public OIDC provider.
Authorizations
Body
The Availability Zone in which the cluster is located.
The cluster ID (not name) of an existing CKS cluster whose shared storage this cluster should join. Set at create time only; this field is not present on UpdateClusterRequest, so it cannot be changed after the cluster is created.
When true, suppresses publication of the /.well-known/openid-configuration and /openid/v1/jwks endpoints to oidc.cks.coreweave.com/id/[CLUSTER-ID], so the cluster cannot be used as a public OIDC provider. Publishing these endpoints exposes the cluster's OIDC configuration and JWKS to the public Internet.
A JSON object of selective overrides applied to every cluster Node's kubelet configuration. A Node reboot is required for changes to take effect. Unknown options are stored but ignored. See the Kubernetes kubelet configuration reference for supported options.