When Workspace fails to pull an image it results in a K8s image_pull_error not visible to the end user
MR: Pending
Description
Insights as a result of this work: Provide support to use images from private cont... (&14664 - closed)
When we attempt to pull an image on the agent side for a workspace but fail to do so, we get an ImagePullBackOff that is not reported as a failed state to the rails side. This leads to the workspace being stuck on the creating state on the UI, even though we could not pull the image.
I think this error is not reported by the applier that applies the manifests, but rather as a field present in the pod status. It could maybe be an intermittent failure that k8s resolves on retry, if so we may need to determine after how long a "pull" operation can last before we report it as fail (or piggyback on something Kubernetes already exposes for this)
Acceptance Criteria
-
Report image pull errors that have reached the retry limit to the rails side and by extension the UI.