jscheffl opened a new pull request, #60612: URL: https://github.com/apache/airflow/pull/60612
@vikramkoka asked me to support K8s provider as close to Helm chart as I was reviewing a couple of PRs anyway. Try to join in there... with a bit of reduced capacity as already some other obligations. But willing to help working off backlog. To compensate removing myself from some integration tests, I assume there are sufficient active contributors. Note to @dstandish I saw a redundant definition for K8s provider with your name but file is parsed top-down, last match wins. So the entry in line 13 was not effective. If you still want to be in, add yourself to line 89 please! FYI @jedcunningham ##### Was generative AI tooling used to co-author this PR? - [ ] Noooooo (please specify the tool below) --- * Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)** for more information. Note: commit author/co-author name and email in commits become permanently public when merged. * For fundamental code changes, an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals)) is needed. * When adding dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). * For significant user-facing changes create newsfragment: `{pr_number}.significant.rst` or `{issue_number}.significant.rst`, in [airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
