Rely on SkeinOperator krb5 setup

We shouldn't have to wire through the krb5 variables manually—and in fact it breaks production because the DAG parse KRB5CCNAME is different than the correct path in the executor.

This has been tested in the Airflow devenv—but it targets code paths which are now known to diverge in production! Wish us luck...

Bug: T418442

Edited by Awight

Merge request reports

Loading