Hi Morgan,
There is a placeholder in the values.yaml: [image: image.png] This should create an entry on the operator container: [image: image.png] Can you share the output of this command pls? k get deploy flink-kubernetes-operator -o yaml Thanks, Matyas On Thu, Jun 23, 2022 at 12:12 PM Geldenhuys, Morgan Karl < morgan.geldenh...@tu-berlin.de> wrote: > Greetings all, > > > I am trying to deploy Flink jobs using the Flink Kubernetes Operator and I > would like to have Prometheus scrape metrics from the various pods. > > > The jobs are created successfully, however, the metrics don't appear to be > available. > > > The following steps were followed based on the documentation: > https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-release-1.0/docs/operations/metrics-logging/#how-to-enable-prometheus-example > > > > - The Prometheus stack is deployed successfully > - The Pod Monitor is enabled successfully > - The Flink Kubernetes operator is successfully created with following > configuration is appended to the values.yaml > > > metrics: > port: 9999 > > defaultConfiguration: > create: true > append: true > flink-conf.yaml: |+ > kubernetes.operator.metrics.reporter.prom.class: > org.apache.flink.metrics.prometheus.PrometheusReporter > kubernetes.operator.metrics.reporter.prom.port: 9999 > > > > - The job is deployed with the following added to > the flinkConfiguration > > > "metrics.reporter.prom.class": > "org.apache.flink.metrics.prometheus.PrometheusReporter", > "metrics.reporter.prom.port": "9999" > > > Now on investigation, it does not appear that the metrics port 9999 is > opened on the containers. The documentation is not very clear where to put > the port config, but i assumed this what they meant as above. Is this > correct? Is there another way of opening ports if this is not functioning > as intended? > > > Thanks in advance! > > > Regards, > > M. > > > >
