Currently KPO uses "core" kubernetes utils for client generation.
*(I'm working on migrating it to use the hook. The effort was waiting on a few other changes and i'm picking it back up now.)* In addition to using the core *utils*, it also uses the "core" airflow kubernetes *settings* from airflow.cfg. E.g. default namespace, "in cluster" etc. My thinking is, we should deprecate consideration of "core" k8s settings in KPO and only allow (after a major release of the provider) configuration using the hook. This way, your KPO tasks are configured by KPO params and the connection (if provided) and that's it. But because this could be somewhat disruptive, want to see what people think. Does anyone feel very strongly that we should indefinitely let KPO continue to consider the core k8s settings, and just merge them in with conn settings if provided?
