Polyaxon v3 is coming →
Nebius AI Cloud

Validate Nebius Managed Kubernetes with Polyaxon

Nebius Managed Kubernetes provides the cluster foundation and optional managed GPU settings. Your platform team still selects the node-group shape, driver mode, storage, interconnect, identity, labels, taints, and scaling behavior that define each capacity class.

Outcome

A Nebius capacity class exposed through Polyaxon with a documented queue, preset, and readiness operation.

Start the guideConnect a compute cluster to Polyaxon

Infrastructure responsibilities

Nebius operates the cluster foundation

Nebius manages the Kubernetes service and exposes configurable GPU node groups and integrations.

Your platform team defines the node group

Compute shape, driver mode, networking, storage, identity, labels, taints, scaling, and upgrades remain explicit choices.

Polyaxon connects the compute cluster

Installing Polyaxon Agent (compute cluster) connects this Kubernetes cluster to the control plane. Its queues and presets apply placement, connections, permissions, and lifecycle controls.

Prerequisites

  • A Nebius Managed Kubernetes cluster with a GPU node group and reviewed NVIDIA driver installation mode.
  • The required interconnect, storage, registry, DNS, service account, labels, taints, and autoscaling configuration.
  • The cluster connected to Polyaxon by installing Polyaxon Agent (compute cluster), with namespace access and a queue or preset selecting that node group.

Validate the infrastructure

  1. 1

    Validate the Nebius GPU pool

    Use the same queue and node-selection policy that will carry production workloads.

    version: 1.1kind: componentname: gpu-readinessrun:  kind: job  container:    image: nvidia/cuda:12.8.1-base-ubuntu22.04    command: ["bash", "-lc"]    args: ["nvidia-smi"]    resources:      limits:        nvidia.com/gpu: "1"

    Keep Nebius placement in the selected queue or preset. This published CUDA image checks GPU visibility only; pin a tag or digest compatible with the selected driver mode. Test InfiniBand separately when it is configured.

  2. 2

    Submit the operation

    Run the component through the target Polyaxon project, queue, preset, and approval path.

    polyaxon run -f nebius-readiness.yaml -q agent-name/queue-name
  3. 3

    Confirm device and network visibility

    Inspect the selected node, GPU inventory, interconnect devices, storage, secrets, logs, and artifact path.

    polyaxon ops dashboard

Production checklist

Record the node-group shape, driver mode, labels, taints, storage, and interconnect as one validated capacity class.
Keep cluster, node-group, compute-cluster connection, queue, and preset configuration in version control.
Revalidate the GPU, storage, identity, DNS, and network path after node-image, driver, or cluster upgrades.
Run collective communication tests only on the exact node group and interfaces used by distributed workloads.

Troubleshooting

The GPU resource is missing

Check node-group readiness, the selected driver installation mode, GPU operator or device-plugin status, and nvidia.com/gpu in node capacity.

Storage or interconnect devices are unavailable

Verify that the selected node group supports the requested feature, then inspect CSI or network components, topology constraints, mounts, and pod placement.

The connected compute cluster cannot submit or collect logs

Verify the Polyaxon Agent deployment, namespace RBAC, service-account permissions, registry access, queue routing, network policy, and control-plane connectivity.

Sources

Official platform, library, model, and Polyaxon references used by this guide.

Continue

Compare AI platformsExplore GPU orchestration