Skip to content

config.toml get default parameters in Openshift cluster.

Hello,

I have a newly deployed OpenShift cluster version 4.12.22 on which I have deployed only MinIO for S3 cache and Gitlab Runner Operator. I have created a configMap with the config.toml I need to use, but for whatever reason some options from the config.toml are getting the default parameters when the merge between file is done.

This is the configMap I use:

apiVersion: v1
data:
  config.toml: |
    [session_server]
      session_timeout = 1800
    
    [[runners]]
      output_limit = 51200
      request_concurrency = 1
      url = "https://example.com"
      token = "bZzWFCdSGuzydDRSxxXy"
      executor = "kubernetes"
      [runners.cache]
        Type = "s3"
        Shared = true
        [runners.cache.s3]
          ServerAddress = "minio.minio-tenant.svc.cluster.local:80"
          AccessKey = "MU0zZbtD2nnsCmDs"
          SecretKey = "sLAfRINB4IfIfapW2vJEM5ikhqYE33CV"
          BucketName = "gitlab-runner"
          Insecure = true
      [runners.kubernetes]
        namespace = "gitlab-runner"
        namespace_overwrite_allowed = ""
        privileged = true
        memory_limit = "24Gi"
        memory_request = "18Gi"
        ephemeral_storage_request = "10Gi"
        pull_policy = ["always"]
        poll_timeout = 3600
kind: ConfigMap
metadata:
  name: gitlab-runner-config-toml
  namespace: gitlab-runner

The following options gets the defaults parameters: poll_timeout, output_limit, request_concurrency.

Can someone give me a hint? Why I get this behavior, what I'm doing wrong?

Edited by Muad`Dib