- Installation command line options
- Chart configuration examples
- Global Settings
- Chart Settings
gitlab-exporter sub-chart provides Prometheus metrics for GitLab
application-specific data. It talks to PostgreSQL directly to perform
queries to retrieve data for CI builds, pull mirrors, etc. In addition,
it uses the Sidekiq API, which talks to Redis to gather different
metrics around the state of the Sidekiq queues (e.g. number of jobs).
This chart depends on Redis and PostgreSQL services, either as part of the complete GitLab chart or provided as external services reachable from the Kubernetes cluster on which this chart is deployed.
The table below contains all the possible chart configurations that can be supplied
helm install command using the
|Supplemental Pod labels. Will not be used for selectors.|
|GitLab Exporter enabled flag|
|List of extra containers to include|
|List of extra init containers to include|
|List of extra volumes mountes to do|
|List of extra volumes to create|
|List of extra environment variables to expose|
|GitLab image pull policy|
|Secrets for the image repository|
|GitLab Exporter image repository|
|initContainer image tag|
|Toggle Prometheus metrics exporter|
|Listen port for the Prometheus metrics exporter|
|GitLab Exporter minimum cpu|
|GitLab Exporter minimum memory|
|Supplemental service labels|
|GitLab Exporter exposed port|
|GitLab Exporter internal port|
|GitLab Exporter service name|
|GitLab Exporter service type|
|Group ID under which the pod should be started|
|User ID under which the pod should be started|
|Toleration labels for pod assignment|
|Set PostgreSQL server port. Takes precedence over |
extraEnv allows you to expose additional environment variables in all containers in the pods.
Below is an example use of
extraEnv: SOME_KEY: some_value SOME_OTHER_KEY: some_other_value
When the container is started, you can confirm that the enviornment variables are exposed:
env | grep SOME SOME_KEY=some_value SOME_OTHER_KEY=some_other_value
pullSecrets allows you to authenticate to a private registry to pull images for a pod.
Additional details about private registries and their authentication methods can be found in the Kubernetes documentation.
Below is an example use of
image: repository: my.image.repository pullPolicy: Always pullSecrets: - name: my-secret-name - name: my-secondary-secret-name
annotations allows you to add annotations to the GitLab Exporter pods. For example:
annotations: kubernetes.io/example-annotation: annotation-value
We share some common global settings among our charts. See the Globals Documentation for common configuration options, such as GitLab and Registry hostnames.
The following values are used to configure the GitLab Exporter pod.
By default, the pod exposes a metrics endpoint at
metrics are enabled, annotations are added to each pod allowing a
Prometheus server to discover and scrape the exposed metrics.