<p>Experiencing an odd issue with KubernetesPodOperator on Airflow 1.1.14.</p>
<p>Essentially for some jobs Airflow is losing contact with the pod it creates.</p>
<p><code>[2021-02-10 07:30:13,657] {taskinstance.py:1150} ERROR - ('Connection broken: IncompleteRead(0 bytes read)', IncompleteRead(0 bytes read))</code></p>
<p>When I check logs in kubernetes with <code>kubectl logs</code> I can see that the job carried on past the connection broken error.</p>
<p>The connection broken error seems to happen exactly 1 hour after the last logs that Airflow pulls from the pod (we do have a 1 hour config on connections), but the pod keeps running happily in the background.</p>
<p>I've seen this behaviour repeatedly, and it tends to happen with longer running jobs with a gap in the log output, but I have no other leads. Happy to update the question if certain specifics are misssing.</p>

jabberwocky
<p>As I have mentioned in comments section I think you can try to set operators  <code>get_logs</code>  parameter to  <code>False</code>  - default value is  <code>True</code> .</p>
<p>Take a look:  <a href="https://stackoverflow.com/questions/55176707/airflow-worker-connection-broken-incompleteread0-bytes-read">airflow-connection-broken</a>,  <a href="https://issues.apache.org/jira/browse/AIRFLOW-3534" rel="nofollow noreferrer">airflow-connection-issue</a> .</p>
