Thanks everyone for the responses. I have checked and noticed that the pod fails to start due to insufficient resources with kubectl describe pods. It is able to run only if I set jobManager to 1 CPU and taskManager to 1.5 CPU at maximum.
But it's good to know that it wasn't due to an incorrect configuration in the deployment. Thanks! On Sat, Mar 26, 2022 at 12:49 PM Yang Wang <danrtsey...@gmail.com> wrote: > Could you please share the result of "kubectl describe pods" when getting > stuck? It will be very useful to help to figure out the root cause. > > I guess it might be related to insufficient resources for minikube. > > > Best, > Yang > > Őrhidi Mátyás <matyas.orh...@gmail.com> 于2022年3月26日周六 03:12写道： > >> It's worth checking the deployment->replica set->pod chain for error >> message. >> >> On Fri, Mar 25, 2022, 19:49 Makas Tzavellas <makas.tzavel...@gmail.com> >> wrote: >> >>> 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! >>> >>
