EricGao888 commented on PR #15302: URL: https://github.com/apache/dolphinscheduler/pull/15302#issuecomment-1857402947
> > I have several questions: > > > > 1. Can you list some specific use cases? > > 2. Do the current job types not meet the requirements? > > 3. If it's to support multiple pods, why use the deployment type instead of the statefulset type? Are either of these types suitable for running scheduled tasks? > > 4. Why is there a need to support services? > > 5. If it's for flexibility, would it be sufficient to directly provide a template for custom job types? > > > > Discussing : > > > > 1. Is Kubernetes more suitable as a runtime? For example, DataX, Spark, Flink, etc. provide Kubernetes as a runtime. The default is local mode. > > Let’s discuss POD first. Currently, there is no support for env, tolerations, etc. If I need to add tolerations parameters, I need to add some code to splice the job and modify the k8sParameter. I think it is not friendly to people who need to use k8s in depth. The second point is that I want it to support some CI functions. For example, I need to initialize namespace, configMap, etc. for each tenant, so that when each tenant is initialized, the same process definition is called and the variables are raised and run. Suitable for assignment. So I was thinking why not be more open? Furthermore, during privatized deployment, the deployment process is directly dragged out in low-code form on ds, eliminating some scripts and making the deployment process more intuitive. As for Delpoyment, I don’t know much about it. I only used it when integrating flink on k8s in DS. Because I saw that Delpoyment can update the content of the pod template, I thought it was very useful, so I poste d it. Flexibility is great, but it may also bring SECURITY VULNERABILITY. That is where we need to trade off. -- 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]
