Get Started with CoreWeave
Learn how to configure your CoreWeave Kubernetes setup to access the Cloud
After providing payment information, you will receive a verification email to the account provided. After verifying your address, your information will be submitted to our team to verify your account request. You will also be redirected to a page that confirms the request was received.
Tip
For a higher chance of admission, it is strongly recommended to fill out the inbound sales form after submitting your account request. Please note, account approval may take up to three business days.
On CoreWeave, Kubeconfig files are used to interact with our Kubernetes cluster via clients such as
kubectl
. API Access Tokens are used for programmatic access to CoreWeave Cloud applications, such as Prometheus.Once your account has been approved and is activated, log in to the CoreWeave Cloud UI, then navigate to API Access on the left-hand menu. New Kubeconfig files and credentials as well as new API tokens are generated from this page.

The API & Kubeconfig page on the Cloud UI, accessed via the "API Access" link on the left-hand menu
Warning
The Kubeconfig and Access Token are shown only once!
Be sure to save this file and the token in a secure location. If you lose your Access Token, it can be found inside your Kubeconfig file.
From the API Access page on the Cloud UI, click the API & KUBECONFIG tab at the top right of the page, then click the Create a New Token button to the right.
When prompted, give the token a recognizable name, then click the Generate button. Generating the new token will also create a Kubeconfig file with the name
cw-kubeconfig
, which will embed your token. This file will download automatically.Note
If you would like to prevent the Kubeconfig file from downloading automatically, un-check the Automatically download Kubeconfig checkbox.

The "New Access Token" modal
Once you have obtained your Access Credentials, download the Kubernetes command line tools.
Additional Resources
For more information on Kubernetes installation and configuration, please reference the official Kubernetes documentation.
Linux
macOS
Windows
Downloading and installing the binary
The following command is a simple way to install
kubectl
on your Linux system by downloading the binary.curl -LO "https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl"
Once you have the
kubectl
binary downloaded, install it by first making the binary executable:$ chmod +x ./kubectl
Then, move the file into the system
bin
directory:$ sudo mv ./kubectl /usr/local/bin/kubectl
Note
If you would prefer to install Kubernetes using a Native Package Manager, please view the Kubernetes guide on Installing using Native Package Manager.
Verifying the kubectl binary
If you'd like to verify kubectl, you can verify it by running a checksum operation on the downloaded file prior to installing it, such as:
curl -LO "https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl"
echo "$(<kubectl.sha256) kubectl" | sha256sum --check
This should return
kubectl: OK
to confirm the file is indeed valid. If this returns an error, please review the official kubectl
installation guide.
Installing using Homebrew
If you do not already have Homebrew installed, follow the Brew Installation guide to do so, then install
kubectl
using Homebrew by running the following command:$ brew install kubectl
Installing using PowerShell
Using PowerShell,
kubectl
can be installed by using the following the command:
& $([scriptblock]::Create((New-Object Net.WebClient).DownloadString('https://raw.githubusercontent.com/coreweave/kubernetes-cloud/master/getting-started/k8ctl_setup.ps1')))
Note
Add the
-Silent
flag to the end of this string for a non-interactive setup.
Installing using a Package Manager
$ choco install kubernetes-cli
$ scoop install kubectl
If you would prefer to download the
kubectl
executable directly, follow the official Kubernetes instructions to download the latest version.Finally, once you have
kubectl
installed, and the cw-kubeconfig
file has been generated and downloaded, the next step is to move this config file to the right location.By default,
kubectl
looks for a file named config
(also referred to as a Kubeconfig file) in the $HOME/.kube
directory.If this is your first time using Kubernetes, or you're using a system that has never had Kubernetes configured before, you probably don't have a Kubeconfig file. You can check to see if you do by inspecting the Kubeconfig default path:
ls ~/.kube/config
If you do not have a Kubeconfig file, all you need to do is create the
~/.kube
directory if it does not already exist, and then move the downloaded cw-kubeconfig
to the ~/.kube/config
path:mkdir ~/.kube && mv ~/Downloads/cw-kubeconfig ~/.kube/config
If for some reason you would like to use a different path for the config file for your cluster, you can export the
$KUBECONFIG
environment variable. For example:export KUBECONFIG=~/.kube/cw-kubeconfig
Or, you can specify a path using the
--kubeconfig
option with kubectl
.If you already have an existing Kubeconfig file, you can install the CoreWeave Kubernetes credentials by merging the
cw-kubeconfig
file into ~/.kube/config
.To do this, first create a backup copy of the original Kubeconfig file:
$ cp ~/.kube/config ~/.kube/config.bak
Next, merge the downloaded
cw-kubeconfig
file into the file at the default path using kubectl
:$ KUBECONFIG=~/.kube/config:~/Downloads/cw-kubeconfig \
kubectl config view --merge --flatten > ~/.kube/config
If you are working on a system other than a Linux system, replace
~/.kube/config
path with one of the corresponding paths below. Be sure to replace the ~/Downloads
path in this example with the actual location of your downloaded Kubeconfig file, and the default path with the one that is applicable to your system.Operating System | Default path |
---|---|
Linux | ~/.kube/config |
macOS X | /Users/<username>/.kube/config |
Windows | %USERPROFILE%\.kube\config |
Since your new account will not yet have any resources, listing your cluster
secrets
is a good way to test that proper communication with the cluster is in place. To verify your CoreWeave Kubernetes configuration using kubectl
, invoke the following commands.$ kubectl config set-context coreweave
$ kubectl get secret
This should return your default
secrets
, such as:NAME TYPE DATA AGE
default-token-frqgm kubernetes.io/service-account-token 3 3h
You are now ready to use CoreWeave Cloud to deploy all types of services on CoreWeave's Kubernetes infrastructure!
Last modified 21d ago