Skip to content

[Config]: standardize quoting style in Kubernetes manifests (#4353)#4359

Merged
rueian merged 2 commits intoray-project:masterfrom
DejusDevspace:refactor/kubernetes-manifests
Apr 16, 2026
Merged

[Config]: standardize quoting style in Kubernetes manifests (#4353)#4359
rueian merged 2 commits intoray-project:masterfrom
DejusDevspace:refactor/kubernetes-manifests

Conversation

@DejusDevspace
Copy link
Copy Markdown
Contributor

@DejusDevspace DejusDevspace commented Jan 8, 2026

Why are these changes needed?

This PR replaces remaining single-quoted string values in Kubernetes manifests with double quotes to align with the standardized quoting style introduced in #4353. No functional changes.

Related issue number

Closes #4353

Checks

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

Comment thread ray-operator/config/samples/ray-service.high-availability.yaml Outdated
Comment thread ray-operator/config/samples/ray-job.deletion-rules.yaml Outdated
Comment thread ray-operator/config/samples/ray-job.kueue-toy-sample.yaml Outdated
Comment thread ray-operator/config/samples/ray-cluster.fluentbit.yaml Outdated
@CheyuWu CheyuWu self-requested a review January 9, 2026 15:29
@CheyuWu
Copy link
Copy Markdown
Collaborator

CheyuWu commented Jan 9, 2026

Hi @DejusDevspace , thanks for your help!

Could you also run a search using \s*'[^']*' scoped to **/*.yaml?
I still noticed a few remaining single-quoted values.

image

@DejusDevspace
Copy link
Copy Markdown
Contributor Author

Alright. I'll do that. Thank you

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@CheyuWu @DejusDevspace Shouldn't this also be in double quotes? Same for the next line as well.

Copy link
Copy Markdown
Contributor Author

@DejusDevspace DejusDevspace Jan 10, 2026

Choose a reason for hiding this comment

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

Yes, I think it should be. I went through an earlier PR that quoted resource values in sample kubernetes manifests, and I believe this should be the same case.

I'll work on that, too. Thanks for pointing it out.

@kash2104
Copy link
Copy Markdown
Contributor

@DejusDevspace Would be better to clean up the commit history by squashing the commits into a single one.

@DejusDevspace DejusDevspace force-pushed the refactor/kubernetes-manifests branch from 74a6b11 to 0b7a897 Compare January 11, 2026 19:01
@DejusDevspace
Copy link
Copy Markdown
Contributor Author

@kash2104 Done.

@kash2104
Copy link
Copy Markdown
Contributor

@DejusDevspace Just tick the test checkboxes in the PR description.

Copy link
Copy Markdown
Member

@Future-Outlier Future-Outlier left a comment

Choose a reason for hiding this comment

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

tks

Copy link
Copy Markdown
Collaborator

@CheyuWu CheyuWu left a comment

Choose a reason for hiding this comment

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

LGTM

@DejusDevspace
Copy link
Copy Markdown
Contributor Author

@kash2104 Done.

@kash2104
Copy link
Copy Markdown
Contributor

LGTM.

@Future-Outlier Future-Outlier moved this from Done to can be merged in @Future-Outlier's kuberay project Apr 15, 2026
…es-manifests

Signed-off-by: Future-Outlier <eric901201@gmail.com>
@Future-Outlier
Copy link
Copy Markdown
Member

@codex review

@chatgpt-codex-connector
Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Bravo.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@Future-Outlier
Copy link
Copy Markdown
Member

just solved the merge conflict

requests:
cpu: 300m
memory: 1G
cpu: "300m"
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.

@Future-Outlier I think you reverted the latest changes? The latest change had this set to 1 CPU

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.

sorry, fixing

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.

ah no, I think right now the PR is correct.

the latest change we updated the "head container"'s spec, not worker container's

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.

Copy link
Copy Markdown
Member

@Future-Outlier Future-Outlier Apr 16, 2026

Choose a reason for hiding this comment

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

line 69 here is for ray worker node container

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.

this is my commit cec3a72

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.

Copy link
Copy Markdown
Member

@Future-Outlier Future-Outlier Apr 16, 2026

Choose a reason for hiding this comment

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

  1. it's not the same as [RayService][e2e] fix flaky test TestAutoscalingRayService #4702
  2. [RayService][e2e] fix flaky test TestAutoscalingRayService #4702 changes the ray head container's resource spec
  3. this PR change the ray worker container's resource spec
  4. so we can merge this!

@Future-Outlier
Copy link
Copy Markdown
Member

@codex review

@chatgpt-codex-connector
Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Breezy!

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@rueian rueian merged commit c2abb1f into ray-project:master Apr 16, 2026
31 checks passed
@github-project-automation github-project-automation bot moved this from can be merged to Done in @Future-Outlier's kuberay project Apr 16, 2026
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.

[Config] Standardize quoting style in Kubernetes manifests

6 participants