[Task]: Reconsider the need to stage Beam SDK to GCS after removing runner v1 support.

[tvalentyn]

What needs to happen?

SDK now uses Beam-provided containers as execution environment on Dataflow. It may no longer be necessary to stage the SDK to staging location, or at minimum, it should not be a requirement on runner v2 pipelines.

Issue Priority

Priority: 3 (nice-to-have improvement)

Issue Components

• Component: Python SDK
• Component: Java SDK
• Component: Go SDK
• Component: Typescript SDK
• Component: IO connector
• Component: Beam examples
• Component: Beam playground
• Component: Beam katas
• Component: Website
• Component: Spark Runner
• Component: Flink Runner
• Component: Samza Runner
• Component: Twister2 Runner
• Component: Hazelcast Jet Runner
• Component: Google Cloud Dataflow Runner

[tvalentyn]

we could actually remove staging for runner v2 now that we are using external contianers, instead of waiting for 2.50.0

[lostluck]

2.50 release manager here.
This issue is currently tagged for the 2.50.0 release, which cuts in a week on August 9th.

Please complete work and get it into the main branch in that time, or move this issue to the 2.51 Milestone: https://github.com/apache/beam/milestone/15

[AnandInguva]

2.50 release manager here. This issue is currently tagged for the 2.50.0 release, which cuts in a week on August 9th.

Please complete work and get it into the main branch in that time, or move this issue to the 2.51 Milestone: https://github.com/apache/beam/milestone/15

It is almost done. I will update the issue before August 9th.