倒排索引/搜索引擎>> minikube-helm-jenkins>> 返回
项目作者： houssoli

项目描述 ：
Jenkins master with dynamically spinned up Jenkins slaves on minikube.
高级语言：
项目地址: git://github.com/houssoli/minikube-helm-jenkins.git
创建时间： 2019-05-29T10:38:33Z
项目社区：https://github.com/houssoli/minikube-helm-jenkins
开源协议：MIT License
下载


minikube-helm-jenkins

This repository contains sample scripts to set up a persistent Jenkins master with dynamically spinned up Jenkins slaves on minikube.

Start minikube and use VirtualBox as VM driver

This will create a local one-node Kubernetes cluster in VirtualBox.

  1. minikube start — vm-driver=virtualbox

Alternatively, as I’m using a linux workstation, running the Kubernetes cluster directly on my local docker host by starting Minikube will require the —vm-driver=none option.

  1. minikube start --vm-driver=none --apiserver-ips 127.0.0.1 --apiserver-name localhost

Verify minikube is running

  1. minikube status
  1.     minikube: Running
  2.     cluster: Running
  3.     kubectl: Correctly Configured: pointing to minikube-vm at 192.168.99.100

Open the minikube dashboard by typing

  1. minikube dashboard

Create namespace

  1. kubectl create -f minikube/jenkins-namespace.yaml

Verify the namespace using the command

  1. kubectl get ns

Create persistent volume (folder /data is persistent on minikube)

Here the official minikube persistent_volumes documentation
In a multi-node Kubernetes cluster you’ll need some solution like NFS to make the mount directory available in the whole cluster.

  1. kubectl create -f minikube/jenkins-volume.yaml

Execute helm to deploy a Jenkins master-slave cluster

Here we will be using the Jenkins Helm Chart which aims to deploy Jenkins master and slave cluster utilizing the Jenkins Kubernetes plugin.
We use the jenkins-values.yaml to provide the template our own values which are necessary for our setup.
We will claim our volume and mount the Docker socket so we can execute Docker commands inside our slave pods.
Because we are using minikube we need to use NodePort as service type. Only cloud providers offer load balancers. We define port 32000 as port.
We can also define which plugins we want to install in our Jenkins. We use some default plugins like git and the pipeline plugin, but we also add the greenballs plugin which will show a green ball instead of a blue ball after a successful build.

  1. helm install --namespace jenkins-project --name jenkins -f helm/jenkins-values.yaml stable/jenkins
Expand to see what the output looks like



output NAME: jenkins LAST DEPLOYED: Wed May 29 13:23:15 2019 NAMESPACE: jenkins-project STATUS: DEPLOYED RESOURCES: ==> v1/ConfigMap NAME DATA AGE jenkins 6 0s jenkins-tests 1 0s ==> v1/Deployment NAME READY UP-TO-DATE AVAILABLE AGE jenkins 0/1 1 0 0s ==> v1/PersistentVolumeClaim NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE jenkins Bound jenkins-pv 20Gi RWO jenkins-pv 0s ==> v1/Pod(related) NAME READY STATUS RESTARTS AGE jenkins-6bcf9d87cc-sqd49 0/1 Init:0/1 0 0s ==> v1/Secret NAME TYPE DATA AGE jenkins Opaque 2 0s ==> v1/Service NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE jenkins NodePort 10.107.131.175 <none> 8080:32000/TCP 0s jenkins-agent ClusterIP 10.105.104.242 <none> 50000/TCP 0s ==> v1/ServiceAccount NAME SECRETS AGE jenkins 1 0s ==> v1beta1/ClusterRoleBinding NAME AGE jenkins-role-binding 0s NOTES: 1. Get your 'admin' user password by running: printf $(kubectl get secret --namespace jenkins-project jenkins -o jsonpath="{.data.jenkins-admin-password}" | base64 --decode);echo 2. Get the Jenkins URL to visit by running these commands in the same shell: export NODE_PORT=$(kubectl get --namespace jenkins-project -o jsonpath="{.spec.ports[0].nodePort}" services jenkins) export NODE_IP=$(kubectl get nodes --namespace jenkins-project -o jsonpath="{.items[0].status.addresses[0].address}") echo http://$NODE_IP:$NODE_PORT/login 3. Login with the password from step 1 and the username: admin For more information on running Jenkins on Kubernetes, visit: https://cloud.google.com/solutions/jenkins-on-container-engine Configure the Kubernetes plugin in Jenkins to use the following Service Account name jenkins using the following steps: Create a Jenkins credential of type Kubernetes service account with service account name jenkins Under configure Jenkins -- Update the credentials config in the cloud section to use the service account credential you created in the step above.


  1. kubectl -n jenkins-project get configmap,deployment,pvc,pod,secret,svc,serviceaccount,clusterrolebinding
