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
Right now, if we start a pod but it doesn't successfully launch in the launch timeout, we just sort of let it exist forever, in an orphaned state. This is very problematic!
We should make sure we clean up after ourselves if we do not launch in time.
The text was updated successfully, but these errors were encountered:
You can repro this by doing something like having a wrong image name in the config or an image that takes longer to download than the configured timeout. It will make it impossible for the user to launch until the pod is manually deleted.
Right now, if we start a pod but it doesn't successfully launch in the launch timeout, we just sort of let it exist forever, in an orphaned state. This is very problematic!
We should make sure we clean up after ourselves if we do not launch in time.
The text was updated successfully, but these errors were encountered: