Concurrency setting being ignored and not following defaults

Description

I have set spec.concurrent: 40 in the Runner custom resource definition. However, the generated config.toml still shows:

concurrent = 1

We are using a custom config.toml via a ConfigMap (required for Fleeting runners and additional configuration).

I attempted to set:

concurrent = 40

above the [[runners]] section, but the operator still overrides this value with 1.

Startup of the pod shows:

concurrent = 40
check_interval = 30
log_level = "info"
listen_address = "[::]:9252"
'/scripts/config.toml' -> '/root/.gitlab-runner/config.toml'
Registration attempt 1 of 30
Runtime platform                                    arch=amd64 os=linux pid=10 revision=9ba718cd version=18.3.0
Running in system-mode.                            
                                                   
Merging configuration from template file "/custom/template.toml" 
Created missing unique system ID                    system_id=r_xxxxxxxxxx
Verifying runner... is valid                        correlation_id=xxxxxxxxxxxxxxxx runner=xxxxxxxx
WARNING: The specified runner request concurrency (10) is larger than the current global concurrent limit (1). The global concurrent limit will not be increased and takes precedence. 
Runner registered successfully. Feel free to start it, but if it's running already the config should be automatically reloaded!
 
Configuration (with the authentication token) was saved in "/etc/gitlab-runner/config.toml" 
Runtime platform                                    arch=amd64 os=linux pid=1 revision=9ba718cd version=18.3.0
Starting multi-runner from /etc/gitlab-runner/config.toml...  builds=0 max_builds=0
Running in system-mode.   

Runner Definition

apiVersion: apps.gitlab.com/v1beta2
kind: Runner
metadata:
  name: europe-west4
  namespace: gitlab-runner-operator
spec:
  gitlabUrl: https://gitlab.com
  token: gitlab-runner-secret
  config: gitlab-runner-config-europe-west4
  env: gitlab-runner-env
  concurrent: 40
  interval: 3

Environment

• GitLab Runner Operator version: v1.39.0
• Kubernetes cluster in use

Observed Behavior

• spec.concurrent is ignored.
• concurrent value in config.toml remains 1 despite custom ConfigMap modifications.

Expected Behavior

• config.toml should reflect spec.concurrent: 40.
• Custom concurrent values in a ConfigMap should not be overridden by the operator.

Possibly Related Issue

Reference: GitLab Runner Operator Issue #11