Commit 46529246 authored by Marcia Ramos's avatar Marcia Ramos

Merge branch '44853-add-rbac-flag-for-runner-chart-to-docs' into 'master'

Add RBAC flag for Runner chart to docs

Closes #44853

See merge request gitlab-org/gitlab-ce!18113
parents 08083f43 437bb48d
...@@ -72,6 +72,18 @@ concurrent: 10 ...@@ -72,6 +72,18 @@ concurrent: 10
## ##
checkInterval: 30 checkInterval: 30
## For RBAC support:
rbac:
create: false
## Run the gitlab-bastion container with the ability to deploy/manage containers of jobs
## cluster-wide or only within namespace
clusterWideAccess: false
## Use the following Kubernetes Service Account name if RBAC is disabled in this Helm chart (see rbac.create)
##
# serviceAccountName: default
## Configuration for the Pods that that the runner launches for each new job ## Configuration for the Pods that that the runner launches for each new job
## ##
runners: runners:
...@@ -116,6 +128,12 @@ runners: ...@@ -116,6 +128,12 @@ runners:
``` ```
### Enabling RBAC support
If your cluster has RBAC enabled, you can choose to either have the chart create its own sevice account or provide one.
To have the chart create the service account for you, set `rbac.create` to true.
### Controlling maximum Runner concurrency ### Controlling maximum Runner concurrency
A single GitLab Runner deployed on Kubernetes is able to execute multiple jobs in parallel by automatically starting additional Runner pods. The [`concurrent` setting](https://docs.gitlab.com/runner/configuration/advanced-configuration.html#the-global-section) controls the maximum number of pods allowed at a single time, and defaults to `10`. A single GitLab Runner deployed on Kubernetes is able to execute multiple jobs in parallel by automatically starting additional Runner pods. The [`concurrent` setting](https://docs.gitlab.com/runner/configuration/advanced-configuration.html#the-global-section) controls the maximum number of pods allowed at a single time, and defaults to `10`.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment