Lee-W opened a new pull request, #69532:
URL: https://github.com/apache/airflow/pull/69532

   * Add Go + Java + Python lang-SDK coordinator system test on 
KubernetesExecutor
   
   Adds a kind-based system test that runs one Dag (lang_sdk_combined) whose 
tasks span the Python task-runner and the Go/Java coordinators on the 
KubernetesExecutor. The golang/java queues route to their coordinators, each 
carrying a pod_template_file (the worktree-1 feature). Each worker pod's init 
container stages the queue's artifact (Go binary / Java jar) from a 
per-language localstack S3 bucket through the DagBundle interface into a shared 
emptyDir that is the coordinator's executables_root/jars_root. The Go queue 
runs on the prod image (self-contained static binary); the Java queue runs on 
the CI image (bundles the JVM the JavaCoordinator needs).
   
   New k8s-test-only bundles: go-sdk/example/k8s_combined and 
java-sdk/k8s-example. Provisioning is a new breeze command, `breeze k8s 
setup-lang-sdk-test`, which builds the artifacts, deploys localstack, uploads 
artifacts and the Python stub Dag, renders the pod-template image placeholders, 
and installs the Helm release.
   
   * Wire up lang-sdk test with breeze k8s command
   
   * Keep the dags-folder bundle when provisioning the lang-SDK k8s test
   
   The lang-SDK Helm values set config.dag_processor.dag_bundle_config_list to 
only the localstack S3 bundle, which replaced the default dags-folder bundle. 
The standard KubernetesExecutor example-Dag tests share the same test run, so 
dropping dags-folder marked their Dags stale and their dagRun triggers returned
   404. Configure the bundles additively via dagProcessor.dagBundleConfigList 
(the chart-recommended input) so both the example Dags and the lang-SDK stub 
Dag are served.
   
   * Move lang-SDK k8s example sources out of go-sdk/java-sdk into 
kubernetes-tests
   
   The Go and Java coordinator example sources for the KubernetesExecutor 
lang-SDK system test lived under go-sdk/example/k8s_combined and 
java-sdk/k8s-example, cluttering the SDK source trees. Move them next to the 
rest of the test assets under kubernetes-tests/lang_sdk/ (go_example, 
java_example).
   
   go_example becomes its own Go module resolving the in-repo go-sdk via a 
replace directive (it no longer sits inside the go-sdk module); java_example 
stays a standalone Gradle build that resolves the SDK from mavenLocal, now 
built with java-sdk's gradle wrapper pointed at the moved project. The breeze 
provisioning command, README, and stub-Dag docs are updated to the new paths. # 
Conflicts:
   #    dev/breeze/doc/images/output_setup_check-all-params-in-groups.txt #     
dev/breeze/doc/images/output_setup_regenerate-command-images.txt
   
    <!-- SPDX-License-Identifier: Apache-2.0
         https://www.apache.org/licenses/LICENSE-2.0 -->
   
   <!--
   Thank you for contributing!
   
   Please provide above a brief description of the changes made in this pull 
request.
   Write a good git commit message following this guide: 
http://chris.beams.io/posts/git-commit/
   
   Please make sure that your code changes are covered with tests.
   And in case of new features or big changes remember to adjust the 
documentation.
   
   For user-facing UI changes, please attach before/after screenshots (or a 
short
   screen recording) so reviewers can assess the visual impact.
   
   Feel free to ping (in general) for the review if you do not see reaction for 
a few days
   (72 Hours is the minimum reaction time you can expect from volunteers) - we 
sometimes miss notifications.
   
   In case of an existing issue, reference it using one of the following:
   
   * closes: #ISSUE
   * related: #ISSUE
   -->
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   <!--
   If generative AI tooling has been used in the process of authoring this PR, 
please
   change below checkbox to `[X]` followed by the name of the tool, uncomment 
the "Generated-by".
   -->
   
   - [ ] Yes (please specify the tool below)
   
   <!--
   Generated-by: [Tool Name] following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
   -->
   
   ---
   
   * 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`, in 
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
 You can add this file in a follow-up commit after the PR is created so you 
know the PR number.
   


-- 
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]

Reply via email to