You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the InferenceModel reconciler reconciles all InferenceModels in the configured namespace. Since the endpoint picker extension is configured for a single InferencePool name, the InferenceModel reconciler should only reconcile InferenceModels that reference, e.g. poolRef, the configured InferencePool.
InferenceModels that do not reference the configured InferencePool are deleted from the data store. Why is this approach being taken instead of filtering the watch, e.g Predicate, so the reconciler only reconciles matching InferenceModels?
The text was updated successfully, but these errors were encountered:
@kfswain may have some insights. It looks to me either approach should work?
I have another point about filtering InferenceModels in the same namespace as the InferencePool. In my opinion users should be allowed to create InferenceModels in different namespaces (think a team owns its own model and namespace). cc @ahg-g and @robscott
Currently, the InferenceModel reconciler reconciles all InferenceModels in the configured namespace. Since the endpoint picker extension is configured for a single InferencePool name, the InferenceModel reconciler should only reconcile InferenceModels that reference, e.g.
poolRef
, the configured InferencePool.InferenceModels that do not reference the configured InferencePool are deleted from the data store. Why is this approach being taken instead of filtering the watch, e.g Predicate, so the reconciler only reconciles matching InferenceModels?
The text was updated successfully, but these errors were encountered: