GitHub user ahipp13 added a comment to the discussion: Airflow 3.0.6 Kubernetes Executor Fails on First "ErrImagePull"
@aongxsss thank you for your reply. I have everything set to always just in case of important security updates, but we usually re-name the image when we make these updates, so I think IfNotPresent should hopefully work better. 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? I am not too familiar with this backend process which is why I wanted to pose the question in a discussion. Because right now what is happening is my task technically runs after getting an image, but since it ErrImagePull once or twice it just thinks it failed when it really didn't. GitHub link: https://github.com/apache/airflow/discussions/56049#discussioncomment-14566815 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
