<p>Installed airflow in kubernetes using the repo <a href="https://airflow-helm.github.io/charts" rel="nofollow noreferrer">https://airflow-helm.github.io/charts</a> and airflow-stable/airflow with version 8.1.3. So I have Airflow v2.0.1 installed. I have it setup using external postgres database and using the kubernetes executor.</p>
<p>What I have noticed is when airflow related pods are done they go into a &quot;NotReady&quot; status. This happens with the update-db pod at startup and also pods launched by the kubernetes executioner. When I go into airflow and look at the task some are successful and some can be failure, but either way the related pods are in &quot;NotReady&quot; status. In the values file I set the below thinking it would delete the pods when they are done. I've gone through the logs and made sure one of the dags ran as intended and was success in the related task was success and of course the related pod when it was done went into &quot;NotReady&quot; status.</p>
<p>The values below are located in Values.airflow.config.</p>
<p>AIRFLOW__KUBERNETES__DELETE_WORKER_PODS: &quot;true&quot;
AIRFLOW__KUBERNETES__DELETE_WORKER_PODS_ON_FAILURE: &quot;true&quot;</p>
<p>So I'm not really sure what I'm missing and if anyone has seen this behavior? It's also really strange that the upgrade-db pod is doing this too.</p>
<p><a href="https://i.stack.imgur.com/4oTQ7.png" rel="nofollow noreferrer">Screenshot of kubectl get pods for the namespace airflow is deployed in with the &quot;NotReady&quot; pods</a></p>

Kyle N
<p>Figured it out. The K8 namespace had auto injection of linkerd sidecar container for each pod. Would have to just use celery executioner or setup some sort of k8 job to cleanup completed pods and jobs that don’t get cleaned up due to the linkerd container running forever in those pods.</p>
