📖 Assist customers in migrating non-networked airflow jobs in APC

[jhpyke]

User Story

As a user of Airflow
I want to have my pipeline continue working
So that I can run my non-networked jobs on APC.

Value / Purpose

Following the work done in #4319 , we now need to roll these changes out to our users. To do this, we will need to support them through our support channels (and likely monitor #ask-data-engineering) to ensure that all users are able to migrate successfully. For users, this means

• Re-running their image pipeline (and resolving any issues they cause doing so - this should be their responsibility)
• updating the definition of their DAGs per the user guidance we have published (we WILL help them with this if needed, but should be light touch - referring back to the docs, pointing out divergance)
• Testing said changes in dev so they can be confident they'll work in prod (again, we can assist with interpreting pod logs/API calls, but not any problems with running their actual code)

We are asking users to self-identify that their DAG is exempt via a Google Sheets form. If users don't either act or indicate their exemption, we will need to determine how active we will be in pursuing them.

Useful Contacts

@jhpyke

User Types

All airflow users with no networking requirements

Hypothesis

No response

Proposal

We should have the resource required to assist users as support issues come in. Depending on the scale of any issues encountered, this may or may not end up being a full-time ticket.

Additional Information

No response

Definition of Done

• All users who have not been exempted have made the required changes to run in APC
• All remaining unconverted DAGs are either disabled, or recognised as exempt
• Users with specific networking requirements are still able to run on the current EKS until we have networking ready for them

[jhpyke]

Closing as all remaining users are covered by the work in #4490. Will follow up with equivalent ticket for those customers once work is unblocked.