Download Latest Version v1.7.0 source code.zip (11.2 MB)
Email in envelope

Get an email when there's a new version of KubeRay

Home / v1.7.0
Name Modified Size InfoDownloads / Week
Parent folder
kuberay_1.7.0_checksums.txt 2026-08-20 418 Bytes
0
kubectl-ray_v1.7.0_darwin_amd64.tar.gz 2026-08-20 34.9 MB
0
kubectl-ray_v1.7.0_darwin_arm64.tar.gz 2026-08-20 33.0 MB
1 1 weekly downloads
kubectl-ray_v1.7.0_linux_amd64.tar.gz 2026-08-20 32.9 MB
0
kubectl-ray_v1.7.0_linux_arm64.tar.gz 2026-08-20 30.2 MB
1 1 weekly downloads
README.md 2026-08-20 34.3 kB
0
v1.7.0 source code.tar.gz 2026-08-20 10.5 MB
0
v1.7.0 source code.zip 2026-08-20 11.2 MB
1 1 weekly downloads
Totals: 8 Items   152.7 MB 3

Highlights

Ray History Server (beta)

The Ray History Server is graduating to beta. Introduced as alpha in KubeRay v1.6, the History Server lets you view the Ray Dashboard and debug ephemeral clusters (such as those managed by RayJob) even after they have been terminated.

Since v1.6, the History Server has received major improvements:

  • Performance and scalability: lazy loading, an LRU byte-based session cache, a disk-first event storage pipeline, and event compression significantly reduce memory usage for both the collector and the server.
  • Ray token authentication support for both the collector and live-cluster proxying.
  • Better UI and API coverage: a cluster selection page, task logs, and Serve / placement group / Ray Data endpoints polled by default.
  • History Server images are now published to quay.io/kuberay (historyserver:v1.7.0 and collector:v1.7.0)

Try it here: History Server Quick Start Guide.

Automatic History Server Sidecar Configuration (alpha)

The operator can now automatically inject the History Server event collector sidecar into your RayCluster’s pods, no manual sidecar configuration needed. Enable the RayClusterHistoryServer feature gate on the operator and set spec.historyServerOptions on your RayCluster:

apiVersion: ray.io/v1
kind: RayCluster
metadata:
  name: raycluster-historyserver
spec:
  historyServerOptions:
    collectorOptions:
      image: quay.io/kuberay/collector:v1.7.0

See ray-cluster.historyserver.yaml (github.com) for a full example.

:warning: Warning: RayClusterHistoryServer is an Alpha feature and is disabled by default. To enable it, set the feature gate on the kuberay-operator:
--feature-gates=RayClusterHistoryServer=true

RayService Incremental Upgrade graduates to Beta

The RayServiceIncrementalUpgrade feature gate is now beta and enabled by default. This feature allows RayService to perform zero-downtime upgrades by gradually shifting traffic to the new cluster using the Kubernetes Gateway API, instead of requiring 2x resources for a blue/green switch.

Since its Alpha release, the feature has received several improvements for more reliable and robust upgrades, including:

  • Rollback support: Users can now revert the RayService spec mid-upgrade, with safe traffic shifting between the pending and active clusters.
  • Improved reliability: Improved capacity management, traffic migration, failure handling, and cluster cleanup during incremental upgrades.
  • E2E test coverage: Expanded test scenarios to improve coverage.

mTLS support via cert-manager (alpha)

KubeRay v1.7 can automatically provision and rotate certificates for mutual TLS between RayCluster’s pods using cert-manager.

:warning: Warning: RayClusterMTLS is an Alpha feature and is disabled by default. To enable it, set the feature gate on the kuberay-operator:
--feature-gates=RayClusterMTLS=true

Enable mTLS feature with following to try this feature:

apiVersion: ray.io/v1
kind: RayCluster
metadata:
  name: raycluster-mtls
spec:
  rayVersion: '2.55.1'
  tlsOptions:
    enabled: true

See ray-cluster.mtls.yaml (github.com) for a full example.

NetworkPolicy support for RayCluster (alpha)

KubeRay v1.7 adds a new spec.networkPolicy field to RayCluster for network isolation. When set, the operator creates separate NetworkPolicies for head and worker pods, with configurable modes (DenyAll, DenyAllIngress, DenyAllEgress) and per-worker-group ingress/egress rules. Intra-cluster pod-to-pod traffic is always permitted.

Try it here: Network Policy Quick Start Guide.

:warning: Warning: RayClusterNetworkPolicy is an Alpha feature and is disabled by default. To enable it, set the feature gate on the kuberay-operator:
--feature-gates=RayClusterNetworkPolicy=true

Below is an example of enabling network policy feature:

apiVersion: ray.io/v1
kind: RayCluster
spec:
  networkPolicy:
    mode: DenyAll
   head:
      ingressRules:

      - from:
        - namespaceSelector:
            matchLabels:
              kubernetes.io/metadata.name: <prometheus-namespace>
        ports:
        - port: 8080
          protocol: TCP

See ray-cluster.network-policy-deny-all.yaml (github.com) for an example.

GCS fault tolerance with embedded storage (alpha)

GCS fault tolerance no longer requires an external Redis. With the GCSFaultToleranceEmbeddedStorage feature gate enabled, you can persist GCS metadata in an embedded RocksDB store backed by a persistent volume on the head Pod:

spec:
  gcsFaultToleranceOptions:
    backend: rocksdb
    storage:
      size: 1Gi

:warning: Warning: GCSFaultToleranceEmbeddedStorage is an Alpha feature and is disabled by default. To enable it, set the feature gate on the kuberay-operator:
--feature-gates=GCSFaultToleranceEmbeddedStorage=true

See ray-cluster.embedded-gcs-ft.yaml (github.com) for a full example.

Other Notable Features

  • RayCluster now supports built-in Ingress configuration via headGroupSpec.ingressOptions with host, path, pathType, and tls fields.
  • RayCronJob now supports the spec.timeZone field, and child RayJobs use deterministic names to prevent duplicate firings.
  • The WorkerGroup API includes a new priority field for scheduler integrations.
  • A new alpha feature gate SidecarSubmitterRestart prevents premature job termination during transient head Pod resource spikes in RayJob sidecar mode.
  • The operator configuration supports defaultPodAnnotations and defaultPodLabels applied to all Ray Pods.
  • Memory usage improvements in the operator: Pod informer cache selectors and more efficient pod resource calculation.
  • kubectl ray logs support --gke-link to print a Cloud Logging link on GKE.
  • Upgraded to Go 1.26; Grafana dashboards updated for Ray 2.56.

Breaking Changes

  • Helm: in the kuberay-operator chart, metrics.serviceMonitor.selector has been renamed to metrics.serviceMonitor.additionalLabels, and empty labels are no longer emitted (#4979). Update your values file if you set this field.
  • History Server (alpha to beta): configuration has changed since the v1.6 alpha. S3 credentials now use the standard AWS environment variables (AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, ...) instead of AWS_S3ID/AWS_S3SECRET/AWS_S3TOKEN (#4665), the runtime-class flag has been replaced by --storage-backend (#5085), and the on-storage event layout has changed (#4670). Redeploy the collector and history server together on v1.7 and see the updated setup guide.

Deprecations

  • The ray.io/v1alpha1 API version is now marked deprecated (#5122). Please migrate to ray.io/v1.

Changelog

Full Changelog: https://github.com/ray-project/kuberay/compare/v1.6.2...v1.7.0

Source: README.md, updated 2026-08-20