Skip to content

The helm chart to deploy different prometheus resources (blackbox-servicemonitor-alertmanager-rule) on various k8s namesapaces

Notifications You must be signed in to change notification settings

rezaebrahimi1/helm-gitlabrunner-monitoring

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

8 Commits
 
 
 
 
 
 

Repository files navigation

helm-gitlabrunner-monitoring

The helm chart to deploy gitlab runner for configuring different prometheus resources (blackbox-servicemonitor-alertmanager-rule) on various k8s namesapaces. (see https://github.com/rezaebrahimi1/cd-thanos)

The required role are specified on role-gitlabrunner.yml file regarding least priviledge principle.

Installation

Helm considerations

The installation is done using helm. Change gitlabUrl, runnerRegistrationToken, clusterWideAccess, image, tags and protected values in values.yaml to your desired state.

Adjust roles for "default" SA

After creation of gitlab-runner namespace, the default SA (service account) will be created. Since this SA is utilized to deploy monitoring resources to k8s cluster namespaces, some extra role are added to it.

Deploy on k8s

Run following command respectively, to have a gitlab-runner instance on K8S cluster and also it's registration with your gitlab instance:

kubectl create ns gitlabrunner

kubectl create -f role-gitlabrunner.yaml

helm repo add gitlab https://charts.gitlab.io

helm repo update

helm upgrade --install gitlabrunner -n gitlabrunner -f values.yaml gitlab/gitlab-runner

After that you should see green status under Available specific runners part.

file:///home/reza/Downloads/gitlab-runner.pngimage

About

The helm chart to deploy different prometheus resources (blackbox-servicemonitor-alertmanager-rule) on various k8s namesapaces

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published