<p><a href="https://cloud.google.com/composer/docs/how-to/using/using-kubernetes-pod-operator" rel="nofollow noreferrer">The Cloud Composer documentation</a> explicitly states that:</p>

<blockquote>
  <p>Due to an issue with the Kubernetes Python client library, your Kubernetes pods should be designed to take no more than an hour to run.</p>
</blockquote>

<p>However, it doesn't provide any more context than that, and I can't find a definitively relevant issue on the Kubernetes Python client project.</p>

<p>To test it, I ran a pod for two hours and saw no problems. What issue creates this restriction, and how does it manifest? </p>

Mike Precup
<p><a href="https://issues.apache.org/jira/browse/AIRFLOW-3253" rel="nofollow noreferrer">https://issues.apache.org/jira/browse/AIRFLOW-3253</a> is the reason (and hopefully, my fix will be merged soon). As the others suggested, this affects anyone using the Kubernetes Python client with GCP auth. If you are authenticating with a Kubernetes service account, you should see no problem.</p>

<p>If you are authenticating via a GCP service account with gcloud (e.g. using the GKEPodOperator), you will generally see this problem with jobs that take longer than an hour because the auth token expires after an hour.</p>
