a question about KubernetesConfigOptions

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

a question about KubernetesConfigOptions

Debasish Ghosh
Hello -


I see that there is no support for options like Volumes and VolumeMounts. Also I see entries for JOB_MANANGER_CPU and TASK_MANAGER_CPU but not for JOB_MANAGER_MEMORY and TASK_MANAGER_MEMORY. How do we accommodate these if we want to pass them as well ? I see that the class is annotated with @PublicEvolving - just wanted to clarify if these are planned to be added in future.

regards.
Reply | Threaded
Open this post in threaded view
|

Re: a question about KubernetesConfigOptions

Yang Wang
Hi Debasish Ghosh,

Thanks for the attention on native K8s integration of Flink.

1. For volumes and volumes mount, it is not supported now. And we are trying to get it done via pod template. Refer here[1] for more information.

2. Currently, on different deployments, Flink has different cpu config options. But for the memory, all the deployments share the same config options. You could find more information here[2]. 
* yarn.appmaster.vcores
* yarn.containers.vcores
* kubernetes.jobmanager.cpu
* kubernetes.taskmanager.cpu

3. You are right. This class is PublicEvolving and we may introduce more config options in the future(e.g. pod template related).



Debasish Ghosh <[hidden email]> 于2020年12月21日周一 下午3:21写道:
Hello -


I see that there is no support for options like Volumes and VolumeMounts. Also I see entries for JOB_MANANGER_CPU and TASK_MANAGER_CPU but not for JOB_MANAGER_MEMORY and TASK_MANAGER_MEMORY. How do we accommodate these if we want to pass them as well ? I see that the class is annotated with @PublicEvolving - just wanted to clarify if these are planned to be added in future.

regards.