k8s实战案例之运行Java单体服务-jenkins

尚未崩坏  论坛元老 | 2023-8-7 11:19:22 | 显示全部楼层 | 阅读模式
打印 上一主题 下一主题
楼主

主题 1024|帖子 1024|积分 3072

1、jenkins架构


基于java命令，运⾏java war包或jar包，本次以jenkins.war 包部署⽅式为例，且要求jenkins的数据保存⾄外部存储(NFS或者PVC)，其他java应⽤看实际需求是否需要将数据保存⾄外部存储。
从上述架构图可以看到，Jenkins通过k8s上的pv/pvc来连接外部存储，通过svc的方式向外暴露服务，在集群内部通过直接访问svc就可以正常访问到jenkins，对于集群外部成员，通过外部负载均衡器来访问Jenkins；
2、镜像准备

2.1、Jenkins镜像目录文件
  1. root@k8s-master01:~/k8s-data/dockerfile/web/magedu/jenkins# tree
  2. .
  3. ├── Dockerfile
  4. ├── build-command.sh
  5. ├── jenkins-2.319.2.war
  6. └── run_jenkins.sh
  8. 0 directories, 4 files
  9. root@k8s-master01:~/k8s-data/dockerfile/web/magedu/jenkins#
复制代码
2.2、构建Jenkins镜像

2.2.1、构建Jenkins镜像Dockerfile
  1. root@k8s-master01:~/k8s-data/dockerfile/web/magedu/jenkins# cat Dockerfile
  2. #Jenkins Version 2.190.1
  3. FROM harbor.ik8s.cc/pub-images/jdk-base:v8.212
  5. ADD jenkins-2.319.2.war /apps/jenkins/jenkins.war
  6. ADD run_jenkins.sh /usr/bin/
  8. EXPOSE 8080
  10. CMD ["/usr/bin/run_jenkins.sh"]
  11. root@k8s-master01:~/k8s-data/dockerfile/web/magedu/jenkins#
复制代码
上述Dockerfile主要引用了一个jdk-base的镜像，该镜像有java环境，然后再这基础之上将jenkins war包和运行脚本加进去，然后暴露8080端口，最后给出运行jenkins的cmd命令；
2.2.2、运行jenkins 脚本
  1. root@k8s-master01:~/k8s-data/dockerfile/web/magedu/jenkins# cat run_jenkins.sh
  2. #!/bin/bash
  3. cd /apps/jenkins && java -server -Xms1024m -Xmx1024m -Xss512k -jar jenkins.war --webroot=/apps/jenkins/jenkins-data --httpPort=8080
  4. root@k8s-master01:~/k8s-data/dockerfile/web/magedu/jenkins#
复制代码
2.2.3、构建Jenkins镜像脚本
  1. root@k8s-master01:~/k8s-data/dockerfile/web/magedu/jenkins# cat build-command.sh
  2. #!/bin/bash
  3. #docker build -t  harbor.ik8s.cc/magedu/jenkins:v2.319.2 .
  4. #echo "镜像制作完成，即将上传至Harbor服务器"
  5. #sleep 1
  6. #docker push harbor.ik8s.cc/magedu/jenkins:v2.319.2
  7. #echo "镜像上传完成"
  9. echo "即将开始就像构建,请稍等!" && echo 3 && sleep 1 && echo 2 && sleep 1 && echo 1
  10. nerdctl build -t  harbor.ik8s.cc/magedu/jenkins:v2.319.2 .
  11. if [ $? -eq 0 ];then
  12.   echo "即将开始镜像上传,请稍等!" && echo 3 && sleep 1 && echo 2 && sleep 1 && echo 1
  13.   nerdctl push harbor.ik8s.cc/magedu/jenkins:v2.319.2
  14.   if [ $? -eq 0 ];then
  15.     echo "镜像上传成功!"
  16.   else
  17.     echo "镜像上传失败"
  18.   fi
  19. else
  20.   echo "镜像构建失败,请检查构建输出信息!"
  21. fi
  22. root@k8s-master01:~/k8s-data/dockerfile/web/magedu/jenkins#
复制代码
运行脚本构建镜像

2.3、验证Jenkins镜像

2.3.1、在harbor上查看对应jenkins镜像是否正常上传？


2.3.2、测试Jenkins镜像是否可以正常运行？


2.3.3、web访问jenkins是否可以正常访问？


能够看到上述页面，说明jenkins镜像制作没有问题;
3、准备PV/PVC

3.1、在nfs服务器上准备jenkins数据目录
  1. root@harbor:~# mkdir -p /data/k8sdata/magedu/{jenkins-data,jenkins-root-data}
  2. root@harbor:~# ll /data/k8sdata/magedu/{jenkins-data,jenkins-root-data}
  3. /data/k8sdata/magedu/jenkins-data:
  4. total 8
  5. drwxr-xr-x  2 root root 4096 Aug  6 03:35 ./
  6. drwxr-xr-x 21 root root 4096 Aug  6 03:35 ../
  8. /data/k8sdata/magedu/jenkins-root-data:
  9. total 8
  10. drwxr-xr-x  2 root root 4096 Aug  6 03:35 ./
  11. drwxr-xr-x 21 root root 4096 Aug  6 03:35 ../
  12. root@harbor:~# tail  /etc/exports
  14. /data/k8sdata/magedu/mysql-datadir-1 *(rw,no_root_squash)
  15. /data/k8sdata/magedu/mysql-datadir-2 *(rw,no_root_squash)
  16. /data/k8sdata/magedu/mysql-datadir-3 *(rw,no_root_squash)
  17. /data/k8sdata/magedu/mysql-datadir-4 *(rw,no_root_squash)
  18. /data/k8sdata/magedu/mysql-datadir-5 *(rw,no_root_squash)
  21. /data/k8sdata/magedu/jenkins-data *(rw,no_root_squash)
  22. /data/k8sdata/magedu/jenkins-root-data *(rw,no_root_squash)
  23. root@harbor:~# exportfs -av
  24. exportfs: /etc/exports [1]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/data/k8sdata/kuboard".
  25.   Assuming default behaviour ('no_subtree_check').
  26.   NOTE: this default has changed since nfs-utils version 1.0.x
  28. exportfs: /etc/exports [2]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/data/volumes".
  29.   Assuming default behaviour ('no_subtree_check').
  30.   NOTE: this default has changed since nfs-utils version 1.0.x
  32. exportfs: /etc/exports [3]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/pod-vol".
  33.   Assuming default behaviour ('no_subtree_check').
  34.   NOTE: this default has changed since nfs-utils version 1.0.x
  36. exportfs: /etc/exports [4]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/data/k8sdata/myserver".
  37.   Assuming default behaviour ('no_subtree_check').
  38.   NOTE: this default has changed since nfs-utils version 1.0.x
  40. exportfs: /etc/exports [5]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/data/k8sdata/mysite".
  41.   Assuming default behaviour ('no_subtree_check').
  42.   NOTE: this default has changed since nfs-utils version 1.0.x
  44. exportfs: /etc/exports [7]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/data/k8sdata/magedu/images".
  45.   Assuming default behaviour ('no_subtree_check').
  46.   NOTE: this default has changed since nfs-utils version 1.0.x
  48. exportfs: /etc/exports [8]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/data/k8sdata/magedu/static".
  49.   Assuming default behaviour ('no_subtree_check').
  50.   NOTE: this default has changed since nfs-utils version 1.0.x
  52. exportfs: /etc/exports [11]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/data/k8sdata/magedu/zookeeper-datadir-1".
  53.   Assuming default behaviour ('no_subtree_check').
  54.   NOTE: this default has changed since nfs-utils version 1.0.x
  56. exportfs: /etc/exports [12]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/data/k8sdata/magedu/zookeeper-datadir-2".
  57.   Assuming default behaviour ('no_subtree_check').
  58.   NOTE: this default has changed since nfs-utils version 1.0.x
  60. exportfs: /etc/exports [13]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/data/k8sdata/magedu/zookeeper-datadir-3".
  61.   Assuming default behaviour ('no_subtree_check').
  62.   NOTE: this default has changed since nfs-utils version 1.0.x
  64. exportfs: /etc/exports [16]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/data/k8sdata/magedu/redis-datadir-1".
  65.   Assuming default behaviour ('no_subtree_check').
  66.   NOTE: this default has changed since nfs-utils version 1.0.x
  68. exportfs: /etc/exports [18]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/data/k8sdata/magedu/redis0".
  69.   Assuming default behaviour ('no_subtree_check').
  70.   NOTE: this default has changed since nfs-utils version 1.0.x
  72. exportfs: /etc/exports [19]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/data/k8sdata/magedu/redis1".
  73.   Assuming default behaviour ('no_subtree_check').
  74.   NOTE: this default has changed since nfs-utils version 1.0.x
  76. exportfs: /etc/exports [20]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/data/k8sdata/magedu/redis2".
  77.   Assuming default behaviour ('no_subtree_check').
  78.   NOTE: this default has changed since nfs-utils version 1.0.x
  80. exportfs: /etc/exports [21]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/data/k8sdata/magedu/redis3".
  81.   Assuming default behaviour ('no_subtree_check').
  82.   NOTE: this default has changed since nfs-utils version 1.0.x
  84. exportfs: /etc/exports [22]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/data/k8sdata/magedu/redis4".
  85.   Assuming default behaviour ('no_subtree_check').
  86.   NOTE: this default has changed since nfs-utils version 1.0.x
  88. exportfs: /etc/exports [23]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/data/k8sdata/magedu/redis5".
  89.   Assuming default behaviour ('no_subtree_check').
  90.   NOTE: this default has changed since nfs-utils version 1.0.x
  92. exportfs: /etc/exports [27]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/data/k8sdata/magedu/mysql-datadir-1".
  93.   Assuming default behaviour ('no_subtree_check').
  94.   NOTE: this default has changed since nfs-utils version 1.0.x
  96. exportfs: /etc/exports [28]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/data/k8sdata/magedu/mysql-datadir-2".
  97.   Assuming default behaviour ('no_subtree_check').
  98.   NOTE: this default has changed since nfs-utils version 1.0.x
  100. exportfs: /etc/exports [29]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/data/k8sdata/magedu/mysql-datadir-3".
  101.   Assuming default behaviour ('no_subtree_check').
  102.   NOTE: this default has changed since nfs-utils version 1.0.x
  104. exportfs: /etc/exports [30]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/data/k8sdata/magedu/mysql-datadir-4".
  105.   Assuming default behaviour ('no_subtree_check').
  106.   NOTE: this default has changed since nfs-utils version 1.0.x
  108. exportfs: /etc/exports [31]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/data/k8sdata/magedu/mysql-datadir-5".
  109.   Assuming default behaviour ('no_subtree_check').
  110.   NOTE: this default has changed since nfs-utils version 1.0.x
  112. exportfs: /etc/exports [34]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/data/k8sdata/magedu/jenkins-data".
  113.   Assuming default behaviour ('no_subtree_check').
  114.   NOTE: this default has changed since nfs-utils version 1.0.x
  116. exportfs: /etc/exports [35]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/data/k8sdata/magedu/jenkins-root-data".
  117.   Assuming default behaviour ('no_subtree_check').
  118.   NOTE: this default has changed since nfs-utils version 1.0.x
  120. exporting *:/data/k8sdata/magedu/jenkins-root-data
  121. exporting *:/data/k8sdata/magedu/jenkins-data
  122. exporting *:/data/k8sdata/magedu/mysql-datadir-5
  123. exporting *:/data/k8sdata/magedu/mysql-datadir-4
  124. exporting *:/data/k8sdata/magedu/mysql-datadir-3
  125. exporting *:/data/k8sdata/magedu/mysql-datadir-2
  126. exporting *:/data/k8sdata/magedu/mysql-datadir-1
  127. exporting *:/data/k8sdata/magedu/redis5
  128. exporting *:/data/k8sdata/magedu/redis4
  129. exporting *:/data/k8sdata/magedu/redis3
  130. exporting *:/data/k8sdata/magedu/redis2
  131. exporting *:/data/k8sdata/magedu/redis1
  132. exporting *:/data/k8sdata/magedu/redis0
  133. exporting *:/data/k8sdata/magedu/redis-datadir-1
  134. exporting *:/data/k8sdata/magedu/zookeeper-datadir-3
  135. exporting *:/data/k8sdata/magedu/zookeeper-datadir-2
  136. exporting *:/data/k8sdata/magedu/zookeeper-datadir-1
  137. exporting *:/data/k8sdata/magedu/static
  138. exporting *:/data/k8sdata/magedu/images
  139. exporting *:/data/k8sdata/mysite
  140. exporting *:/data/k8sdata/myserver
  141. exporting *:/pod-vol
  142. exporting *:/data/volumes
  143. exporting *:/data/k8sdata/kuboard
  144. root@harbor:~#
复制代码
3.2、在k8s上创建pv
  1. ---
  2. apiVersion: v1
  3. kind: PersistentVolume
  4. metadata:
  5.   name: jenkins-datadir-pv
  6.   namespace: magedu
  7. spec:
  8.   capacity:
  9.     storage: 100Gi
  10.   accessModes:
  11.     - ReadWriteOnce
  12.   nfs:
  13.     server: 192.168.0.42
  14.     path: /data/k8sdata/magedu/jenkins-data
  16. ---
  17. apiVersion: v1
  18. kind: PersistentVolume
  19. metadata:
  20.   name: jenkins-root-datadir-pv
  21.   namespace: magedu
  22. spec:
  23.   capacity:
  24.     storage: 100Gi
  25.   accessModes:
  26.     - ReadWriteOnce
  27.   nfs:
  28.     server: 192.168.0.42
  29.     path: /data/k8sdata/magedu/jenkins-root-data
复制代码
  1. root@k8s-master01:~/k8s-data/yaml/magedu/jenkins/pv# kubectl apply  -f jenkins-persistentvolume.yaml
  2. persistentvolume/jenkins-datadir-pv created
  3. persistentvolume/jenkins-root-datadir-pv created
  4. root@k8s-master01:~/k8s-data/yaml/magedu/jenkins/pv#
复制代码
3.3、验证pv


3.4、在k8s上创建pvc
  1. ---
  2. apiVersion: v1
  3. kind: PersistentVolumeClaim
  4. metadata:
  5.   name: jenkins-datadir-pvc
  6.   namespace: magedu
  7. spec:
  8.   volumeName: jenkins-datadir-pv
  9.   accessModes:
  10.     - ReadWriteOnce
  11.   resources:
  12.     requests:
  13.       storage: 80Gi
  15. ---
  16. apiVersion: v1
  17. kind: PersistentVolumeClaim
  18. metadata:
  19.   name: jenkins-root-data-pvc
  20.   namespace: magedu
  21. spec:
  22.   volumeName: jenkins-root-datadir-pv
  23.   accessModes:
  24.     - ReadWriteOnce
  25.   resources:
  26.     requests:
  27.       storage: 80Gi
复制代码
  1. root@k8s-master01:~/k8s-data/yaml/magedu/jenkins/pv# kubectl apply -f jenkins-persistentvolumeclaim.yaml
  2. persistentvolumeclaim/jenkins-datadir-pvc created
  3. persistentvolumeclaim/jenkins-root-data-pvc created
  4. root@k8s-master01:~/k8s-data/yaml/magedu/jenkins/pv#
复制代码
3.5、验证pvc


4、准备在k8s上运行jenkins的yaml文件
  1. kind: Deployment
  2. #apiVersion: extensions/v1beta1
  3. apiVersion: apps/v1
  4. metadata:
  5.   labels:
  6.     app: magedu-jenkins
  7.   name: magedu-jenkins-deployment
  8.   namespace: magedu
  9. spec:
  10.   replicas: 1
  11.   selector:
  12.     matchLabels:
  13.       app: magedu-jenkins
  14.   template:
  15.     metadata:
  16.       labels:
  17.         app: magedu-jenkins
  18.     spec:
  19.       containers:
  20.       - name: magedu-jenkins-container
  21.         image: harbor.ik8s.cc/magedu/jenkins:v2.319.2
  22.         #imagePullPolicy: IfNotPresent
  23.         imagePullPolicy: Always
  24.         ports:
  25.         - containerPort: 8080
  26.           protocol: TCP
  27.           name: http
  28.         volumeMounts:
  29.         - mountPath: "/apps/jenkins/jenkins-data/"
  30.           name: jenkins-datadir-magedu
  31.         - mountPath: "/root/.jenkins"
  32.           name: jenkins-root-datadir
  33.       volumes:
  34.         - name: jenkins-datadir-magedu
  35.           persistentVolumeClaim:
  36.             claimName: jenkins-datadir-pvc
  37.         - name: jenkins-root-datadir
  38.           persistentVolumeClaim:
  39.             claimName: jenkins-root-data-pvc
  41. ---
  42. kind: Service
  43. apiVersion: v1
  44. metadata:
  45.   labels:
  46.     app: magedu-jenkins
  47.   name: magedu-jenkins-service
  48.   namespace: magedu
  49. spec:
  50.   type: NodePort
  51.   ports:
  52.   - name: http
  53.     port: 80
  54.     protocol: TCP
  55.     targetPort: 8080
  56.     nodePort: 38080
  57.   selector:
  58.     app: magedu-jenkins
复制代码
5、应用配置清单运行Jenkins
  1. root@k8s-master01:~/k8s-data/yaml/magedu/jenkins# kubectl apply -f jenkins.yaml
  2. deployment.apps/magedu-jenkins-deployment created
  3. service/magedu-jenkins-service created
  4. root@k8s-master01:~/k8s-data/yaml/magedu/jenkins#
复制代码
6、验证

6.1、验证Jenkins Pod是否正常运行？


6.2、验证web访问jenkins是否可正常访问？


查看jenkins密码
  1. root@k8s-master01:~/k8s-data/yaml/magedu/jenkins# kubectl get pods -n magedu
  2. NAME                                             READY   STATUS      RESTARTS        AGE
  3. magedu-jenkins-deployment-5f6899db-zn4xg         1/1     Running     0               11m
  4. magedu-nginx-deployment-5589bbf4bc-6gd2w         1/1     Running     12 (107m ago)   62d
  5. magedu-tomcat-app1-deployment-7754c8549c-c7rtb   1/1     Running     6 (108m ago)    62d
  6. magedu-tomcat-app1-deployment-7754c8549c-prglk   1/1     Running     6 (108m ago)    62d
  7. mysql-0                                          2/2     Running     4 (108m ago)    51d
  8. mysql-1                                          2/2     Running     4 (108m ago)    51d
  9. mysql-2                                          2/2     Running     4 (108m ago)    51d
  10. redis-0                                          1/1     Running     4 (108m ago)    60d
  11. redis-1                                          1/1     Running     4 (108m ago)    60d
  12. redis-2                                          1/1     Running     4 (108m ago)    60d
  13. redis-3                                          1/1     Running     4 (108m ago)    60d
  14. redis-4                                          1/1     Running     4 (108m ago)    60d
  15. redis-5                                          1/1     Running     4 (108m ago)    60d
  16. ubuntu1804                                       0/1     Completed   0               60d
  17. zookeeper1-675c5477cb-vmwwq                      1/1     Running     6 (108m ago)    62d
  18. zookeeper2-759fb6c6f-7jktr                       1/1     Running     6 (108m ago)    62d
  19. zookeeper3-5c78bb5974-vxpbh                      1/1     Running     6 (108m ago)    62d
  20. root@k8s-master01:~/k8s-data/yaml/magedu/jenkins# kubectl exec -it magedu-jenkins-deployment-5f6899db-zn4xg -n magedu  cat /root/.jenkins/secrets/initialAdminPassword
  21. kubectl exec [POD] [COMMAND] is DEPRECATED and will be removed in a future version. Use kubectl exec [POD] -- [COMMAND] instead.
  22. 8c4a17a8ecfe4fb88ed8701cb18340df
  23. root@k8s-master01:~/k8s-data/yaml/magedu/jenkins#
复制代码


ok，能够通过web网页正常访问到jenkins pod，到此jenkins服务就正常运行至k8s上了；后续可以通过外部负载均衡器将jenkins发布到集群外部成员访问；
7、在外部负载均衡器上发布jenkins

ha01
  1. root@k8s-ha01:~# cat /etc/keepalived/keepalived.conf
  2. ! Configuration File for keepalived
  3.   
  4. global_defs {
  5.    notification_email {
  6.      acassen
  7.    }
  8.    notification_email_from Alexandre.Cassen@firewall.loc
  9.    smtp_server 192.168.200.1
  10.    smtp_connect_timeout 30
  11.    router_id LVS_DEVEL
  12. }
  13.   
  14. vrrp_instance VI_1 {
  15.     state MASTER
  16.     interface ens160
  17.     garp_master_delay 10
  18.     smtp_alert
  19.     virtual_router_id 51
  20.     priority 100
  21.     advert_int 1
  22.     authentication {
  23.         auth_type PASS
  24.         auth_pass 1111
  25.     }
  26.     virtual_ipaddress {
  27.         192.168.0.111 dev ens160 label ens160:0
  28.         192.168.0.112 dev ens160 label ens160:1
  29.     }
  30. }
  31. root@k8s-ha01:~# cat /etc/haproxy/haproxy.cfg
  32. global
  33.         log /dev/log    local0
  34.         log /dev/log    local1 notice
  35.         chroot /var/lib/haproxy
  36.         stats socket /run/haproxy/admin.sock mode 660 level admin expose-fd listeners
  37.         stats timeout 30s
  38.         user haproxy
  39.         group haproxy
  40.         daemon
  42.         # Default SSL material locations
  43.         ca-base /etc/ssl/certs
  44.         crt-base /etc/ssl/private
  46.         # See: https://ssl-config.mozilla.org/#server=haproxy&server-version=2.0.3&config=intermediate
  47.         ssl-default-bind-ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384
  48.         ssl-default-bind-ciphersuites TLS_AES_128_GCM_SHA256:TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256
  49.         ssl-default-bind-options ssl-min-ver TLSv1.2 no-tls-tickets
  51. defaults
  52.         log     global
  53.         mode    http
  54.         option  httplog
  55.         option  dontlognull
  56.         timeout connect 5000
  57.         timeout client  50000
  58.         timeout server  50000
  59.         errorfile 400 /etc/haproxy/errors/400.http
  60.         errorfile 403 /etc/haproxy/errors/403.http
  61.         errorfile 408 /etc/haproxy/errors/408.http
  62.         errorfile 500 /etc/haproxy/errors/500.http
  63.         errorfile 502 /etc/haproxy/errors/502.http
  64.         errorfile 503 /etc/haproxy/errors/503.http
  65.         errorfile 504 /etc/haproxy/errors/504.http
  67. listen k8s_apiserver_6443
  68. bind 192.168.0.111:6443
  69. mode tcp
  70. #balance leastconn
  71. server k8s-master01 192.168.0.31:6443 check inter 2000 fall 3 rise 5
  72. server k8s-master02 192.168.0.32:6443 check inter 2000 fall 3 rise 5
  73. server k8s-master03 192.168.0.33:6443 check inter 2000 fall 3 rise 5
  75. listen jenkins_80
  76. bind 192.168.0.112:80
  77. mode tcp
  78. server k8s-node01 192.168.0.34:38080 check inter 2000 fall 3 rise 5
  79. server k8s-node02 192.168.0.35:38080 check inter 2000 fall 3 rise 5
  80. server k8s-node03 192.168.0.36:38080 check inter 2000 fall 3 rise 5
  81. root@k8s-ha01:~# systemctl restart keepalived haproxy
  82. root@k8s-ha01:~# ss -tnl
  83. State            Recv-Q            Send-Q                       Local Address:Port                       Peer Address:Port           Process           
  84. LISTEN           0                 4096                         192.168.0.111:6443                            0.0.0.0:*                                
  85. LISTEN           0                 4096                         192.168.0.112:80                              0.0.0.0:*                                
  86. LISTEN           0                 4096                         127.0.0.53%lo:53                              0.0.0.0:*                                
  87. LISTEN           0                 128                                0.0.0.0:22                              0.0.0.0:*                                
  88. root@k8s-ha01:~#
复制代码
ha02
  1. root@k8s-ha02:~# cat /etc/keepalived/keepalived.conf
  2. ! Configuration File for keepalived
  3.   
  4. global_defs {
  5.    notification_email {
  6.      acassen
  7.    }
  8.    notification_email_from Alexandre.Cassen@firewall.loc
  9.    smtp_server 192.168.200.1
  10.    smtp_connect_timeout 30
  11.    router_id LVS_DEVEL
  12. }
  13.   
  14. vrrp_instance VI_1 {
  15.     state BACKUP
  16.     interface ens160
  17.     garp_master_delay 10
  18.     smtp_alert
  19.     virtual_router_id 51
  20.     priority 70
  21.     advert_int 1
  22.     authentication {
  23.         auth_type PASS
  24.         auth_pass 1111
  25.     }
  26.     virtual_ipaddress {
  27.         192.168.0.111 dev ens160 label ens160:0
  28.         192.168.0.112 dev ens160 label ens160:1
  29.     }
  30. }
  31. root@k8s-ha02:~# cat /etc/haproxy/haproxy.cfg
  32. global
  33.         log /dev/log    local0
  34.         log /dev/log    local1 notice
  35.         chroot /var/lib/haproxy
  36.         stats socket /run/haproxy/admin.sock mode 660 level admin expose-fd listeners
  37.         stats timeout 30s
  38.         user haproxy
  39.         group haproxy
  40.         daemon
  42.         # Default SSL material locations
  43.         ca-base /etc/ssl/certs
  44.         crt-base /etc/ssl/private
  46.         # See: https://ssl-config.mozilla.org/#server=haproxy&server-version=2.0.3&config=intermediate
  47.         ssl-default-bind-ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384
  48.         ssl-default-bind-ciphersuites TLS_AES_128_GCM_SHA256:TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256
  49.         ssl-default-bind-options ssl-min-ver TLSv1.2 no-tls-tickets
  51. defaults
  52.         log     global
  53.         mode    http
  54.         option  httplog
  55.         option  dontlognull
  56.         timeout connect 5000
  57.         timeout client  50000
  58.         timeout server  50000
  59.         errorfile 400 /etc/haproxy/errors/400.http
  60.         errorfile 403 /etc/haproxy/errors/403.http
  61.         errorfile 408 /etc/haproxy/errors/408.http
  62.         errorfile 500 /etc/haproxy/errors/500.http
  63.         errorfile 502 /etc/haproxy/errors/502.http
  64.         errorfile 503 /etc/haproxy/errors/503.http
  65.         errorfile 504 /etc/haproxy/errors/504.http
  67. listen k8s_apiserver_6443
  68. bind 192.168.0.111:6443
  69. mode tcp
  70. #balance leastconn
  71. server k8s-master01 192.168.0.31:6443 check inter 2000 fall 3 rise 5
  72. server k8s-master02 192.168.0.32:6443 check inter 2000 fall 3 rise 5
  73. server k8s-master03 192.168.0.33:6443 check inter 2000 fall 3 rise 5
  76. listen jenkins_80
  77. bind 192.168.0.112:80
  78. mode tcp
  79. server k8s-node01 192.168.0.34:38080 check inter 2000 fall 3 rise 5
  80. server k8s-node02 192.168.0.35:38080 check inter 2000 fall 3 rise 5
  81. server k8s-node03 192.168.0.36:38080 check inter 2000 fall 3 rise 5
  82. root@k8s-ha02:~# systemctl restart keepalived haproxy
  83. root@k8s-ha02:~#
  84. root@k8s-ha02:~# ss -tnl
  85. State            Recv-Q            Send-Q                       Local Address:Port                       Peer Address:Port           Process           
  86. LISTEN           0                 4096                         192.168.0.111:6443                            0.0.0.0:*                                
  87. LISTEN           0                 4096                         192.168.0.112:80                              0.0.0.0:*                                
  88. LISTEN           0                 4096                         127.0.0.53%lo:53                              0.0.0.0:*                                
  89. LISTEN           0                 128                                0.0.0.0:22                              0.0.0.0:*                                
  90. root@k8s-ha02:~#
复制代码
7.1、访问负载均衡器的vip，看看是否能够访问到jenkins ?


能够正常通过访问负载均衡器的vip访问到jenkins，说明jenkins服务正常被负载均衡器反代成功；
        出处：https://www.cnblogs.com/qiuhom-1874/        本文版权归作者和博客园共有，欢迎转载，但未经作者同意必须保留此段声明，且在文章页面明显位置给出原文连接，否则保留追究法律责任的权利.
免责声明：如果侵犯了您的权益，请联系站长，我们会及时删除侵权内容，谢谢合作！

本帖子中包含更多资源

您需要 登录 才可以下载或查看，没有账号？立即注册

x
回复

使用道具 举报

0 个回复

倒序浏览
返回列表

快速回复

高级模式
B Color Image Link Quote Code Smilies
您需要登录后才可以回帖 登录 or 立即注册

本版积分规则

尚未崩坏

论坛元老
这个人很懒什么都没写!

楼主热帖

标签云

运维 CIO 存储 服务器
微信订阅号
微信服务号
微信客服
小程序
H5
关于我们 商务合作 网站地图
©Copyright 2022-2024 杭州祥升科技有限公司 版权所有 浙ICP备20004199号
快速回复 返回顶部 返回列表