- #HOW TO INSTALL GITLAB RUNNER ON KUBERNETES HOW TO#
- #HOW TO INSTALL GITLAB RUNNER ON KUBERNETES UPDATE#
- #HOW TO INSTALL GITLAB RUNNER ON KUBERNETES REGISTRATION#
#HOW TO INSTALL GITLAB RUNNER ON KUBERNETES HOW TO#
See Running Privileged Containers for the Runners for how to enable it,Īnd the GitLab CI Runner documentation on running dind. # Configure the maximum number of concurrent jobs # ref: # concurrent : 10 Running Docker-in-Docker containers with GitLab Runners
![how to install gitlab runner on kubernetes how to install gitlab runner on kubernetes](https://i.stack.imgur.com/ralQg.png)
The concurrent setting controls the maximum number of pods allowed at a single time, and defaults to 10. Please read the docs before turning this on: # ref: # privileged : false # Namespace to run Kubernetes jobs in (defaults to 'default') # namespace: # Build Container specific configuration # builds : # cpuLimit: 200m # memoryLimit: 256Mi cpuRequests : 100m memoryRequests : 128Mi # Service Container specific configuration # services : # cpuLimit: 200m # memoryLimit: 256Mi cpuRequests : 100m memoryRequests : 128Mi # Helper Container specific configuration # helpers : # cpuLimit: 200m # memoryLimit: 256Mi cpuRequests : 100m memoryRequests : 128Mi Controlling maximum Runner concurrencyĪ single GitLab Runner deployed on Kubernetes is able to execute multiple jobs in parallel by automatically starting additional Runner pods. # ref: # runnerRegistrationToken : " " # Set the certsSecretName in order to pass custom certficates for GitLab Runner to use # Provide resource name for a Kubernetes Secret Object in the same namespace, # this is used to populate the /etc/gitlab-runner/certs directory # ref: #certsSecretName: # Configure the maximum number of concurrent jobs # ref: # concurrent : 10 # Defines in seconds how often to check GitLab for a new builds # ref: # checkInterval : 30 # Configuration for the Pods that that the runner launches for each new job # runners : # Default container image to use for builds when none is specified # image : ubuntu:16.04 # Run all containers with the privileged flag enabled # This will allow the docker:dind image to run if you need to run Docker # commands. This must # be retreived from your GitLab Instance.
#HOW TO INSTALL GITLAB RUNNER ON KUBERNETES REGISTRATION#
Here is a snippet of the important settings: # The GitLab Server URL (with protocol) that want to register the runner against # ref: # gitlabUrl : # The Registration Token for adding new Runners to the GitLab Server. The rest of the configuration is documented in the values.yaml in the chart repository. Unless you need to specify additional configuration, you are ready to install. See the GitLab Runner Documentation for more information.
![how to install gitlab runner on kubernetes how to install gitlab runner on kubernetes](https://about.gitlab.com/images/ci/gitlab-ci-cd-logo_2x.png)
runnerRegistrationToken - The Registration Token for adding new Runners to the GitLab Server.gitlabUrl - the GitLab Server URL (with protocol) to register the runner against.In order for GitLab Runner to function, your config file must specify the following: The default configuration can always be found in the values.yaml in the chart repository. See Helm docsįor information on how your values file will override the defaults. The Helm client installed locally on your machineĬonfiguring GitLab Runner using the Helm ChartĬreate a values.yaml file for your GitLab Runner configuration.The kubectl CLI installed locally and authenticated for the cluster.Your GitLab Server's API is reachable from the cluster.New pod within the specified namespace to run it.įor more information on available GitLab Helm Charts, please see our overview. For each new job it receives from GitLab CI, it will provision a.
![how to install gitlab runner on kubernetes how to install gitlab runner on kubernetes](https://wwsean08.com/images/2018/06/gitlab-runner.png)
#HOW TO INSTALL GITLAB RUNNER ON KUBERNETES UPDATE#
Now, install Gitlab on Kubernetes using Helm helm repo add gitlab helm repo update helm upgrade -install gitlab gitlab/gitlab -namespace gitlab \ -timeout 600s \ -set = \ -set =true \ -set certmanager.install=false \ -set =false \ -set =lab-tls \ -f value.yamlīy default, gitlab-nginx-ingress-controller service will be deployed as LoadBalancer type.These charts have been tested on Google Kubernetes Engine and Azure Container Service. On my cluster, I also already have my own wildcard certificate, so I going to use this for ingress TLS kubectl create secret tls lab-tls - key privkey.pem - cert fullchain.pem -n gitlab Installation You can also opt not to install nginx-ingress-controller from Gitlab by adding these two options when installing Gitlab: -set =true \ -set nginx-ingress.enabled=false \Ĭreate namespace for Gitlab installation kubectl create ns gitlab
![how to install gitlab runner on kubernetes how to install gitlab runner on kubernetes](https://miro.medium.com/max/1280/1*mg0r9TEWJvW9vdoNvgmrug.png)
kubectl delete svc nginx-ingress-controller -n ingress-nginx My cluster already has its nginx-ingress-controller, I will delete it to use the one from GitLab.