For application mode FlinkDeployments (maybe even session mode) in Kubernetes from the Flink Kubernetes Operator what is the absolute minimum amount of CPU and RAM that is required to run the JobManager and TaskManager processes?
Some of the example deployment yaml examples have CPU set at 1 full vCPU and memory at 2GB (2048 MB). If you factor in JobManager HA, and 1 or more TaskManagers (not sure what is the bounding limit for these processes), you can be at 3 vCPU and 6 GB memory used just by the “Flink Infrastructure” not counting the Job pods. Has anyone seen a need to have more resources dedicated to these processes for some reason? Has anyone run it leaner than this (like with 0.5 vCPU and less than 1GB memory) in production? Comparing this to Google Cloud Platform and the Dataflow Runner, AFAIK the only resources utilized (that customers pay for) are the Job instances. Lee Parayno Sent from my iPhone
