Small clarification, KPO doesn't currently take into account the default namespace specified in kube settings. AFAIK it considers the following:
- in_cluster - cluster_context - config_file - enable_tcp_keepalive - verify_ssl And so my proposal would be that, after a deprecation period, we only derive these settings from the hook + KPO params. During deprecation period, we would emit a warning when the effective setting (i.e. the setting derived after applying all config sources in order of precedence) would be different after core airflow K8s config is excluded from KPO config.
