[Bug] `RayClusterSpec.historyServerOptions.collectorOptions` do not expose `securityContext`

[danielgafni]

Search before asking

• I searched the issues and found no similar issues.

KubeRay Component

historyserver

KubeRay Version

v1.7.0

Ray Version

2.56.1

Environment

Isn't relevant

What happened + What you expected to happen

The new collectorOptions setting for RayClusterSpec. historyServerOptions do not expose securityContext , which is often needed to configure the container.

I think securityContext should be exposed.

Reproduction script

Isn't relevant

Anything else

For example, the collector currently fails if if Ray is running under root user (because the collector uses uid 1000)

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

[win5923]

cc @chiayi
I think this makes sense.

[danielgafni]

Thanks! while we're at it please expose as many fields as possible :) volume mounts etc

By the way, I guess another issue is the fact that problems with the collector container startup cause the entire pod to fail - is this intended?

[yindia]

I'd like to pick this up. I looked at the code and it's a small additive gap: CollectorOptions in raycluster_types.go exposes image, imagePullPolicy, resources, and env, but BuildCollectorContainer never sets a securityContext on the collector sidecar, so there's no way to run it as a non-1000 uid.

Proposed change:

• add SecurityContext *corev1.SecurityContext to CollectorOptions (pointer with omitempty, so existing specs are unaffected)
• set container.SecurityContext from it in BuildCollectorContainer
• regenerate the CRDs, deepcopy, and api-docs, then sync the helm CRDs
• add a pod_test.go case asserting the collector container picks up the securityContext

On @danielgafni's point about exposing more fields: I'd keep this PR to securityContext since that's the reported bug, and handle volumeMounts (which also needs volumes) as a follow-up so the API change stays reviewable. Happy to do both here if you'd prefer.

Does this approach look right? If so I'll open the PR.