cswangzheng opened a new issue, #3479: URL: https://github.com/apache/incubator-seatunnel/issues/3479
### Search before asking - [X] I had searched in the [feature](https://github.com/apache/incubator-seatunnel/issues?q=is%3Aissue+label%3A%22Feature%22) and found no similar feature requirement. ### Description We have already use k8s for flink and spark. For flink we use application mod. For spark, we use cluster mode, which means the job manager deployment is created by flink client, and driver pod created by spark client. For example, we can use this command to start a seatunnel flink cluster: `./bin/flink run-application \ --target kubernetes-application \ -Dkubernetes.cluster-id=seatunnel-cluster \ -Dkubernetes.container.image=seatunnel-image-name \ local:///opt/flink/seatunnel.jar` The first thing is in the document part, told user we can support this kind of deployment. The second thing, usually we build a unique image for flink or spark without config file in it, so use config as a file in pod is not a choose, if the content of config file can be passed by param should be better. So we want to add new param like config-content, which is base64 encode value of the content of config file. Any thoughts for this? ### Usage Scenario Enhance seatunnel to support more kind of deployment mode. ### Related issues _No response_ ### Are you willing to submit a PR? - [X] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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]
