Hello,
Thanks for the response, I will take a look at it.
But if we aren't able to use the flink operator due to technical
constraints is it possible to deploy the JM as deployment without any
consequences that I am not aware of?
Sincerely,
Le sam. 3 sept. 2022 à 23:27, Gyula Fóra a écrit :
>
Hey All,
We recently updated to Flink 1.15.1. We deploy stream cluster in Application
mode in Native K8S.(Deployed on Amazon EKS). The cluster is configured with
Kubernetes HA Service, Minimum 3 replicas of Job manager and pod-template which
is configured with topologySpreadConstraints to enab
Hi, Biao!
Thanks for the fast response! Setting that in the podTemplate opens the
metrics port in the pods, but unfortunately not on the rest service. Not
sure if that is standard procedure, but my Prometheus setup scraps the
metrics port on services but not pods. On my previous non-operator
stand
Hi Javier,
You can use podTemplate to expose the port in the flink containers.
Here is a snippet:
spec:
flinkVersion: v1_15
flinkConfiguration:
state.savepoints.dir: file:///flink-data/flink-savepoints
state.checkpoints.dir: file:///flink-data/flink-checkpoints
metrics.reporter.pro