Expand to see output



output NAME DATA AGE configmap/jenkins 6 4m44s configmap/jenkins-tests 1 4m44s NAME READY UP-TO-DATE AVAILABLE AGE deployment.extensions/jenkins 1/1 1 1 4m44s NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE persistentvolumeclaim/jenkins Bound jenkins-pv 20Gi RWO jenkins-pv 4m44s NAME READY STATUS RESTARTS AGE pod/jenkins-6bcf9d87cc-sqd49 1/1 Running 0 4m44s NAME TYPE DATA AGE secret/default-token-mxhmh kubernetes.io/service-account-token 3 45m secret/jenkins Opaque 2 4m44s secret/jenkins-token-qxlf8 kubernetes.io/service-account-token 3 4m44s NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/jenkins NodePort 10.107.131.175 <none> 8080:32000/TCP 4m44s service/jenkins-agent ClusterIP 10.105.104.242 <none> 50000/TCP 4m44s NAME SECRETS AGE serviceaccount/default 1 45m serviceaccount/jenkins 1 4m44s NAME AGE clusterrolebinding.rbac.authorization.k8s.io/cluster-admin 16h clusterrolebinding.rbac.authorization.k8s.io/jenkins-role-binding 4m44s clusterrolebinding.rbac.authorization.k8s.io/kubeadm:kubelet-bootstrap 16h clusterrolebinding.rbac.authorization.k8s.io/kubeadm:node-autoapprove-bootstrap 16h clusterrolebinding.rbac.authorization.k8s.io/kubeadm:node-autoapprove-certificate-rotation 16h clusterrolebinding.rbac.authorization.k8s.io/kubeadm:node-proxier 16h clusterrolebinding.rbac.authorization.k8s.io/minikube-rbac 16h clusterrolebinding.rbac.authorization.k8s.io/storage-provisioner 16h clusterrolebinding.rbac.authorization.k8s.io/system:aws-cloud-provider 16h clusterrolebinding.rbac.authorization.k8s.io/system:basic-user 16h clusterrolebinding.rbac.authorization.k8s.io/system:controller:attachdetach-controller 16h clusterrolebinding.rbac.authorization.k8s.io/system:controller:certificate-controller 16h clusterrolebinding.rbac.authorization.k8s.io/system:controller:clusterrole-aggregation-controller 16h clusterrolebinding.rbac.authorization.k8s.io/system:controller:cronjob-controller 16h clusterrolebinding.rbac.authorization.k8s.io/system:controller:daemon-set-controller 16h clusterrolebinding.rbac.authorization.k8s.io/system:controller:deployment-controller 16h clusterrolebinding.rbac.authorization.k8s.io/system:controller:disruption-controller 16h clusterrolebinding.rbac.authorization.k8s.io/system:controller:endpoint-controller 16h clusterrolebinding.rbac.authorization.k8s.io/system:controller:expand-controller 16h clusterrolebinding.rbac.authorization.k8s.io/system:controller:generic-garbage-collector 16h clusterrolebinding.rbac.authorization.k8s.io/system:controller:horizontal-pod-autoscaler 16h clusterrolebinding.rbac.authorization.k8s.io/system:controller:job-controller 16h clusterrolebinding.rbac.authorization.k8s.io/system:controller:namespace-controller 16h clusterrolebinding.rbac.authorization.k8s.io/system:controller:node-controller 16h clusterrolebinding.rbac.authorization.k8s.io/system:controller:persistent-volume-binder 16h clusterrolebinding.rbac.authorization.k8s.io/system:controller:pod-garbage-collector 16h clusterrolebinding.rbac.authorization.k8s.io/system:controller:pv-protection-controller 16h clusterrolebinding.rbac.authorization.k8s.io/system:controller:pvc-protection-controller 16h clusterrolebinding.rbac.authorization.k8s.io/system:controller:replicaset-controller 16h clusterrolebinding.rbac.authorization.k8s.io/system:controller:replication-controller 16h clusterrolebinding.rbac.authorization.k8s.io/system:controller:resourcequota-controller 16h clusterrolebinding.rbac.authorization.k8s.io/system:controller:route-controller 16h clusterrolebinding.rbac.authorization.k8s.io/system:controller:service-account-controller 16h clusterrolebinding.rbac.authorization.k8s.io/system:controller:service-controller 16h clusterrolebinding.rbac.authorization.k8s.io/system:controller:statefulset-controller 16h clusterrolebinding.rbac.authorization.k8s.io/system:controller:ttl-controller 16h clusterrolebinding.rbac.authorization.k8s.io/system:coredns 16h clusterrolebinding.rbac.authorization.k8s.io/system:discovery 16h clusterrolebinding.rbac.authorization.k8s.io/system:kube-controller-manager 16h clusterrolebinding.rbac.authorization.k8s.io/system:kube-dns 16h clusterrolebinding.rbac.authorization.k8s.io/system:kube-scheduler 16h clusterrolebinding.rbac.authorization.k8s.io/system:node 16h clusterrolebinding.rbac.authorization.k8s.io/system:node-proxier 16h clusterrolebinding.rbac.authorization.k8s.io/system:public-info-viewer 16h clusterrolebinding.rbac.authorization.k8s.io/system:volume-scheduler 16h


