<p>I have an image of size of 6.5GB in the Google Container Registry. When I try to pull the image on a Kubernetes cluster node(worker node) via a deployment, an error occurs: ErrImagePull(or sometimes ImagePullBackOff). I used the describe command to see the error in detail. The error is described as <strong>Failed to pull image "gcr.io/.../.. ": rpc error: code = Canceled desc = context canceled</strong>
What may be the issue and how to mitigate it?</p>

<p>It seems that the kubelet expects a updates on progress during the pull of a large image but this currently isn't available by default with most container registries. It's not ideal behaviour but it appears people have been able to work around it from reading the responses on <a href="https://github.com/kubernetes/kubernetes/issues/59376" rel="noreferrer">https://github.com/kubernetes/kubernetes/issues/59376</a> and <a href="https://stackoverflow.com/questions/43342014/kubernetes-set-a-timeout-limit-on-image-pulls">Kubernetes set a timeout limit on image pulls</a> by adjusting the timeout</p>
