Hi, I have been experimenting with flink-kubernetes-operator today and it's very cool. However, the Flink application will be stuck in scheduled state if I increase the CPU to anything above 1 for JobManager and TaskManager. It works fine if I keep the CPU to 1.
I am testing the Flink deployment with Minikube running with 4 CPUs and 8GB RAM. Unfortunately, I am not sure what to look out for to figure out why it's stuck. Appreciate it if someone could help point me in the right direction. Thanks!
