-
Notifications
You must be signed in to change notification settings - Fork 267
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
Enhance the model adapter stability to alpha grade #136
Comments
Few follow-ups
|
Stability ImprovementScenario 0: Any status issue or unloaded issues.
unloaded issues are normally related to pod restart etc and the lora information is missing. Now Pod watch has been corrected and all related issues should be resolved. Status issue should be resolved for most of major workflow. This needs more improvement later Scenario 1: Delete base model, then delete loraStill running, this is definitely a bug, it should enqueue the right model adapter objects. then it could update the status. Scenarios 2: Create adapter, Delete adapter, Create adapter.#239 reproducible Scenarios 3: Failed to delete model adapter which take long time |
Scenarios 3: partial pods in terminating status and apply the the adapter
|
Misc 1: model adapter didn't filter out unrelated pods (resolved) #255
unrelated pods should be filtered out. This is because the model adapter controller |
Misc 2: base model pod event can not trigger adapter reconciliationSince the pod is not owned by the modelAdapter, we can not that easily trigger the adapter reconciliation. It should check reverse lookup adapter list. which one status has this pod name, then put that model adapter in the queue
https://book-v1.book.kubebuilder.io/basics/simple_controller |
Misc 3: Create lora always experience the object outdated issue
|
🚀 Feature Description and Motivation
Use Case
No response
Proposed Solution
No response
The text was updated successfully, but these errors were encountered: