Jenkinsのhelm chartをインストールした

github.com

を参考にインストールした

$ helm repo add jenkins https://charts.jenkins.io
$ helm repo update
$ helm install jenkins jenkins/jenkins

NAME: jenkins
LAST DEPLOYED: Sat Oct 30 16:21:03 2021
NAMESPACE: default
STATUS: deployed
REVISION: 1
NOTES:
1. Get your 'admin' user password by running:
  kubectl exec --namespace default -it svc/jenkins -c jenkins -- /bin/cat /run/secrets/chart-admin-password && echo
2. Get the Jenkins URL to visit by running these commands in the same shell:
  echo http://127.0.0.1:8080
  kubectl --namespace default port-forward svc/jenkins 8080:8080

3. Login with the password from step 1 and the username: admin
4. Configure security realm and authorization strategy
5. Use Jenkins Configuration as Code by specifying configScripts in your values.yaml file, see documentation: http:///configuration-as-code and examples: https://github.com/jenkinsci/configuration-as-code-plugin/tree/master/demos

For more information on running Jenkins on Kubernetes, visit:
https://cloud.google.com/solutions/jenkins-on-container-engine

For more information about Jenkins Configuration as Code, visit:
https://jenkins.io/projects/jcasc/

確認する

$ kubectl get all
NAME            READY   STATUS    RESTARTS   AGE
pod/jenkins-0   2/2     Running   0          110s

NAME                    TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)     AGE
service/kubernetes      ClusterIP   10.43.0.1       <none>        443/TCP     23h
service/jenkins         ClusterIP   10.43.24.242    <none>        8080/TCP    110s
service/jenkins-agent   ClusterIP   10.43.160.219   <none>        50000/TCP   110s

NAME                       READY   AGE
statefulset.apps/jenkins   1/1     110s

GitLabのhelmと比較するとpod数は少ないようである。 jenkinsは機能が疎結合にしていない感じなのか