Skip to content

Fix a problem with wrong prmetheus target because of missing port in POD

dinorastoder requested to merge dinorastoder/gitlab-runner:prometheus-metrics-port into master

Trying to solve problem in #26 (closed) where metrics can not be scraped by Prometheus. Issue is because Promehteus require that scraping ports are defined in Pod/Container specification.

From https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.10/

List of ports to expose from the container. Exposing a port here gives the system additional information about the network connections a container uses, but is primarily informational. Not specifying a port here DOES NOT prevent that port from being exposed. Any port which is listening on the default "0.0.0.0" address inside a container will be accessible from the network. Cannot be updated.

Merge request reports