Skip to content

Bump gitlab-exporter to 10.3.0

Matthias Käppler requested to merge mk-gitlab-exporter-10.3 into master

What does this MR do?

This updates the gitlab-exporter service to the latest version 10.3.0, which in return updates Puma to the latest available version 5.3.2.

Related issues

General maintenance.

Test plan

Step 1: Check out the branch locally

Step 2: Patch configmap to use Puma as the Rack server

diff --git a/charts/gitlab/charts/gitlab-exporter/templates/configmap.yaml b/charts/gitlab/charts/gitlab-exporter/templates/configmap.yaml
index 9680b15e1..c6aac08ce 100644
--- a/charts/gitlab/charts/gitlab-exporter/templates/configmap.yaml
+++ b/charts/gitlab/charts/gitlab-exporter/templates/configmap.yaml
@@ -10,7 +10,7 @@ metadata:
 data:
   gitlab-exporter.yml.erb: |
     server:
-      name: webrick
+      name: puma
       listen_address: 0.0.0.0
       listen_port: {{ .Values.service.internalPort }}

Step 3: Apply changes

$ helm upgrade gitlab . \
  --set global.hosts.domain=192.168.18.5.nip.io \
  -f examples/kind/values-base.yaml \
  -f examples/kind/values-ssl.yaml \
--set gitlab.gitlab-exporter.enabled=true --set gitlab.gitlab-exporter.image.tag=mk-gitlab-exporter-10-3

Step 4: Verify Puma start up in gitlab-exporter container

by pulling container logs or k9s:

Screenshot_from_2021-06-01_14-12-48

Verify that Puma version is 5.3.2

Checklist

See Definition of done.

For anything in this list which will not be completed, please provide a reason in the MR discussion.

Required

  • Merge Request Title and Description are up to date, accurate, and descriptive
  • MR targeting the appropriate branch
  • MR has a green pipeline on GitLab.com (requires gitlab-org/build/CNG!682 (merged))

Expected (please provide an explanation if not completing)

Edited by Mitchell Nielsen

Merge request reports