build(deps): bump github.com/ray-project/kuberay/ray-operator from 1.5.2 to 1.6.1

[dependabot]

Bumps github.com/ray-project/kuberay/ray-operator from 1.5.2 to 1.6.1.

Release notes

Sourced from github.com/ray-project/kuberay/ray-operator's releases.

v1.6.1

Bug fixes

• Fixed a bug where using spec.rayClusterSpec.suspend in RayService did not trigger suspend on the underlying RayCluster. This can break suspend behavior in some cases with Kueue when queueing or pre-empting RayService objects ray-project/kuberay#4739
• Fixed a bug where Volcano PodGroups can be deleted unconditionally. ray-project/kuberay#4669

Changelog

• c9ddfc2459dabc4149b8f383df2f6f6325e9b56c [Release][Helm] update KubeRay version to v1.6.1 (#4759)
• c2eea319deb6bbbe5a9da71919044293f2af6bc6 [release-1.6] cherry-pick RayService e2e test fixes (#4757)
• 947807e3e58a22b036a8b2aa274df48e3a793b5e [release-1.6] cherry-pick bug fixes for v1.6.1 (#4744)

v1.6.0

Highlights

Ray History Server (alpha)

KubeRay v1.6 introduces alpha support for the Ray History Server. This project enables users to collect and aggregate events from a Ray cluster, replaying them to restore historical snapshots of the cluster's state. By providing an alternative backend for the Ray Dashboard, the History Server allows users to view the Ray dashboard and debug ephemeral clusters (such as those managed via RayJob) even after they have been terminated.

Try the history server here: History Server Quick Start Guide.

⚠️ Warning: This feature is in alpha status, meaning future KubeRay releases may include breaking updates. We’d love to hear your experience with it! Please drop your feedback in this tracking issue to help us shape its development.

Ray Token Authentication using Kubernetes RBAC

Starting in KubeRay v1.6 and Ray v2.55, you can use Kubernetes RBAC to manage user access control to Ray clusters that have token authentication enabled. With this feature enabled, Ray will be configured to delegate token authentication to Kubernetes. This means you can use the same credentials used with Kubernetes to access Ray clusters and platform operators can use standard Kubernetes RBAC to control access to Ray clusters. See Configure Ray clusters to use Kubernetes RBAC authentication for a step-by-step guide.

You can now also reference Secrets containing static auth tokens for Ray cluster token authentication.

apiVersion: v1
kind: Secret
metadata:
  name: ray-cluster-token
type: Opaque
stringData:
  auth_token: "super-secret-example-token"
---
apiVersion: ray.io/v1
kind: RayCluster
metadata:
  name: ray-cluster-with-auth
spec:
  authOptions:
    mode: token
    secretName: ray-cluster-token
  rayVersion: '2.53.0'
  headGroupSpec:
    rayStartParams: {}

... (truncated)

Commits

• c9ddfc2 [Release][Helm] update KubeRay version to v1.6.1 (#4759)
• c2eea31 [release-1.6] cherry-pick RayService e2e test fixes (#4757)
• 947807e [release-1.6] cherry-pick bug fixes for v1.6.1 (#4744)
• 3fe72c3 [Release][Helm] update KubeRay version to v1.6.0 (#4622)
• 0a9eabd [Release] Sync master changes to release-1.6 (#4600)
• b0c43fd [Release] Update KubeRay version references for 1.6.0 (#4586)
• e50aafc Disable RayMultiHostIndexing feature for TestReconcile_Multihost_Replicas (#4...
• 6652c36 Promote RayMultiHostIndexing feature to Beta (#4572)
• 0983367 Include serve-x prefixed ports in ray serve service for grpc support (#4558)
• b9a8dc0 [CronJob] Add RayCronJob related YAML (#4577)
• Additional commits viewable in compare view

[dependabot]

Superseded by #7581.