Various infrastructure issues might lead into ImagePullBackOff or CrashLoopBackOff. We are not sure what how does ArgoCD handle these, so it needs to be investigated and potential problem mitigation should be documented.
From what I have seen, ArgoCD sees & reports these in the UI, but does not care otherwise. The manifests that ArgoCD syncs are on a higher level (e.g. Deployments, etc...).
Various infrastructure issues might lead into ImagePullBackOff or CrashLoopBackOff. We are not sure what how does ArgoCD handle these, so it needs to be investigated and potential problem mitigation should be documented.