ray-project/kuberay

Description We have a constant defined in: kuberay/ray-operator/controllers/ray/utils/constant.go Lines 197 to 198 in 8614968 // RAY_AUTH_TOKEN_SECRET_KEY is the key used in the Secret containing Ray auth token RAY_AUTH_TOKEN_SECRET_KEY = "auth_token" But there are still some places use hard-coded "auth_token". They should all use the constant. Here are files that contains hard-coded value: ray-operator/controllers/ray/raycluster_controller.go ray-operator/controllers/ray/raycluster_controller_unit_test.go kubectl-plugin/pkg/cmd/get/get_token_test.go

Follow-ups after the History Server e2e switched from MinIO to RustFS (#5339). Cleanup Update the History Server docs to use RustFS instead of MinIO Remove historyserver/config/minio.yaml

Description Related to #5347 (comment). With Ray < 2.58, the task detail page cannot show task logs. We should bump the Ray image in the history server example YAMLs and e2e test data from 2.56.0 to 2.58.0. Tasks: Update YAMLs in historyserver/config/ and historyserver/test/testdata/ to use Ray version 2.58 Can use command like this to update all of them at once. Need to manually validate the result grep -rl "rayproject/ray:2.56.0" historyserver/config historyserver/test/testdata | xargs sed -i '' 's#rayproject/ray:2.56.0#rayproject/ray:2.58.0#g' Update History server docs prerequisite section https://docs.ray.io/en/latest/cluster/kubernetes/user-guides/kuberay-history-server.html#prerequisites in Ray repo

Search before asking I had searched in the issues and found no similar feature requirement. KubeRay Component ray-operator Description RayClusterMetricsManager emits rayClusterConditionProvisioned in Collect(), but its Desc is not included in Describe(): kuberay/ray-operator/controllers/ray/metrics/ray_cluster_metrics.go Lines 23 to 30 in f72fa09 // RayClusterMetricsManager implements the prometheus.Collector and RayClusterMetricsObserver interface to collect ray cluster metrics. type RayClusterMetricsManager struct { rayClusterProvisionedDurationSeconds *prometheus.GaugeVec rayClusterInfo *prometheus.Desc rayClusterConditionProvisioned *prometheus.Desc

Search before asking I searched the issues and found no similar issues. KubeRay Component ray-operator KubeRay Version main Ray Version No response Environment N/A What happened + What you expected to happen The operator supports configuring the log encoder in two ways: Command-line flags Config file When using --config, the logStdoutEncoder and logFileEncoder are loaded into config, but main.go still uses the flag variables directly when creating the encoders: kuberay/ray-operator/main.go Lines 168 to 181 in f72fa09 stdoutEncoder, err := newLogEncoder(logStdoutEncoder) exitOnError(err, "failed to create log encoder for stdout") opts.Encoder = stdoutEncoder if config.LogFile != "" {