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
In the previous version, you updated the Helm chart to support labels, which work correctly for the Models. However, the pods don't have the proper labels applied to them. Is there a way to ensure the labels propagate to the pods as well?
Thanks
The text was updated successfully, but these errors were encountered:
Our helm chart includes tenancy labels and we see them on model resources, but they are not being applied to the model pods, and it seems like the kubeai server is looking for labels on the model pods (not only on the model resources) for its multi-tenancy features.
First of all, sorry about the delayed response, we had a lapse in Issue support.
@nestoras KubeAI does not propagate Model labels to the Pods that are created to serve that Model. I think it probably makes sense to pass those along.
@nason Can you elaborate on this: it seems like the kubeai server is looking for labels on the model pods? The check for label selectors (tenancy labels - referring to this doc) lives here and checks the Model's labels.
In the previous version, you updated the Helm chart to support labels, which work correctly for the Models. However, the pods don't have the proper labels applied to them. Is there a way to ensure the labels propagate to the pods as well?
Thanks
The text was updated successfully, but these errors were encountered: