Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

⛰ Move Airflow Compute to APC cluster #4549

Open
4 tasks
jhpyke opened this issue Jun 17, 2024 · 0 comments
Open
4 tasks

⛰ Move Airflow Compute to APC cluster #4549

jhpyke opened this issue Jun 17, 2024 · 0 comments
Labels

Comments

@jhpyke
Copy link
Contributor

jhpyke commented Jun 17, 2024

Brief summary of what this Epic is

This Epic captures the work required to move Airflow jobs from the existing Airflow Cluster(s) to APC. This work was triggered by the failure of Kube2IAM, but represents a long term plan to improve the stability of the cluster

List of issues in this epic

Other information

Overall plan is:

  • Create a new release of mojap-airflow-tools to be available within dev. This will have conditional logic that triggers the new cluster/IRSA on our basic pods ONLY.
  • Release it, and update requirements file for airflow-dev to reflect the new release. This should take effect within 20 mins - if not check scheduler logs (requirements-ip-install-<date/time>.log)
  • Run a test pod using the BasicPodOperator to ensure it can accept the new service-account info correctly.
  • Assuming testing is smooth, release comms to users on how to update their images to be accessible from new cluster (new image release pipeline already made by @jacobwoffenden)
  • Work with users with specific networking requirements to ensure these are met by new cluster
  • Transition new user workloads to APC.
@jhpyke jhpyke added the epic label Jun 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: ⛰ Epic
Development

No branches or pull requests

1 participant