-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Add deferrable mode to Kubernetes and GKE operators #28230
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
Conversation
3a6d75b to
95d0758
Compare
95d0758 to
8b8c48b
Compare
7790412 to
f290082
Compare
ca232d5 to
2843e15
Compare
docs/apache-airflow-providers-google/operators/cloud/kubernetes_engine.rst
Outdated
Show resolved
Hide resolved
kaxil
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you can separate this into 2 PRs - one for async mode for KPO and the other for async mode for GKE, that will help in reviewing
|
As we are adding new feature to existing operator instead of creating new operator for deferrable mode, we decided to also use KubernetesPodOperator as a base class for the GKEStartPodOperator to instantiate needed behavior. So splitting this to 2 separate PRs will be not an option here as we will also need to wait until KubernetesPodOperator will be merged to main and only then add new PR for the GKEStartPodOperator. |
da7f5d5 to
b90f308
Compare
As I had mentioned in #28230 (comment) , if the PR is big, it will take time to review and makes our life as reviewers hard. So please expect it will take some time to review the PR fully |
cdb53a7 to
a34fcf2
Compare
…remove method for writing permanent config file
Add logging on all stages of pod run, also description for parameters and unit tests
27d4fa1 to
fb6f2c5
Compare
|
@kaxil @MrGeorgeOwl @lwyszomi |
|
@MrGeorgeOwl can you rebase and fix conflicts? |
|
@eladkal |
Thanks. i thought by split some parts were extracted then we have some parts left here as a followup. Thanks for the clarification |
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.