Kubernetes cluster

Put your Kubernetes cluster to work for the team

Build or connect a Kubernetes cluster on the platform; users simply create a project, press Run and read the results.

Talk to our team

Build a cluster

Kubernetes Illustration

Platform Job

Master Node 01

VIP Master Node 02

Master Node 03

Worker Node 01

Worker Node 02

Worker Node 03

Build a cluster

A cluster in a few clicks from the console

No config files, no commands to memorise. Pick the machines, assign roles and press Create — the platform installs Kubernetes, the GPU components and shared storage in one go.

Pick machines

Tick the machines and the shared storage for the cluster.

Pick machines
Master Nodes and VIP

Choose the Master Nodes; several Masters share one VIP, so the cluster keeps running if one goes down.

Master Nodes and VIP
Name and storage

Name the cluster and choose the shared storage for project data.

Name and storage
Final check

Every machine's system, network and disk are checked at once, and any problem is explained on the spot.

Final check
Create

Watch every step's progress; machines with graphics cards get the GPU Operator automatically.

Create
Done

The cluster appears on the platform, ready for projects.

Done

Connect a cluster

Already have a cluster? Connect it

Paste an administrator's settings once. The platform sets up its own working area in the cluster and stays inside it, leaving your existing services alone.

Paste administrator settings

Get the settings from your cluster administrator and paste them into the platform once.
Set up the platform’s area

The platform sets up its own working area in the cluster, leaving your existing services alone.
Give projects their own space and quota

Administrators decide how much CPU, memory and GPU each project may use.

Everyday operation

Everyday cluster care, from the console

From changing nodes to backup and restore, administrators follow progress in one place.

Add or remove nodes

Add machines when you need more computing power, or remove nodes you no longer use.

Rolling upgrades

Upgrade nodes in sequence and follow each step in the console.

Backup and restore

Back up the cluster and restore it from the console when needed.

Automatic upkeep

Routine upkeep runs automatically; administrators check its status in the console.

Offline installation

Prepare the installation files in advance to build a cluster without internet access.

Console cluster management: nodes, upgrades, backup and restore

GPU

Share a single GPU

Administrators decide how many cards each project may use and whether it has them to itself or shares them; cards that support MIG can be split into several parts. One screen shows usage on Docker hosts and clusters alike.

GPU Operator, installed automatically

Machines with graphics cards get the GPU Operator automatically.

Exclusive

A whole card for one project.

Shared

Projects take turns; the platform queues the jobs.

MIG partitions

One card split into parts for several jobs at once.

GPU Monitor: graphics cards on Docker hosts and clusters on one page

Cluster tools

See the cluster and every run

Check cluster status and job results inside the platform.

Cluster K8s Manager

Browse workloads, nodes and events to see how the cluster is running.

Run a job on the cluster

The same form, the same results, the same terminal. Job outputs land in the project folder.

Shared storage

Your data follows the job

Register a NAS once in the console and every host and cluster node mounts it. Whichever machine runs the job, it reads the same project folder.

Start with one machine, grow to a whole cluster

Ready as soon as it is installed; add hosts or a cluster when you need more.

Talk to our team

Talk to us

Put your Kubernetes cluster to work for the team

A cluster in a few clicks from the console

Pick machines

Master Nodes and VIP

Name and storage

Final check

Create

Done