GitHub user suvorom added a comment to the discussion: Airflow 3.0.6 Kubernetes Executor Fails on First "ErrImagePull"
> I guess my question is overall around the Airflow Kubernetes Executor's > function. If the task has an ErrImagePull, should it really mark the task as > failed? Since it could retry again and retrieve the image? Exactly, Kubernetes does the successful pull retry in most cases, but the task is already marked as failed. GitHub link: https://github.com/apache/airflow/discussions/56049#discussioncomment-14803068 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
