-
Notifications
You must be signed in to change notification settings - Fork 402
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
KubeRay: kubebuilder creat RayService Controller and CR #270
Conversation
) | ||
|
||
// EDIT THIS FILE! THIS IS SCAFFOLDING FOR YOU TO OWN! | ||
// NOTE: json tags are required. Any new fields you add must have json tags for the fields to be serialized. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just curious, does KubeBuilder auto-generate this file as an empty template?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This one will auto generated if init by kubebuilder. But I do not think it is total empty
ray-operator/config/crd/patches/cainjection_in_rayservice_rayservices.yaml
Outdated
Show resolved
Hide resolved
ray-operator/config/crd/patches/webhook_in_rayservice_rayservices.yaml
Outdated
Show resolved
Hide resolved
ray-operator/config/crd/patches/cainjection_in_rayservice_rayservices.yaml
Outdated
Show resolved
Hide resolved
ray-operator/config/crd/patches/webhook_in_rayservice_rayservices.yaml
Outdated
Show resolved
Hide resolved
ray-operator/config/rbac/rayservice_rayservice_editor_role.yaml
Outdated
Show resolved
Hide resolved
ray-operator/config/rbac/rayservice_rayservice_viewer_role.yaml
Outdated
Show resolved
Hide resolved
ray-operator/config/samples/rayservice_v1alpha1_rayservice.yaml
Outdated
Show resolved
Hide resolved
Great! I will have a look later today. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suggest to move unrelated changes like renaming the backend service folder name to a separate PR and leave this PR for pure service controller changes. We are using squash merge and all these changes will be squash to single commit then. |
ray-operator/config/crd/patches/webhook_in_ray_rayservices.yaml
Outdated
Show resolved
Hide resolved
#275 is merged. Let's rebase the master and update this PR. |
Thanks. I have rebased this pr. |
Nice, the diff is much cleaner now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes look clean and straightforward.
/lgtm
Seems Dmitri has approved the changed as well and now we can merge the PR |
Why are these changes needed?
We plan to add a new RayService controller. This pr does the kubebuilder create api with basic implement. No real logic yet. Once this pr merged. We will start to implement logic for RayService.
Related issue number
#214
Checks