As mentioned by Krengifo this could be due to insufficient resources.

When running with a Kubernetes Executor, if the task's state is changed externally, you should check the pod status and logs in kubernetes.

You'll find the pod id in the airflow logs, then can check for more info with:

kubectl describe pods <pod-id>