Flink Job is not started automatically on deployment of Flink job cluster about flinkk8soperator

[anandswaminathan]

@anekdoti Might be related to this - #130

Can you paste the output of the pods ? kubectl get pods -n flink-operator
Also wondering why you output does not have status field - https://github.com/lyft/flinkk8soperator/blob/master/deploy/crd.yaml#L382

Wondering issue with Subresources

[anekdoti]

Hello @anandswaminathan

thanks for your attention. Here is the output of kubectl get pods -n flink-operator:

NAME                                                      READY   STATUS    RESTARTS   AGE
flinkoperator-cd9f5ccdb-pd95v                             1/1     Running   0          45h
wordcount-operator-example-f366d27c-jm-bc9545777-6r6hz    1/1     Running   0          16h
wordcount-operator-example-f366d27c-tm-7b99f654bb-s9w29   1/1     Running   0          16h
wordcount-operator-example-f366d27c-tm-7b99f654bb-tddbx   1/1     Running   0          16h

[anekdoti]

Concerning the relation to #130: I also initially had problems with the taskmanagers starting because the taskmanager.network.memory.min was set larger than the JVM heap size. I worked around this by increasing the resource requests for job- and taskmanager to 1000Mi from 200Mi. Maybe I should have mentioned this before.

[anandswaminathan]

@anekdoti We have found the root cause of the issue. You are running the older version of the operator. We are updating the docs. Sorry for the trouble.

[anandswaminathan]

@anekdoti
The quickstart docs have been fixed: https://github.com/lyft/flinkk8soperator/blob/master/docs/quick-start-guide.md

Please start from scratch by deleting the existing resources. We do not want different version again causing issues.

[anekdoti]

@anandswaminathan
It works perfectly now! Thank you very much!

[anandswaminathan]

@anekdoti Great. Closing this.