TOC: Introduction: 00:00 GitLab Runner Kubernetes Executor: 00:48 GitLab Runner Helm Chart: 03:28 Filling out the values.yaml file: 07:15 Install the Helm chart: 16:46 Run a GitLab CI pipeline: 20:06 Overview of GitLab Runner Operator and GitLab Agent: 22:43 Conclusion: 29:04

Thank you for sharing the knowledge, it's very helpful I was stuck before watching this. 🙌

Thanks so much for this, I was stuck until I watched it :)

Thanks for sharing. Helpful video, really enjoy it! Love the way you sharing, hope you keep it up!

@tech_with_moss

Жыл бұрын

Thank you! I'm glad it was valuable!

Thanks a lot for this video, works like a charm!

Thanks a lot. Now it is kinda clear for me. As you mentioned, official documentation is really messy

Excellent! Thank for share. Regards. 😃

thanks you a lot, wish you all the best!!

u deserve more subscribers!!

@tech_with_moss

Жыл бұрын

Thanks so much! I appreciate the kind words.

excelente bro, tienes que hacer uno sobre la conexión a un cluster de kubernetes personal y hacer deploy en el, saludos...

It's very good bro! Thanks

@tech_with_moss

Жыл бұрын

I'm glad you liked it!

brilliant viedeo, thank you so much for the video!

@tech_with_moss

Жыл бұрын

Im glad you liked it!

Thanks a lot Moss. It's clear for me. Can you please also show how create gitlab runner for windows machine too.

did you move .m2 inside your build directory? because whenever i tried to cache .m2 i used to get "not supported outside build directory". if so, how did you manipulate the maven docker image to move .m2 directory inside your $CI_PROJECT_DIR?

Can you cover adding S3 bucket for caching

Have you tried utilizing the runner to setup a docker network with a couple containers on it? I'm getting some hostname resolution issues.

Thank you!! please i have a qst i am using minikube and i want to install the gitlab runner over the cluster, do i have to do the installation from the controller node ?

Thank you so much for this. I am having issue using custom certificate when registering the gitlab runner in a GCP Kubernetes cluster. I am getting the error message x509; certificate signed by unknown authority. I have set the certsSecretName in the value.yaml file and still getting the error. Any idea on what to do

is the rapberry pi 4 powerful enough to be a good Gitlab runner? say I have 5 projects that uses the same pipeline with 6 jobs... and this 5 projects may have 10-20 pipeline triggers everyday...

Any update with the readiness probe error for the kubelet? Is it a token issue? When i initially deployed my runner into my eks cluster it was showing up in my projects, but now since this readiness probe error started showing up the executor is not showing up in my projects. I have tried helm uninstall and then re-installing with no luck

500th like on this VID - ITS MIIIIINE !!!

@tech_with_moss

7 ай бұрын

Congrats and thanks for the like!

If you want to add runners to the instance of gitlab-runner, are you supposed to edit the ConfigMap?

@kyleposluns1088

Жыл бұрын

Also, are you supposed to do one helm chart for each runner and one runner for each project? How do you update the helm chart with an additional runner?

I am able to install runner, pod is creating. But when I tried to run pipeline with runner it's not working.

but, my runner get error: Warning FailedMount 1s kubelet Unable to attach or mount volumes: unmounted volumes=[projected-secrets], unattached volumes=[projected-secrets etc-gitlab-runner configmaps custom-certs kube-api-access-fg9mr]: timed out waiting for the condition

I tried the same way, but Unable Gitlab-Runner did not get registered

HELP