返信元:
One step closer to having our #Jenkins be fully #Kubernetes at work. It's not like it was particularly difficult to set up, but more that there was enough bare metal resources allocated to the CI that it was a backlog item. Moving to k8s workers means those bare metal worker nodes can become k8s workers and be available for other workloads and devs can have more flexibility in directly defining their build environment requirements.
Deployed a #Rancher #k3s cluster with #Harvester, added a project/namespace for Jenkins, generated the kubeconfig with Rancher Manager, and then added it as a cloud provider in Jenkins. It was that easy. I made a basic pod template that runs a #Fedora image in the GUI, then created a Jenkinsfile in a #forgejo #git repo that did 6 parallel tasks. #Jenkins picked it up and it was fun to watch k8s pull the Fedora images and do it's thing from there.
