An AnyScale explainer says KubeRay brings RayCluster, RayJob and RayService to Kubernetes-native lifecycle management and autoscaling.
An AnyScale explainer says KubeRay is the Kubernetes-native layer for running Ray at scale, tying Ray clusters, batch jobs and serving workloads into the infrastructure many teams already operate. The material frames KubeRay as the standard way to run Ray on Kubernetes and says it underpins managed Ray offerings from major cloud providers.
According to the source material, the core problem is that Kubernetes understands Pods, Services and Jobs, but not a Ray cluster, Ray job or Ray Serve application. Without an operator layer, teams must hand-build the same plumbing for head and worker deployments, job submission, autoscaling and failure recovery. KubeRay is presented as the bridge: it turns a RayCluster spec into the necessary Pods and Services, and reports Ray state back to Kubernetes through status fields and Events.
The explainer says KubeRay provides three main custom resources. RayCluster is the building block for long-running clusters. RayJob creates a dedicated RayCluster for a single batch workload and tears it down when the job finishes. RayService manages Ray Serve applications with high availability and zero-downtime upgrades. The source also describes RayCronJob for recurring Ray jobs.
For scaling and resilience, the material says KubeRay adds Ray-aware autoscaling based on pending tasks, actors and placement groups, rather than relying only on the Kubernetes Horizontal Pod Autoscaler. It also cites Global Control Service fault tolerance for recovering cluster metadata after a head-node failure while keeping Ray Serve applications running.
Source link