Verify the helm install

  1. helm ls
  1. NAME    REVISION        UPDATED                         STATUS          CHART           APP VERSION     NAMESPACE      
  2. jenkins 1               Wed May 29 20:23:34 2019        DEPLOYED        jenkins-0.28.9  lts             jenkins-project

Get the admin user password for jenkins

  1. printf $(kubectl get secret --namespace jenkins-project jenkins -o jsonpath="{.data.jenkins-admin-password}" | base64 --decode);echo
  3. O0wF7MjV2O

Get the Jenkins URL to visit within Minikube

In case of MiniKube cluster we will be using the minikube externalIP adress that can be found by issuing the command :

  1. export NODE_PORT=$(kubectl get --namespace jenkins-project -o jsonpath="{.spec.ports[0].nodePort}" services jenkins)
  2. export NODE_IP=$(minikube ip)
  3. echo http://$NODE_IP:$NODE_PORT/login

See also

  1. minikube service list
Expand to see output



output |-----------------|----------------------|-----------------------------| | NAMESPACE | NAME | URL | |-----------------|----------------------|-----------------------------| | default | kubernetes | No node port | | jenkins-project | jenkins | http://192.168.99.100:32000 | | jenkins-project | jenkins-agent | No node port | | kube-system | kube-dns | No node port | | kube-system | kubernetes-dashboard | No node port | | kube-system | tiller-deploy | No node port | |-----------------|----------------------|-----------------------------|


Get the Jenkins URL to visit (when not in minikube, like with the —vm-driver=none option)

  1. export NODE_PORT=$(kubectl get --namespace jenkins-project -o jsonpath="{.spec.ports[0].nodePort}" services jenkins)
  2. export NODE_IP=$(kubectl get nodes --namespace jenkins-project -o jsonpath="{.items[0].status.addresses[0].address}")
  3. echo http://$NODE_IP:$NODE_PORT/login

Get more information

  1. kubectl get nodes --namespace jenkins-project -o yaml

This implementation is following a full tutorial which can be found @lvthillo/deploy-jenkins-with-dynamic-slaves-in-minikube-8aef5404e9c1">here, thank to @lvthillo"">@lvthillo.