Managing AI workloads across Managed Service for Kubernetes® clusters with SkyPilot

You can use SkyPilot as a single, declarative job surface that runs your AI workloads across one or more Managed Service for Kubernetes clusters. SkyPilot picks the best cluster for each job based on hardware availability and the constraints in the task definition, and fails over across clusters when capacity is tight in the preferred one. The SkyPilot placement logic combines constraint matching with policy:

With capability match, SkyPilot filters clusters by whether they meet the requested hardware and features, such as the GPU model, the number of GPUs per node, InfiniBand™ or a shared filesystem.
With capacity chasing, SkyPilot chases capacity across other clusters or regions when the preferred cluster has insufficient capacity.
With failover and retries, SkyPilot handles provisioning failures, such as preemptions or insufficient capacity, by automatically retrying with other matching clusters.

Costs

Nebius AI Cloud charges you for the following billing items:

Managed SkyPilot API Server (standalone application)
Managed Kubernetes nodes

Steps

Install dependencies

Make sure you have Python 3.10 or higher installed.
Install SkyPilot with Kubernetes and Nebius support:
```
pip3 install "skypilot[kubernetes,nebius]"
```

Prepare infrastructure

Deploy the Managed SkyPilot API Server:
1. In the Nebius AI Cloud console, go to AI Services → SkyPilot.
2. Enter a name for the application or keep the default one.
3. Select a Platform and a Preset (vCPUs and RAM) for the API server virtual machine.
4. Click Deploy application.
Connect to the SkyPilot API server. On the application page in the web console, click How to connect and copy the sky api login command. Then run the command in your terminal:
```
sky api login -e "https://<gateway>.skypilot.gw.msp.<region>.nebius.cloud"
```
Check that SkyPilot can reach your project:
```
sky check kubernetes
```
At this stage, no Managed Kubernetes clusters have been added yet, so the output looks similar to the following:
```
Checking credentials to enable infra for SkyPilot.
  Kubernetes: disabled
    Reason [compute]: No available context found in kubeconfig.
🎉 Enabled infra 🎉
  No infra to check/enabled.
```
You will run the same command again later to confirm that the contexts are picked up.
Create at least one Managed Kubernetes cluster with a GPU node group. To demonstrate cross-cluster failover, create two or more clusters.

For more information about how to install SkyPilot and connect to it, see Managing AI workloads on Compute virtual machines with SkyPilot.

Add Managed Kubernetes clusters to SkyPilot

The Managed SkyPilot API Server auto-discovers all Managed Kubernetes clusters in the same project. You do not need to add a local kubeconfig or configure a service account.

Open the SkyPilot dashboard. On the application page in the web console, click How to connect and then click on the public endpoint URL.
On the dashboard, go to the Infra tab and click Refresh. The dashboard lists the Managed Kubernetes clusters available to SkyPilot.

Verify that SkyPilot can access the clusters:

sky check kubernetes

The output lists the enabled contexts:

Kubernetes: enabled [compute]
  Allowed contexts:
  ├── <context_1>: enabled.
  └── <context_2>: enabled.
🎉 Enabled infra 🎉
  Kubernetes [compute]
    Allowed contexts:
    ├── <context_1>
    └── <context_2>

(Optional) For detailed per-cluster and per-node GPU availability, run:

sky show-gpus

The output shows the available GPUs and per-node availability:

GPU   REQUESTABLE_QTY_PER_NODE  UTILIZATION
H100  1, 2, 4, 8                24 of 24 free

Kubernetes per-node GPU availability
CONTEXT      NODE                       vCPU  Memory (GB)  GPU   GPU UTILIZATION  NODE STATUS
<context_1>  computeinstance-<VM_ID_1>  -     -            H100  8 of 8 free      Healthy
<context_1>  computeinstance-<VM_ID_2>  -     -            H100  8 of 8 free      Healthy

(Optional) Limit clusters which SkyPilot uses

By default, SkyPilot can place jobs on any Managed Kubernetes cluster it discovers. To restrict SkyPilot to a subset of clusters for every user of this Managed SkyPilot API Server, set kubernetes.allowed_contexts in the dashboard:

In the SkyPilot dashboard, click Configuration.
In the Edit SkyPilot API Server Configuration textbox, paste the following YAML, listing the contexts in the order in which SkyPilot should evaluate them:
```
kubernetes:
  allowed_contexts:
    - <context_1>
    - <context_2>
```
Click Apply.

To verify which contexts are enabled, run sky check kubernetes again.

Run a job

Decide how SkyPilot should choose the target Managed Kubernetes cluster:

To let SkyPilot fail over across clusters, run sky launch without specifying a cluster:

sky launch --gpus H100 --infra k8s echo 'Hello World'

SkyPilot picks the first context that satisfies the request and submits the job:

Considered resources (1 node):
----------------------------------------------------------------------------------------------------
 INFRA                       INSTANCE  vCPUs  Mem(GB)  GPUS    COST ($)  CHOSEN
----------------------------------------------------------------------------------------------------
 Kubernetes (<context_1>)    -         4      16       H100:1  0.00         ✔
----------------------------------------------------------------------------------------------------
Launching a new cluster 'sky-...'. Proceed? [Y/n]: y

To target a specific Managed Kubernetes cluster, set --infra k8s/<context>:

sky launch --gpus H100 --infra k8s/<context> echo 'Hello World'

If the targeted cluster does not have the requested resources, SkyPilot returns an error:

sky.exceptions.ResourcesUnavailableError: Kubernetes cluster does not contain any instances satisfying the request: 1x Kubernetes({'H100': 1}, region=<context>).
To fix: relax or change the resource requirements.

In the --gpus parameter, set the node group platform, such as H100, B300 or L40S. Both examples run a bash command as the entrypoint. You can also pass a YAML task definition instead. For examples, see the SkyPilot quickstart.

(Optional) Monitor jobs

To list all SkyPilot jobs created during this tutorial and their statuses, run:

sky status

To stream the logs of a job, run:

sky logs <task_name>

How to delete the created resources

Some of the created resources are chargeable. If you do not need them, delete these resources, so Nebius AI Cloud does not charge for them:

Delete all SkyPilot jobs created during this tutorial:
```
sky down --all -y
```
Delete Managed Kubernetes clusters.
If you no longer need the Managed SkyPilot API Server, delete it in the Nebius AI Cloud console. Go to AI Services → SkyPilot, open the application, go to the Settings tab and click Delete application.

InfiniBand and InfiniBand Trade Association are registered trademarks of the InfiniBand Trade Association.

Documentation Index

​Costs

​Steps

​Install dependencies

​Prepare infrastructure

​Add Managed Kubernetes clusters to SkyPilot

​(Optional) Limit clusters which SkyPilot uses

​Run a job

​(Optional) Monitor jobs

​How to delete the created resources