Scaling Jenkins on Kubernetes

#jenkins #kubernetes #docker
Why do we want to run Jenkins in Kubernetes? That might be your first question. You might not find a requirement to run Jenkins in K8s strait away. When your codebase grows larger or runs many jobs parallelly, Jenkins will grow very large. This will slow down your builds and lead to unnecessary resource utilization.

[harshal]

Thanks a ton, I was exactly looking for this, because we have thousands of jobs that runs daily on slave vms. Now got an better idea about it

[shuseiko]

Very nice explained in details the kubernetes-plugin option in jenkins.
I'll like to see how you handle the cluster with multi-nodes and shared persistent volumes. Specialy when you overwrite the default jnlp container.
Also your mic is too low sounding.

[nookalashashank]

Where is the kubectl get PVC -n Jenkins code

[shaikidur]

Hello kasun sameera, Thanks for sharing your knowledge it is help us a lot, I followed you same as what you shown, but I don't know what happen my case is showing pending—‘Jenkins’ is reserved for jobs with matching label expression not at all running.
Pleas give me any idea and suggestion.
Thanks in advance.

[omkarkulkarni]

Good tutorial..I am trying to setup Jenkins master slave on kubernetes. But i am facing 1 issue.Whenever Jenkins slave is launched.it launches a jnlp container along with with my custom maven container..Then problem i am facing is but default it runs the build under following path /home/jenkins/
looks like jnlp container creates a emptydir volume and mount at both container at /home/jenkins path..
But when i create a custom volume eg hostPath type.And define at pod and and mount at both containers.Still some how my build are performed under default /home/jenkins path..
Requesting for help if anyone has tried this..