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

[dependabot]

Bumps github.com/ray-project/kuberay/ray-operator from 1.6.2 to 1.7.0.

Release notes

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

v1.7.0

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 for a full example.

⚠️ 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)

... (truncated)

Commits

• 59d663a yaml: bump to 1.7.0 (#5176)
• 7f4c2fc [release-1.7] cherry picks for v1.7.0 (#5163)
• 067ba6d [release-1.7] cherry picks for v1.7.0 (#5159)
• 1339663 [history server] rename session-cache-max-bytes to session-cache-max-memory (...
• 97509c3 [CRD] Mark ray.io/v1alpha1 as a deprecated API version (#5122)
• bf50aa1 [History server] Update RAY_ROOT_DIR TO STORAGE_ROOT_DIR and examples to ...
• 7065599 [History Server] Support Ray 2.56 task log info (#5125)
• e6bb292 test: cache and retry for helm pull prometheus to prevent flakiness (#5136)
• 9908ecb Bump x/net version used by ray-operator to latest (0.57.0) to address CVEs (#...
• d77dadd [History Server] Poll Serve, placement group, and Ray Data endpoints by defau...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)