Hi Community, I recently ran into an issue I am trying to find solutions to it but I haven’t so far found anything helpful. I am running a flinkkubernetes operator and whenever I create a FlinkDeployment in a Istio-managed namespace (istio injection enabled), the jobManager pod won’t start. Is there a way to add annotations in the FlinkDeployment CR to disable this behavior? Greatly appreciate your assistance.

Yes. In your flink deployment ls spec.podTemplate.metadata.annotations You can refer https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-main/docs/custom-resource/pod-template/#pod-template

Hi @Bhupendra Yadav thank you for your swift response. Does it change anything if I place the podTemplate at spec.podTemplate instead of spec.jobmanager.podTemplate? All I want is for the jobManager pod that’s eventually created by the deployment to not automatically inject itio-proxy sidecar.

If you just want to use for job manager, then yes you can add in job manager.podTemplate. Ps: spec.podtemplate is common for both jm and tm

In both cases it returned an error as shown below

Check the flink k8s operator logs for more info. I have used the pod template myself and it works as expected.

I have managed to figure out the problem and fixed it. Finally I can create the jm pod without istio injection