Skip to content

[apiserver] Add migration doc from v1 to v2 #3812

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 9 commits into
base: master
Choose a base branch
from

Conversation

nadongjun
Copy link
Contributor

Why are these changes needed?

Related issue number

Closes #3607

Checks

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

Co-authored-by: Jun-Hao Wan <[email protected]>
Signed-off-by: Dongjun Na <[email protected]>
@dentiny
Copy link
Contributor

dentiny commented Jul 23, 2025

CC @rueian / @kevin85421

Copy link
Contributor

@dentiny dentiny left a comment

Choose a reason for hiding this comment

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

Thanks for the doc! I think it's clear and concise.
Meanwhile, as I commented in the google doc, do we plan to add some examples on code migration?


With v2, we eliminate these bottlenecks by directly reusing the OpenAPI schema defined in the Kubernetes CRDs.
Instead of manually defining fields or generating new clients, v2 acts as a transparent HTTP proxy to the
Kubernetes API server. All CRD fields are exposed by default, and advanced behaviors such as compute template
Copy link
Contributor

Choose a reason for hiding this comment

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

just for my own curiosity (not request to change), why do we manually break lines, instead of writing a long line, which automatically breaks into multiple lines when display?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Oh I see — I didn’t know that. Thanks for the explanation.


## Dev Progress

- Not all v2 features will ship in the kuberay v1.4 release
Copy link
Contributor

Choose a reason for hiding this comment

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

CC @rueian do we want a timeline for v2 release?

Copy link
Contributor

Choose a reason for hiding this comment

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

I guess the timeline can be:

  1. We try to support compute templates in KubeRay 1.5.0, but still keep the API server v2 in Alpha.
  2. Announce Beta since KubeRay 1.6.0

nadongjun and others added 6 commits July 25, 2025 17:11
Co-authored-by: Nary Yeh <[email protected]>
Signed-off-by: Dongjun Na <[email protected]>
Co-authored-by: Nary Yeh <[email protected]>
Signed-off-by: Dongjun Na <[email protected]>
Co-authored-by: Nary Yeh <[email protected]>
Signed-off-by: Dongjun Na <[email protected]>
Co-authored-by: Nary Yeh <[email protected]>
Signed-off-by: Dongjun Na <[email protected]>
Co-authored-by: Nary Yeh <[email protected]>
Signed-off-by: Dongjun Na <[email protected]>
Co-authored-by: Nary Yeh <[email protected]>
Signed-off-by: Dongjun Na <[email protected]>
@nadongjun
Copy link
Contributor Author

@machichima Nice catch, thanks!


## Dev Progress

- Not all v2 features will ship in the kuberay v1.4 release
Copy link
Contributor

Choose a reason for hiding this comment

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

I guess the timeline can be:

  1. We try to support compute templates in KubeRay 1.5.0, but still keep the API server v2 in Alpha.
  2. Announce Beta since KubeRay 1.6.0

Co-authored-by: Rueian <[email protected]>
Signed-off-by: Dongjun Na <[email protected]>
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.

[Feature] [apiserver] Provide migration doc from v1 to v2
5 participants