Segal Clusters
Coordinate application workloads through a managed Kubernetes cluster and explicitly sized node pools.
Engineering-led activation. Production access depends on an authorized provider account, a customer-specific service binding and confirmed availability.
How the service fits.
Kubernetes clusters and worker node pools. This is not a promise of a dedicated NVLink or InfiniBand fabric.
- 1
Create a dedicated cluster in the customer’s project
- 2
Attach the required CPU or GPU-capable node pools
- 3
Deploy workloads with persistent volumes and network policies
Service architecture
- Control plane and worker-node responsibilities are separate
- Container images come from a controlled registry
- GPU scheduling requires the appropriate device integration
Operating boundaries
- A Kubernetes cluster is not a guaranteed NVLink domain
- Interconnect and GPU topology need a workload-specific review
- Cluster and node-pool lifecycle can incur separate charges
Deployment & support
Segal provides the branded service experience and coordinates configuration, support and commercial scope. The infrastructure service is supplied through OVHcloud; provider eligibility and applicable service terms must be confirmed before activation.
Upstream service: Managed Kubernetes Service. Provider specifications were reviewed on 24 October 2026; actual inventory and quota are checked separately.
Upstream technical reference