Introducing KubeRay v1.6 and v1.7

KubeRay v1.6 and v1.7 introduce a broad set of improvements for operating Ray workloads on Kubernetes, incorporating more than 381 commits from roughly 75 contributors. Major additions include the beta KubeRay History Server, which preserves logs, events, Ray Data datasets, and Ray Serve application information after clusters are deleted, alongside automated collector sidecar injection and compatibility with token-authenticated clusters. Security enhancements add native NetworkPolicy configuration, cert-manager-based mTLS certificate automation, and Kubernetes RBAC-based token authentication, while RayService incremental upgrades gain beta status with rollback support. The releases also add cron-based RayJob scheduling, independently restartable job-submitter sidecars, improved job cleanup policies, a RayCluster recreate upgrade strategy, configurable Ingress settings, Autoscaler V2 worker-group priorities, and beta stable indexing for multi-host workers. For fault tolerance, KubeRay supports an embedded RocksDB backend for Ray GCS to reduce dependence on external Redis, improves Redis cleanup handling during deletion, and surfaces Kubernetes platform events in the Ray Dashboard to aid infrastructure troubleshooting.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.