Configure Airflow KubernetesExecutor with pod templates and per-task pod overrides for resource isolation

Steps

1. Set executor = KubernetesExecutor in airflow.cfg and provide a pod_template_file pointing to a base Kubernetes Pod manifest YAML
2. Define default resource requests/limits in the base pod template; Kubernetes will apply these to every task pod
3. Override resources for specific tasks using the executor_config parameter on the operator: executor_config={'KubernetesExecutor': {'request_memory': '2Gi', 'limit_cpu': '1'}}
4. Mount secrets and ConfigMaps in the pod template or per-task executor_config to supply environment variables and credentials without baking them into images
5. Configure pod_template_file namespace, service account, and image pull policy; ensure the Airflow worker service account has the RBAC permissions to create and delete pods
6. Use Airflow's built-in pod log streaming to retrieve task logs from ephemeral Kubernetes pods before they are deleted