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
As of now, instaslice only supports one container per pod to request GPU access. However, from the code it appears that this one container also needs to be the first container in the list of containers in the pod. This seems rather restrictive and unnecessary. Instaslice should be able to go over the list of containers of the pod and select the one that is requesting the GPU access irrespective of the order it is declared in the pod definition.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
/remove-lifecycle stale
openshift-cibot
added
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
and removed
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
labels
Feb 8, 2025
As of now,
instaslice
only supports one container per pod to request GPU access. However, from the code it appears that this one container also needs to be the first container in the list of containers in the pod. This seems rather restrictive and unnecessary. Instaslice should be able to go over the list of containers of the pod and select the one that is requesting the GPU access irrespective of the order it is declared in the pod definition./cc @rphillips
The text was updated successfully, but these errors were encountered: