V: Victor Monteiro

D: Daniel Imberman

G: Grant Nicholas

- Using custom resources for airflow deployments + openshift integration
-storage options
- Splitting the k8s operator and k8s executor code
- Building k8s only operators?
- placing operator inside of a "k8s folder"?
- customizable task-level configurations

• Airflow + kubernetes operators
  • Create a Pod Operator
  • Possibly create a Job Operator
  • Creating an example custom resource for the airflow community: V
• Airflow + kubernetes executor
  • Executor storage + DAG transportation: D + G
    • perhaps we should use a "git server" that can take in revision
  • Task level configuration: G
  • Using kubernetes secrets + keychain: D + kubernetes team
  • We need to throttle the speed in which the executor can launch pods: G + D
    • We can create a pending queue that the watcher can remove from when it receives a running event
    •