atombender commented on issue #26485: URL: https://github.com/apache/beam/issues/26485#issuecomment-1987173270
Has there been any work on this? I'm struggling to understand how to make the Beam work through the Flink task manager on Kubernetes. Obviously, with Kubernetes, `DOCKER` is not an option, only `EXTERNAL`. With Python, it looks like you run `apache/beam_python_sdk --worker_pool` as a sidecar inside the Flink task manager pod. But the Beam boot command in `apache/beam_go_sdk` doesn't have this flag. It's also unclear what you're supposed to pass as arguments (like `--id`) to this command. There are zero examples on doing this with Go. Even after several years of apparent Beam + Go support, nobody seems to have posted any code examples, and there's just a tiny handful of StackOverflow posts that don't have any solutions. > it looks like the go SDK has not provided worker pool in SDK harness container yet unlike python and java SDKs. It this a prerequisite, then? Are the plans to work on it? -- 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]
