Airflow Kubernetes Executor pods go into "NotReady" state instead of being deleted

Question

Installed airflow in kubernetes using the repo https://airflow-helm.github.io/charts 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.

What I have noticed is when airflow related pods are done they go into a "NotReady" 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 "NotReady" 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 "NotReady" status.

The values below are located in Values.airflow.config.

AIRFLOW__KUBERNETES__DELETE_WORKER_PODS: "true" AIRFLOW__KUBERNETES__DELETE_WORKER_PODS_ON_FAILURE: "true"

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.

Screenshot of kubectl get pods for the namespace airflow is deployed in with the "NotReady" pods