kubectl to CKS clusters and keep credentials secure.
The following section walks through creating an API Access Token and downloading the associated kubeconfig file.
Prerequisites
This guide assumes that you have an active CoreWeave account.Create a new API access token
API access tokens authenticate programmatic access to CoreWeave services. Create them in the CoreWeave Cloud Console. To create a new access token, complete the following steps:- In Cloud Console, navigate to Tokens, and then click the Create Token button in the upper-right corner.
-
In the Create API Token dialog, complete the following fields to configure the token values, and then click Create:
Field Description Name The name of the token. Expiration How long the token remains valid. Note A description for future reference. -
Select one of the following options:
After you complete these steps, your new API access token is ready to use with CoreWeave services.
Option Description Token Secret Copy and store the token secret for use cases such as scraping metrics, scraping logs, self-hosted Grafana setup, or to add the token secret to an existing kubeconfig.Kubeconfig Create and download a kubeconfigfor a specific cluster, so you can interact with the cluster using commands likekubectl. Akubeconfigcan access multiple clusters when you switch contexts.
Use the kubeconfig file
After you have a kubeconfig file from the previous section, this section explains how to put it in place sokubectl can authenticate to your CKS cluster.
To use the kubeconfig file, you must have the kubectl command-line tool installed. If you don’t have kubectl installed, follow the instructions in the Kubernetes documentation.
To use the kubeconfig file, choose one of the following options:
- Copy it to the default location for kubeconfig files, typically
~/.kube/config. - Specify the file location with the
KUBECONFIGenvironment variable. - Use the
--kubeconfigflag withkubectl.
kubectl to interact with the CKS clusters. The following command displays the merged kubeconfig that kubectl will use, which helps you verify the configuration: