-
Notifications
You must be signed in to change notification settings - Fork 59
LLMServerPool Implementation #36
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
LLMServerPool Implementation #36
Conversation
/hold |
/label tide/merge-method-squash |
1a3ab93
to
790d3a2
Compare
/unhold |
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.
We should use controller-runtime instead of creating and managing workqueues and informerFactory etc. https://github.com/kubernetes-sigs/controller-runtime
See the example here, it is simpler: https://github.com/kubernetes-sigs/controller-runtime/blob/main/examples/crd/main.go
7db0c98
to
741da3d
Compare
42c2f72
to
cc30945
Compare
cc30945
to
583fd27
Compare
583fd27
to
e9617a9
Compare
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 started to review this, but it seems this is still in development, right?
/hold just so this doesn't get merged by mistake |
Yes, I should have put a hold on it (ty for that). I'll take the hold off when it's complete. |
e9617a9
to
133349f
Compare
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kfswain The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
} | ||
klog.V(1).Info("reconciling LLMServerPool", req.NamespacedName) | ||
|
||
serverPool := &v1alpha1.LLMServerPool{} |
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.
aren't we supposed to create a Service here?
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 realized that it would be confusing to have the EPP reconcile and create an object on the LLMServerPool's behalf, in addition to whatever controller created the EPP. Instead, the implementation of the LLMServerPool controller should create the service and pass the service name in on startup. I think centralizing the object creation/control will make for a cleaner interface/experience
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.
Leaving this comment unresolved for posterity. But discussed further offline. And it sounds like we are in agreement here
133349f
to
72bcadc
Compare
72bcadc
to
37da3e5
Compare
/unhold |
/lgtm |
Implementation to integrate LLMServerPool and Pod reconciliation into the I-GW EndpointPicker(ext-proc)