Skip to content

ray-operator: disallow overriding Serve Service names#4954

Open
andrewsykim wants to merge 2 commits into
ray-project:masterfrom
andrewsykim:fix-service-name-override
Open

ray-operator: disallow overriding Serve Service names#4954
andrewsykim wants to merge 2 commits into
ray-project:masterfrom
andrewsykim:fix-service-name-override

Conversation

@andrewsykim

Copy link
Copy Markdown
Member

Why are these changes needed?

Similar to how we have validation for Head Services to disallow name overrides, we should similarly have validation for Serve services. The embedded Service is for overriding fields in Service.Spec but not the name itself.

Related issue number

Checks

  • I've made sure the tests are passing.
  • Testing Strategy
    • Unit tests
    • Manual tests
    • This PR is not tested :(

Signed-off-by: Andrew Sy Kim <andrewsy@google.com>
@andrewsykim andrewsykim force-pushed the fix-service-name-override branch from 85eb1a2 to 36d3257 Compare June 29, 2026 16:43
Signed-off-by: Andrew Sy Kim <andrewsy@google.com>

@win5923 win5923 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is a breaking change for users who rely on spec.serveService.metadata.name. Would it make sense to first emit a warning indicating that this will be rejected in the next release?

@andrewsykim

Copy link
Copy Markdown
Member Author

Do you know any users using this? I was worried about that too initially, but we don't allow overriding Service name for HeadService.

@win5923

win5923 commented Jun 30, 2026

Copy link
Copy Markdown
Member

IDK, but i agree this change. We could remove this sample YAML as well, or just remove the name field.
https://github.com/ray-project/kuberay/blob/master/ray-operator/config/samples/ray-service.custom-serve-service.yaml

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants