1. 实验环境

image.png

image.png

image.png

2. 安装前准备

2.1. 环境准备

所有机器都需要执行

  1. [root@hdss7-11 ~]# systemctl stop firewalld
  2. [root@hdss7-11 ~]# systemctl disable firewalld
  3. [root@hdss7-11 ~]# setenforce 0
  4. [root@hdss7-11 ~]# sed -ir '/^SELINUX=/s/=.+/=disabled/' /etc/selinux/config
  5. [root@hdss7-11 ~]# yum install -y epel-release
  6. [root@hdss7-11 ~]# yum install -y wget net-tools telnet tree nmap sysstat lrzsz dos2unix bind-utils vim less

2.2. bind安装

2.2.1. hdss7-11 安装bind

  1. [root@hdss7-11 ~]# yum install -y bind

2.2.2. hdss7-11 配置bind

  • 主配置文件
  1. [root@hdss7-11 ~]# vim /etc/named.conf # 确保以下配置正确
  2. listen-on port 53 { 10.4.7.11; };
  3. directory "/var/named";
  4. allow-query { any; };
  5. forwarders { 10.4.7.254; };
  6. recursion yes;
  7. dnssec-enable no;
  8. dnssec-validation no;
  • 在 hdss7-11.host.com 配置区域文件
  1. # 增加两个zone配置,od.com为业务域,host.com.zone为主机域
  2. [root@hdss7-11 ~]# vim /etc/named.rfc1912.zones
  3. zone "host.com" IN {
  4. type master;
  5. file "host.com.zone";
  6. allow-update { 10.4.7.11; };
  7. };
  8. zone "od.com" IN {
  9. type master;
  10. file "od.com.zone";
  11. allow-update { 10.4.7.11; };
  12. };
  • 在 hdss7-11.host.com 配置主机域文件
  1. # line6中时间需要修改
  2. [root@hdss7-11 ~]# vim /var/named/host.com.zone
  3. $ORIGIN host.com.
  4. $TTL 600 ; 10 minutes
  5. @ IN SOA dns.host.com. dnsadmin.host.com. (
  6. 2020010501 ; serial
  7. 10800 ; refresh (3 hours)
  8. 900 ; retry (15 minutes)
  9. 604800 ; expire (1 week)
  10. 86400 ; minimum (1 day)
  11. )
  12. NS dns.host.com.
  13. $TTL 60 ; 1 minute
  14. dns A 10.4.7.11
  15. HDSS7-11 A 10.4.7.11
  16. HDSS7-12 A 10.4.7.12
  17. HDSS7-21 A 10.4.7.21
  18. HDSS7-22 A 10.4.7.22
  19. HDSS7-200 A 10.4.7.200
  • 在 hdss7-11.host.com 配置业务域文件
  1. [root@hdss7-11 ~]# vim /var/named/od.com.zone
  2. $ORIGIN od.com.
  3. $TTL 600 ; 10 minutes
  4. @ IN SOA dns.od.com. dnsadmin.od.com. (
  5. 2020010501 ; serial
  6. 10800 ; refresh (3 hours)
  7. 900 ; retry (15 minutes)
  8. 604800 ; expire (1 week)
  9. 86400 ; minimum (1 day)
  10. )
  11. NS dns.od.com.
  12. $TTL 60 ; 1 minute
  13. dns A 10.4.7.11
  • 在 hdss7-11.host.com 启动bind服务,并测试
  1. [root@hdss7-11 ~]# named-checkconf # 检查配置文件
  2. [root@hdss7-11 ~]# systemctl start named ; systemctl enable named
  3. [root@hdss7-11 ~]# host HDSS7-200 10.4.7.11
  4. Using domain server:
  5. Name: 10.4.7.11
  6. Address: 10.4.7.11#53
  7. Aliases:
  8. HDSS7-200.host.com has address 10.4.7.200

2.2.3. 修改主机DNS

  • 修改所有主机的dns服务器地址
  1. [root@hdss7-11 ~]# sed -i '/DNS1/s/10.4.7.254/10.4.7.11/' /etc/sysconfig/network-scripts/ifcfg-ens32
  2. [root@hdss7-11 ~]# systemctl restart network
  3. [root@hdss7-11 ~]# cat /etc/resolv.conf
  4. # Generated by NetworkManager
  5. search host.com
  6. nameserver 10.4.7.11
  • 本次实验环境使用的是虚拟机,因此也要对windows宿主机NAT网卡DNS进行修改

image.png
image.png

2.3. 根证书准备

  • 在 hdss7-200 下载工具
  1. [root@hdss7-200 ~]# wget https://pkg.cfssl.org/R1.2/cfssl_linux-amd64 -O /usr/local/bin/cfssl
  2. [root@hdss7-200 ~]# wget https://pkg.cfssl.org/R1.2/cfssljson_linux-amd64 -O /usr/local/bin/cfssl-json
  3. [root@hdss7-200 ~]# wget https://pkg.cfssl.org/R1.2/cfssl-certinfo_linux-amd64 -O /usr/local/bin/cfssl-certinfo
  4. [root@hdss7-200 ~]# chmod u+x /usr/local/bin/cfssl*
  • 在 hdss7-200 签发根证书
  1. [root@hdss7-200 ~]# mkdir /opt/certs/ ; cd /opt/certs/
  2. # 根证书配置:
  3. # CN 一般写域名,浏览器会校验
  4. # names 为地区和公司信息
  5. # expiry 为过期时间
  6. [root@hdss7-200 certs]# vim /opt/certs/ca-csr.json
  7. {
  8. "CN": "OldboyEdu",
  9. "hosts": [
  10. ],
  11. "key": {
  12. "algo": "rsa",
  13. "size": 2048
  14. },
  15. "names": [
  16. {
  17. "C": "CN",
  18. "ST": "beijing",
  19. "L": "beijing",
  20. "O": "od",
  21. "OU": "ops"
  22. }
  23. ],
  24. "ca": {
  25. "expiry": "175200h"
  26. }
  27. }
  28. [root@hdss7-200 certs]# cfssl gencert -initca ca-csr.json | cfssl-json -bare ca
  29. 2020/01/05 10:42:07 [INFO] generating a new CA key and certificate from CSR
  30. 2020/01/05 10:42:07 [INFO] generate received request
  31. 2020/01/05 10:42:07 [INFO] received CSR
  32. 2020/01/05 10:42:07 [INFO] generating key: rsa-2048
  33. 2020/01/05 10:42:08 [INFO] encoded CSR
  34. 2020/01/05 10:42:08 [INFO] signed certificate with serial number 451005524427475354617025362003367427117323539780
  35. [root@hdss7-200 certs]# ls -l ca*
  36. -rw-r--r-- 1 root root 993 Jan 5 10:42 ca.csr
  37. -rw-r--r-- 1 root root 328 Jan 5 10:39 ca-csr.json
  38. -rw------- 1 root root 1675 Jan 5 10:42 ca-key.pem
  39. -rw-r--r-- 1 root root 1346 Jan 5 10:42 ca.pem

2.4. docker环境准备

需要安装docker的机器:hdss7-21 hdss7-22 hdss7-200,以hdss7-21为例

  1. [root@hdss7-21 ~]# wget -O /etc/yum.repos.d/docker-ce.repo https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo
  2. [root@hdss7-21 ~]# yum install -y docker-ce
  3. [root@hdss7-21 ~]# mkdir /etc/docker/
  4. # 不安全的registry中增加了harbor地址
  5. # 各个机器上bip网段不一致,bip中间两段与宿主机最后两段相同,目的是方便定位问题
  6. [root@hdss7-21 ~]# vim /etc/docker/daemon.json
  7. {
  8. "graph": "/data/docker",
  9. "storage-driver": "overlay2",
  10. "insecure-registries": ["registry.access.redhat.com","quay.io","harbor.od.com"],
  11. "registry-mirrors": ["https://registry.docker-cn.com"],
  12. "bip": "172.7.21.1/24",
  13. "exec-opts": ["native.cgroupdriver=systemd"],
  14. "live-restore": true
  15. }
  16. [root@hdss7-21 ~]# mkdir /data/docker
  17. [root@hdss7-21 ~]# systemctl start docker ; systemctl enable docker

2.5. harbor安装

参考地址:https://www.yuque.com/duduniao/trp3ic/ohrxds#9Zpxx
官方地址:https://goharbor.io/
下载地址:https://github.com/goharbor/harbor/releases

2.5.1. hdss7-200 安装harbor

  1. # 目录说明:
  2. # /opt/src : 源码、文件下载目录
  3. # /opt/release : 各个版本软件存放位置
  4. # /opt/apps : 各个软件当前版本的软链接
  5. [root@hdss7-200 ~]# cd /opt/src
  6. [root@hdss7-200 src]# wget https://github.com/goharbor/harbor/releases/download/v1.9.4/harbor-offline-installer-v1.9.4.tgz
  7. [root@hdss7-200 src]# mv harbor /opt/release/harbor-v1.9.4
  8. [root@hdss7-200 src]# ln -s /opt/release/harbor-v1.9.4 /opt/apps/harbor
  9. [root@hdss7-200 src]# ll /opt/apps/
  10. total 0
  11. lrwxrwxrwx 1 root root 26 Jan 5 11:13 harbor -> /opt/release/harbor-v1.9.4
  12. # 实验环境仅修改以下配置项,生产环境还得修改密码
  13. [root@hdss7-200 src]# vim /opt/apps/harbor/harbor.yml
  14. hostname: harbor.od.com
  15. http:
  16. port: 180
  17. data_volume: /data/harbor
  18. location: /data/harbor/logs
  19. [root@hdss7-200 src]# yum install -y docker-compose
  20. [root@hdss7-200 src]# cd /opt/apps/harbor/
  21. [root@hdss7-200 harbor]# ./install.sh
  22. ......
  23. ----Harbor has been installed and started successfully.----
  24. [root@hdss7-200 harbor]# docker-compose ps
  25. Name Command State Ports
  26. --------------------------------------------------------------------------------------
  27. harbor-core /harbor/harbor_core Up
  28. harbor-db /docker-entrypoint.sh Up 5432/tcp
  29. harbor-jobservice /harbor/harbor_jobservice ... Up
  30. harbor-log /bin/sh -c /usr/local/bin/ ... Up 127.0.0.1:1514->10514/tcp
  31. harbor-portal nginx -g daemon off; Up 8080/tcp
  32. nginx nginx -g daemon off; Up 0.0.0.0:180->8080/tcp
  33. redis redis-server /etc/redis.conf Up 6379/tcp
  34. registry /entrypoint.sh /etc/regist ... Up 5000/tcp
  35. registryctl /harbor/start.sh Up
  • 设置harbor开机启动
  1. [root@hdss7-200 harbor]# vim /etc/rc.d/rc.local # 增加以下内容
  2. # start harbor
  3. cd /opt/apps/harbor
  4. /usr/bin/docker-compose stop
  5. /usr/bin/docker-compose start

2.5.2. hdss7-200 安装nginx

  • 安装Nginx反向代理harbor
  1. # 当前机器中Nginx功能较少,使用yum安装即可。如有多个harbor考虑源码编译且配置健康检查
  2. # nginx配置此处忽略,仅仅使用最简单的配置。
  3. [root@hdss7-200 harbor]# vim /etc/nginx/conf.d/harbor.conf
  4. [root@hdss7-200 harbor]# cat /etc/nginx/conf.d/harbor.conf
  5. server {
  6. listen 80;
  7. server_name harbor.od.com;
  8. # 避免出现上传失败的情况
  9. client_max_body_size 1000m;
  10. location / {
  11. proxy_pass http://127.0.0.1:180;
  12. }
  13. }
  14. [root@hdss7-200 harbor]# systemctl start nginx ; systemctl enable nginx
  • hdss7-11 配置DNS解析
  1. [root@hdss7-11 ~]# vim /var/named/od.com.zone # 序列号需要滚动一个
  2. $ORIGIN od.com.
  3. $TTL 600 ; 10 minutes
  4. @ IN SOA dns.od.com. dnsadmin.od.com. (
  5. 2020010502 ; serial
  6. 10800 ; refresh (3 hours)
  7. 900 ; retry (15 minutes)
  8. 604800 ; expire (1 week)
  9. 86400 ; minimum (1 day)
  10. )
  11. NS dns.od.com.
  12. $TTL 60 ; 1 minute
  13. dns A 10.4.7.11
  14. harbor A 10.4.7.200
  15. [root@hdss7-11 ~]# systemctl restart named.service # reload 无法使得配置生效
  16. [root@hdss7-11 ~]# host harbor.od.com
  17. harbor.od.com has address 10.4.7.200

image.png

  • 新建项目: public

image.png

  • 测试harbor
  1. [root@hdss7-21 ~]# docker image tag nginx:latest harbor.od.com/public/nginx:latest
  2. [root@hdss7-21 ~]# docker login -u admin harbor.od.com
  3. [root@hdss7-21 ~]# docker image push harbor.od.com/public/nginx:latest
  4. [root@hdss7-21 ~]# docker logout

image.png

3. 主控节点安装

3.1. etcd安装

etcd 的leader选举机制,要求至少为3台或以上的奇数台。本次安装涉及:hdss7-12,hdss7-21,hdss7-22

3.1.1. 签发etcd证书

证书签发服务器 hdss7-200:

  • 创建ca的json配置: /opt/certs/ca-config.json

    • server 表示服务端连接客户端时携带的证书,用于客户端验证服务端身份
    • client 表示客户端连接服务端时携带的证书,用于服务端验证客户端身份
    • peer 表示相互之间连接时使用的证书,如etcd节点之间验证
  1. {
  2. "signing": {
  3. "default": {
  4. "expiry": "175200h"
  5. },
  6. "profiles": {
  7. "server": {
  8. "expiry": "175200h",
  9. "usages": [
  10. "signing",
  11. "key encipherment",
  12. "server auth"
  13. ]
  14. },
  15. "client": {
  16. "expiry": "175200h",
  17. "usages": [
  18. "signing",
  19. "key encipherment",
  20. "client auth"
  21. ]
  22. },
  23. "peer": {
  24. "expiry": "175200h",
  25. "usages": [
  26. "signing",
  27. "key encipherment",
  28. "server auth",
  29. "client auth"
  30. ]
  31. }
  32. }
  33. }
  34. }
  • 创建etcd证书配置:/opt/certs/etcd-peer-csr.json

重点在hosts上,将所有可能的etcd服务器添加到host列表,不能使用网段,新增etcd服务器需要重新签发证书

  1. {
  2. "CN": "k8s-etcd",
  3. "hosts": [
  4. "10.4.7.11",
  5. "10.4.7.12",
  6. "10.4.7.21",
  7. "10.4.7.22"
  8. ],
  9. "key": {
  10. "algo": "rsa",
  11. "size": 2048
  12. },
  13. "names": [
  14. {
  15. "C": "CN",
  16. "ST": "beijing",
  17. "L": "beijing",
  18. "O": "od",
  19. "OU": "ops"
  20. }
  21. ]
  22. }
  • 签发证书
  1. [root@hdss7-200 ~]# cd /opt/certs/
  2. [root@hdss7-200 certs]# cfssl gencert -ca=ca.pem -ca-key=ca-key.pem -config=ca-config.json -profile=peer etcd-peer-csr.json |cfssl-json -bare etcd-peer
  3. [root@hdss7-200 certs]# ll etcd-peer*
  4. -rw-r--r-- 1 root root 1062 Jan 5 17:01 etcd-peer.csr
  5. -rw-r--r-- 1 root root 363 Jan 5 16:59 etcd-peer-csr.json
  6. -rw------- 1 root root 1675 Jan 5 17:01 etcd-peer-key.pem
  7. -rw-r--r-- 1 root root 1428 Jan 5 17:01 etcd-peer.pem

3.1.2. 安装etcd

etcd地址:https://github.com/etcd-io/etcd/
实验使用版本: etcd-v3.1.20-linux-amd64.tar.gz
本次安装涉及:hdss7-12,hdss7-21,hdss7-22

  • 下载etcd
  1. [root@hdss7-12 ~]# useradd -s /sbin/nologin -M etcd
  2. [root@hdss7-12 ~]# cd /opt/src/
  3. [root@hdss7-12 src]# wget https://github.com/etcd-io/etcd/releases/download/v3.1.20/etcd-v3.1.20-linux-amd64.tar.gz
  4. [root@hdss7-12 src]# tar -xf etcd-v3.1.20-linux-amd64.tar.gz
  5. [root@hdss7-12 src]# mv etcd-v3.1.20-linux-amd64 /opt/release/etcd-v3.1.20
  6. [root@hdss7-12 src]# ln -s /opt/release/etcd-v3.1.20 /opt/apps/etcd
  7. [root@hdss7-12 src]# ll /opt/apps/etcd
  8. lrwxrwxrwx 1 root root 25 Jan 5 17:56 /opt/apps/etcd -> /opt/release/etcd-v3.1.20
  9. [root@hdss7-12 src]# mkdir -p /opt/apps/etcd/certs /data/etcd /data/logs/etcd-server
  • 下发证书到各个etcd上
  1. [root@hdss7-200 ~]# cd /opt/certs/
  2. [root@hdss7-200 certs]# for i in 12 21 22;do scp ca.pem etcd-peer.pem etcd-peer-key.pem hdss7-${i}:/opt/apps/etcd/certs/ ;done
  1. [root@hdss7-12 src]# md5sum /opt/apps/etcd/certs/*
  2. 8778d0c3411891af61a287e49a70c89a /opt/apps/etcd/certs/ca.pem
  3. 7918783c2f6bf69e96edf03e67d04983 /opt/apps/etcd/certs/etcd-peer-key.pem
  4. d4d849751a834c7727d42324fdedf92d /opt/apps/etcd/certs/etcd-peer.pem
  • 创建启动脚本(部分参数每台机器不同)
  1. [root@hdss7-12 ~]# vim /opt/apps/etcd/etcd-server-startup.sh
  2. #!/bin/sh
  3. # listen-peer-urls etcd节点之间通信端口
  4. # listen-client-urls 客户端与etcd通信端口
  5. # quota-backend-bytes 配额大小
  6. # 需要修改的参数:name,listen-peer-urls,listen-client-urls,initial-advertise-peer-urls
  7. WORK_DIR=$(dirname $(readlink -f $0))
  8. [ $? -eq 0 ] && cd $WORK_DIR || exit
  9. /opt/apps/etcd/etcd --name etcd-server-7-12 \
  10. --data-dir /data/etcd/etcd-server \
  11. --listen-peer-urls https://10.4.7.12:2380 \
  12. --listen-client-urls https://10.4.7.12:2379,http://127.0.0.1:2379 \
  13. --quota-backend-bytes 8000000000 \
  14. --initial-advertise-peer-urls https://10.4.7.12:2380 \
  15. --advertise-client-urls https://10.4.7.12:2379,http://127.0.0.1:2379 \
  16. --initial-cluster etcd-server-7-12=https://10.4.7.12:2380,etcd-server-7-21=https://10.4.7.21:2380,etcd-server-7-22=https://10.4.7.22:2380 \
  17. --ca-file ./certs/ca.pem \
  18. --cert-file ./certs/etcd-peer.pem \
  19. --key-file ./certs/etcd-peer-key.pem \
  20. --client-cert-auth \
  21. --trusted-ca-file ./certs/ca.pem \
  22. --peer-ca-file ./certs/ca.pem \
  23. --peer-cert-file ./certs/etcd-peer.pem \
  24. --peer-key-file ./certs/etcd-peer-key.pem \
  25. --peer-client-cert-auth \
  26. --peer-trusted-ca-file ./certs/ca.pem \
  27. --log-output stdout
  1. [root@hdss7-12 ~]# chmod u+x /opt/apps/etcd/etcd-server-startup.sh
  2. [root@hdss7-12 ~]# chown -R etcd.etcd /opt/apps/etcd/ /data/etcd /data/logs/etcd-server

3.1.3. 启动etcd

因为这些进程都是要启动为后台进程,要么手动启动,要么采用后台进程管理工具,实验中使用后台管理工具

  1. [root@hdss7-12 ~]# yum install -y supervisor
  2. [root@hdss7-12 ~]# systemctl start supervisord ; systemctl enable supervisord
  3. [root@hdss7-12 ~]# vim /etc/supervisord.d/etcd-server.ini
  4. [program:etcd-server-7-12]
  5. command=/opt/apps/etcd/etcd-server-startup.sh ; the program (relative uses PATH, can take args)
  6. numprocs=1 ; number of processes copies to start (def 1)
  7. directory=/opt/apps/etcd ; directory to cwd to before exec (def no cwd)
  8. autostart=true ; start at supervisord start (default: true)
  9. autorestart=true ; retstart at unexpected quit (default: true)
  10. startsecs=30 ; number of secs prog must stay running (def. 1)
  11. startretries=3 ; max # of serial start failures (default 3)
  12. exitcodes=0,2 ; 'expected' exit codes for process (default 0,2)
  13. stopsignal=QUIT ; signal used to kill process (default TERM)
  14. stopwaitsecs=10 ; max num secs to wait b4 SIGKILL (default 10)
  15. user=etcd ; setuid to this UNIX account to run the program
  16. redirect_stderr=true ; redirect proc stderr to stdout (default false)
  17. stdout_logfile=/data/logs/etcd-server/etcd.stdout.log ; stdout log path, NONE for none; default AUTO
  18. stdout_logfile_maxbytes=64MB ; max # logfile bytes b4 rotation (default 50MB)
  19. stdout_logfile_backups=5 ; # of stdout logfile backups (default 10)
  20. stdout_capture_maxbytes=1MB ; number of bytes in 'capturemode' (default 0)
  21. stdout_events_enabled=false ; emit events on stdout writes (default false)
  22. [root@hdss7-12 ~]# supervisorctl update
  23. etcd-server-7-12: added process group
  • etcd 进程状态查看
  1. [root@hdss7-12 ~]# supervisorctl status # supervisorctl 状态
  2. etcd-server-7-12 RUNNING pid 22375, uptime 0:00:39
  3. [root@hdss7-12 ~]# netstat -lntp|grep etcd
  4. tcp 0 0 10.4.7.12:2379 0.0.0.0:* LISTEN 22379/etcd
  5. tcp 0 0 127.0.0.1:2379 0.0.0.0:* LISTEN 22379/etcd
  6. tcp 0 0 10.4.7.12:2380 0.0.0.0:* LISTEN 22379/etcd
  7. [root@hdss7-12 ~]# /opt/apps/etcd/etcdctl member list # 随着etcd重启,leader会变化
  8. 988139385f78284: name=etcd-server-7-22 peerURLs=https://10.4.7.22:2380 clientURLs=http://127.0.0.1:2379,https://10.4.7.22:2379 isLeader=false
  9. 5a0ef2a004fc4349: name=etcd-server-7-21 peerURLs=https://10.4.7.21:2380 clientURLs=http://127.0.0.1:2379,https://10.4.7.21:2379 isLeader=true
  10. f4a0cb0a765574a8: name=etcd-server-7-12 peerURLs=https://10.4.7.12:2380 clientURLs=http://127.0.0.1:2379,https://10.4.7.12:2379 isLeader=false
  11. [root@hdss7-12 ~]# /opt/apps/etcd/etcdctl cluster-health
  12. member 988139385f78284 is healthy: got healthy result from http://127.0.0.1:2379
  13. member 5a0ef2a004fc4349 is healthy: got healthy result from http://127.0.0.1:2379
  14. member f4a0cb0a765574a8 is healthy: got healthy result from http://127.0.0.1:2379
  15. cluster is healthy
  • etcd 启停方式
  1. [root@hdss7-12 ~]# supervisorctl start etcd-server-7-12
  2. [root@hdss7-12 ~]# supervisorctl stop etcd-server-7-12
  3. [root@hdss7-12 ~]# supervisorctl restart etcd-server-7-12
  4. [root@hdss7-12 ~]# supervisorctl status etcd-server-7-12

3.2. apiserver 安装

3.2.1. 下载kubernetes服务端

aipserver 涉及的服务器:hdss7-21,hdss7-22
下载 kubernetes 二进制版本包需要科学上网工具

  1. [root@hdss7-21 ~]# cd /opt/src
  2. [root@hdss7-21 src]# wget https://dl.k8s.io/v1.15.2/kubernetes-server-linux-amd64.tar.gz
  3. [root@hdss7-21 src]# tar -xf kubernetes-server-linux-amd64.tar.gz
  4. [root@hdss7-21 src]# mv kubernetes /opt/release/kubernetes-v1.15.2
  5. [root@hdss7-21 src]# ln -s /opt/release/kubernetes-v1.15.2 /opt/apps/kubernetes
  6. [root@hdss7-21 src]# ll /opt/apps/kubernetes
  7. lrwxrwxrwx 1 root root 31 Jan 6 12:59 /opt/apps/kubernetes -> /opt/release/kubernetes-v1.15.2
  8. [root@hdss7-21 src]# cd /opt/apps/kubernetes
  9. [root@hdss7-21 kubernetes]# rm -f kubernetes-src.tar.gz
  10. [root@hdss7-21 kubernetes]# cd server/bin/
  11. [root@hdss7-21 bin]# rm -f *.tar *_tag # *.tar *_tag 镜像文件
  12. [root@hdss7-21 bin]# ll
  13. total 884636
  14. -rwxr-xr-x 1 root root 43534816 Aug 5 18:01 apiextensions-apiserver
  15. -rwxr-xr-x 1 root root 100548640 Aug 5 18:01 cloud-controller-manager
  16. -rwxr-xr-x 1 root root 200648416 Aug 5 18:01 hyperkube
  17. -rwxr-xr-x 1 root root 40182208 Aug 5 18:01 kubeadm
  18. -rwxr-xr-x 1 root root 164501920 Aug 5 18:01 kube-apiserver
  19. -rwxr-xr-x 1 root root 116397088 Aug 5 18:01 kube-controller-manager
  20. -rwxr-xr-x 1 root root 42985504 Aug 5 18:01 kubectl
  21. -rwxr-xr-x 1 root root 119616640 Aug 5 18:01 kubelet
  22. -rwxr-xr-x 1 root root 36987488 Aug 5 18:01 kube-proxy
  23. -rwxr-xr-x 1 root root 38786144 Aug 5 18:01 kube-scheduler
  24. -rwxr-xr-x 1 root root 1648224 Aug 5 18:01 mounter

3.2.2. 签发证书

签发证书 涉及的服务器:hdss7-200

  • 签发client证书(apiserver和etcd通信证书)
  1. [root@hdss7-200 ~]# cd /opt/certs/
  2. [root@hdss7-200 certs]# vim /opt/certs/client-csr.json
  3. {
  4. "CN": "k8s-node",
  5. "hosts": [
  6. ],
  7. "key": {
  8. "algo": "rsa",
  9. "size": 2048
  10. },
  11. "names": [
  12. {
  13. "C": "CN",
  14. "ST": "beijing",
  15. "L": "beijing",
  16. "O": "od",
  17. "OU": "ops"
  18. }
  19. ]
  20. }
  21. [root@hdss7-200 certs]# cfssl gencert -ca=ca.pem -ca-key=ca-key.pem -config=ca-config.json -profile=client client-csr.json |cfssl-json -bare client
  22. 2020/01/06 13:42:47 [INFO] generate received request
  23. 2020/01/06 13:42:47 [INFO] received CSR
  24. 2020/01/06 13:42:47 [INFO] generating key: rsa-2048
  25. 2020/01/06 13:42:47 [INFO] encoded CSR
  26. 2020/01/06 13:42:47 [INFO] signed certificate with serial number 268276380983442021656020268926931973684313260543
  27. 2020/01/06 13:42:47 [WARNING] This certificate lacks a "hosts" field. This makes it unsuitable for
  28. websites. For more information see the Baseline Requirements for the Issuance and Management
  29. of Publicly-Trusted Certificates, v.1.1.6, from the CA/Browser Forum (https://cabforum.org);
  30. specifically, section 10.2.3 ("Information Requirements").
  31. [root@hdss7-200 certs]# ls client* -l
  32. -rw-r--r-- 1 root root 993 Jan 6 13:42 client.csr
  33. -rw-r--r-- 1 root root 280 Jan 6 13:42 client-csr.json
  34. -rw------- 1 root root 1679 Jan 6 13:42 client-key.pem
  35. -rw-r--r-- 1 root root 1363 Jan 6 13:42 client.pem
  • 签发server证书(apiserver和其它k8s组件通信使用)
  1. # hosts中将所有可能作为apiserver的ip添加进去,VIP 10.4.7.10 也要加入
  2. [root@hdss7-200 certs]# vim /opt/certs/apiserver-csr.json
  3. {
  4. "CN": "k8s-apiserver",
  5. "hosts": [
  6. "127.0.0.1",
  7. "192.168.0.1",
  8. "kubernetes.default",
  9. "kubernetes.default.svc",
  10. "kubernetes.default.svc.cluster",
  11. "kubernetes.default.svc.cluster.local",
  12. "10.4.7.10",
  13. "10.4.7.21",
  14. "10.4.7.22",
  15. "10.4.7.23"
  16. ],
  17. "key": {
  18. "algo": "rsa",
  19. "size": 2048
  20. },
  21. "names": [
  22. {
  23. "C": "CN",
  24. "ST": "beijing",
  25. "L": "beijing",
  26. "O": "od",
  27. "OU": "ops"
  28. }
  29. ]
  30. }
  31. [root@hdss7-200 certs]# cfssl gencert -ca=ca.pem -ca-key=ca-key.pem -config=ca-config.json -profile=server apiserver-csr.json |cfssl-json -bare apiserver
  32. 2020/01/06 13:46:56 [INFO] generate received request
  33. 2020/01/06 13:46:56 [INFO] received CSR
  34. 2020/01/06 13:46:56 [INFO] generating key: rsa-2048
  35. 2020/01/06 13:46:56 [INFO] encoded CSR
  36. 2020/01/06 13:46:56 [INFO] signed certificate with serial number 573076691386375893093727554861295529219004473872
  37. 2020/01/06 13:46:56 [WARNING] This certificate lacks a "hosts" field. This makes it unsuitable for
  38. websites. For more information see the Baseline Requirements for the Issuance and Management
  39. of Publicly-Trusted Certificates, v.1.1.6, from the CA/Browser Forum (https://cabforum.org);
  40. specifically, section 10.2.3 ("Information Requirements").
  41. [root@hdss7-200 certs]# ls apiserver* -l
  42. -rw-r--r-- 1 root root 1249 Jan 6 13:46 apiserver.csr
  43. -rw-r--r-- 1 root root 566 Jan 6 13:45 apiserver-csr.json
  44. -rw------- 1 root root 1675 Jan 6 13:46 apiserver-key.pem
  45. -rw-r--r-- 1 root root 1598 Jan 6 13:46 apiserver.pem
  • 证书下发
  1. [root@hdss7-200 certs]# for i in 21 22;do echo hdss7-$i;ssh hdss7-$i "mkdir /opt/apps/kubernetes/server/bin/certs";scp apiserver-key.pem apiserver.pem ca-key.pem ca.pem client-key.pem client.pem hdss7-$i:/opt/apps/kubernetes/server/bin/certs/;done

3.2.3. 配置apiserver日志审计

aipserver 涉及的服务器:hdss7-21,hdss7-22

  1. [root@hdss7-21 bin]# mkdir /opt/apps/kubernetes/conf
  2. [root@hdss7-21 bin]# vim /opt/apps/kubernetes/conf/audit.yaml # 打开文件后,设置 :set paste,避免自动缩进
  3. apiVersion: audit.k8s.io/v1beta1 # This is required.
  4. kind: Policy
  5. # Don't generate audit events for all requests in RequestReceived stage.
  6. omitStages:
  7. - "RequestReceived"
  8. rules:
  9. # Log pod changes at RequestResponse level
  10. - level: RequestResponse
  11. resources:
  12. - group: ""
  13. # Resource "pods" doesn't match requests to any subresource of pods,
  14. # which is consistent with the RBAC policy.
  15. resources: ["pods"]
  16. # Log "pods/log", "pods/status" at Metadata level
  17. - level: Metadata
  18. resources:
  19. - group: ""
  20. resources: ["pods/log", "pods/status"]
  21. # Don't log requests to a configmap called "controller-leader"
  22. - level: None
  23. resources:
  24. - group: ""
  25. resources: ["configmaps"]
  26. resourceNames: ["controller-leader"]
  27. # Don't log watch requests by the "system:kube-proxy" on endpoints or services
  28. - level: None
  29. users: ["system:kube-proxy"]
  30. verbs: ["watch"]
  31. resources:
  32. - group: "" # core API group
  33. resources: ["endpoints", "services"]
  34. # Don't log authenticated requests to certain non-resource URL paths.
  35. - level: None
  36. userGroups: ["system:authenticated"]
  37. nonResourceURLs:
  38. - "/api*" # Wildcard matching.
  39. - "/version"
  40. # Log the request body of configmap changes in kube-system.
  41. - level: Request
  42. resources:
  43. - group: "" # core API group
  44. resources: ["configmaps"]
  45. # This rule only applies to resources in the "kube-system" namespace.
  46. # The empty string "" can be used to select non-namespaced resources.
  47. namespaces: ["kube-system"]
  48. # Log configmap and secret changes in all other namespaces at the Metadata level.
  49. - level: Metadata
  50. resources:
  51. - group: "" # core API group
  52. resources: ["secrets", "configmaps"]
  53. # Log all other resources in core and extensions at the Request level.
  54. - level: Request
  55. resources:
  56. - group: "" # core API group
  57. - group: "extensions" # Version of group should NOT be included.
  58. # A catch-all rule to log all other requests at the Metadata level.
  59. - level: Metadata
  60. # Long-running requests like watches that fall under this rule will not
  61. # generate an audit event in RequestReceived.
  62. omitStages:
  63. - "RequestReceived"

3.2.4. 配置启动脚本

aipserver 涉及的服务器:hdss7-21,hdss7-22

  • 创建启动脚本
  1. [root@hdss7-21 bin]# vim /opt/apps/kubernetes/server/bin/kube-apiserver-startup.sh
  2. #!/bin/bash
  3. WORK_DIR=$(dirname $(readlink -f $0))
  4. [ $? -eq 0 ] && cd $WORK_DIR || exit
  5. /opt/apps/kubernetes/server/bin/kube-apiserver \
  6. --apiserver-count 2 \
  7. --audit-log-path /data/logs/kubernetes/kube-apiserver/audit-log \
  8. --audit-policy-file ../../conf/audit.yaml \
  9. --authorization-mode RBAC \
  10. --client-ca-file ./certs/ca.pem \
  11. --requestheader-client-ca-file ./certs/ca.pem \
  12. --enable-admission-plugins NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota \
  13. --etcd-cafile ./certs/ca.pem \
  14. --etcd-certfile ./certs/client.pem \
  15. --etcd-keyfile ./certs/client-key.pem \
  16. --etcd-servers https://10.4.7.12:2379,https://10.4.7.21:2379,https://10.4.7.22:2379 \
  17. --service-account-key-file ./certs/ca-key.pem \
  18. --service-cluster-ip-range 192.168.0.0/16 \
  19. --service-node-port-range 3000-29999 \
  20. --target-ram-mb=1024 \
  21. --kubelet-client-certificate ./certs/client.pem \
  22. --kubelet-client-key ./certs/client-key.pem \
  23. --log-dir /data/logs/kubernetes/kube-apiserver \
  24. --tls-cert-file ./certs/apiserver.pem \
  25. --tls-private-key-file ./certs/apiserver-key.pem \
  26. --v 2
  • 配置supervisor启动配置
  1. [root@hdss7-21 bin]# vim /etc/supervisord.d/kube-apiserver.ini
  2. [program:kube-apiserver-7-21]
  3. command=/opt/apps/kubernetes/server/bin/kube-apiserver-startup.sh
  4. numprocs=1
  5. directory=/opt/apps/kubernetes/server/bin
  6. autostart=true
  7. autorestart=true
  8. startsecs=30
  9. startretries=3
  10. exitcodes=0,2
  11. stopsignal=QUIT
  12. stopwaitsecs=10
  13. user=root
  14. redirect_stderr=true
  15. stdout_logfile=/data/logs/kubernetes/kube-apiserver/apiserver.stdout.log
  16. stdout_logfile_maxbytes=64MB
  17. stdout_logfile_backups=5
  18. stdout_capture_maxbytes=1MB
  19. stdout_events_enabled=false
  20. [root@hdss7-21 bin]# supervisorctl update
  21. [root@hdss7-21 bin]# supervisorctl status
  22. etcd-server-7-21 RUNNING pid 23637, uptime 22:26:08
  23. kube-apiserver-7-21 RUNNING pid 32591, uptime 0:05:37
  • 启停apiserver
  1. [root@hdss7-12 ~]# supervisorctl start kube-apiserver-7-21
  2. [root@hdss7-12 ~]# supervisorctl stop kube-apiserver-7-21
  3. [root@hdss7-12 ~]# supervisorctl restart kube-apiserver-7-21
  4. [root@hdss7-12 ~]# supervisorctl status kube-apiserver-7-21
  • 查看进程
  1. [root@hdss7-21 bin]# netstat -lntp|grep api
  2. tcp 0 0 127.0.0.1:8080 0.0.0.0:* LISTEN 32595/kube-apiserve
  3. tcp6 0 0 :::6443 :::* LISTEN 32595/kube-apiserve
  4. [root@hdss7-21 bin]# ps uax|grep kube-apiserver|grep -v grep
  5. root 32591 0.0 0.0 115296 1476 ? S 20:17 0:00 /bin/bash /opt/apps/kubernetes/server/bin/kube-apiserver-startup.sh
  6. root 32595 3.0 2.3 402720 184892 ? Sl 20:17 0:16 /opt/apps/kubernetes/server/bin/kube-apiserver --apiserver-count 2 --audit-log-path /data/logs/kubernetes/kube-apiserver/audit-log --audit-policy-file ../../conf/audit.yaml --authorization-mode RBAC --client-ca-file ./certs/ca.pem --requestheader-client-ca-file ./certs/ca.pem --enable-admission-plugins NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota --etcd-cafile ./certs/ca.pem --etcd-certfile ./certs/client.pem --etcd-keyfile ./certs/client-key.pem --etcd-servers https://10.4.7.12:2379,https://10.4.7.21:2379,https://10.4.7.22:2379 --service-account-key-file ./certs/ca-key.pem --service-cluster-ip-range 192.168.0.0/16 --service-node-port-range 3000-29999 --target-ram-mb=1024 --kubelet-client-certificate ./certs/client.pem --kubelet-client-key ./certs/client-key.pem --log-dir /data/logs/kubernetes/kube-apiserver --tls-cert-file ./certs/apiserver.pem --tls-private-key-file ./certs/apiserver-key.pem --v 2

3.3. 配置apiserver L4代理

3.3.1. nginx配置

L4 代理涉及的服务器:hdss7-11,hdss7-12

  1. [root@hdss7-11 ~]# yum install -y nginx
  2. [root@hdss7-11 ~]# vim /etc/nginx/nginx.conf
  3. # 末尾加上以下内容,stream 只能加在 main 中
  4. # 此处只是简单配置下nginx,实际生产中,建议进行更合理的配置
  5. stream {
  6. log_format proxy '$time_local|$remote_addr|$upstream_addr|$protocol|$status|'
  7. '$session_time|$upstream_connect_time|$bytes_sent|$bytes_received|'
  8. '$upstream_bytes_sent|$upstream_bytes_received' ;
  9. upstream kube-apiserver {
  10. server 10.4.7.21:6443 max_fails=3 fail_timeout=30s;
  11. server 10.4.7.22:6443 max_fails=3 fail_timeout=30s;
  12. }
  13. server {
  14. listen 7443;
  15. proxy_connect_timeout 2s;
  16. proxy_timeout 900s;
  17. proxy_pass kube-apiserver;
  18. access_log /var/log/nginx/proxy.log proxy;
  19. }
  20. }
  21. [root@hdss7-11 ~]# systemctl start nginx; systemctl enable nginx
  22. [root@hdss7-11 ~]# curl 127.0.0.1:7443 # 测试几次
  23. Client sent an HTTP request to an HTTPS server.
  24. [root@hdss7-11 ~]# cat /var/log/nginx/proxy.log
  25. 06/Jan/2020:21:00:27 +0800|127.0.0.1|10.4.7.21:6443|TCP|200|0.001|0.000|76|78|78|76
  26. 06/Jan/2020:21:05:03 +0800|127.0.0.1|10.4.7.22:6443|TCP|200|0.020|0.019|76|78|78|76
  27. 06/Jan/2020:21:05:04 +0800|127.0.0.1|10.4.7.21:6443|TCP|200|0.001|0.001|76|78|78|76

3.3.2. keepalived配置

aipserver L4 代理涉及的服务器:hdss7-11,hdss7-12

  • 安装keepalive
  1. [root@hdss7-11 ~]# yum install -y keepalived
  2. [root@hdss7-11 ~]# vim /etc/keepalived/check_port.sh # 配置检查脚本
  3. #!/bin/bash
  4. if [ $# -eq 1 ] && [[ $1 =~ ^[0-9]+ ]];then
  5. [ $(netstat -lntp|grep ":$1 " |wc -l) -eq 0 ] && echo "[ERROR] nginx may be not running!" && exit 1 || exit 0
  6. else
  7. echo "[ERROR] need one port!"
  8. exit 1
  9. fi
  10. [root@hdss7-11 ~]# chmod +x /etc/keepalived/check_port.sh
  • 配置主节点:/etc/keepalived/keepalived.conf

主节点中,必须加上 nopreempt
因为一旦因为网络抖动导致VIP漂移,不能让它自动飘回来,必须要分析原因后手动迁移VIP到主节点!如主节点确认正常后,重启备节点的keepalive,让VIP飘到主节点.
keepalived 的日志输出配置此处省略,生产中需要进行处理。

  1. ! Configuration File for keepalived
  2. global_defs {
  3. router_id 10.4.7.11
  4. }
  5. vrrp_script chk_nginx {
  6. script "/etc/keepalived/check_port.sh 7443"
  7. interval 2
  8. weight -20
  9. }
  10. vrrp_instance VI_1 {
  11. state MASTER
  12. interface ens32
  13. virtual_router_id 251
  14. priority 100
  15. advert_int 1
  16. mcast_src_ip 10.4.7.11
  17. nopreempt
  18. authentication {
  19. auth_type PASS
  20. auth_pass 11111111
  21. }
  22. track_script {
  23. chk_nginx
  24. }
  25. virtual_ipaddress {
  26. 10.4.7.10
  27. }
  28. }
  • 配置备节点:/etc/keepalived/keepalived.conf
  1. ! Configuration File for keepalived
  2. global_defs {
  3. router_id 10.4.7.12
  4. }
  5. vrrp_script chk_nginx {
  6. script "/etc/keepalived/check_port.sh 7443"
  7. interval 2
  8. weight -20
  9. }
  10. vrrp_instance VI_1 {
  11. state BACKUP
  12. interface ens32
  13. virtual_router_id 251
  14. mcast_src_ip 10.4.7.12
  15. priority 90
  16. advert_int 1
  17. authentication {
  18. auth_type PASS
  19. auth_pass 11111111
  20. }
  21. track_script {
  22. chk_nginx
  23. }
  24. virtual_ipaddress {
  25. 10.4.7.10
  26. }
  27. }
  • 启动keepalived
  1. [root@hdss7-11 ~]# systemctl start keepalived ; systemctl enable keepalived
  2. [root@hdss7-11 ~]# ip addr show ens32
  3. 2: ens32: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
  4. link/ether 00:0c:29:6d:b8:82 brd ff:ff:ff:ff:ff:ff
  5. inet 10.4.7.11/24 brd 10.4.7.255 scope global noprefixroute ens32
  6. valid_lft forever preferred_lft forever
  7. inet 10.4.7.10/32 scope global ens32
  8. valid_lft forever preferred_lft forever
  9. ......

3.4. controller-manager 安装

controller-manager 涉及的服务器:hdss7-21,hdss7-22
controller-manager 设置为只调用当前机器的 apiserver,走127.0.0.1网卡,因此不配制SSL证书

  1. [root@hdss7-21 ~]# vim /opt/apps/kubernetes/server/bin/kube-controller-manager-startup.sh
  2. #!/bin/sh
  3. WORK_DIR=$(dirname $(readlink -f $0))
  4. [ $? -eq 0 ] && cd $WORK_DIR || exit
  5. /opt/apps/kubernetes/server/bin/kube-controller-manager \
  6. --cluster-cidr 172.7.0.0/16 \
  7. --leader-elect true \
  8. --log-dir /data/logs/kubernetes/kube-controller-manager \
  9. --master http://127.0.0.1:8080 \
  10. --service-account-private-key-file ./certs/ca-key.pem \
  11. --service-cluster-ip-range 192.168.0.0/16 \
  12. --root-ca-file ./certs/ca.pem \
  13. --v 2
  14. [root@hdss7-21 ~]# chmod u+x /opt/apps/kubernetes/server/bin/kube-controller-manager-startup.sh
  1. [root@hdss7-21 ~]# vim /etc/supervisord.d/kube-controller-manager.ini
  2. [program:kube-controller-manager-7-21]
  3. command=/opt/apps/kubernetes/server/bin/kube-controller-manager-startup.sh ; the program (relative uses PATH, can take args)
  4. numprocs=1 ; number of processes copies to start (def 1)
  5. directory=/opt/apps/kubernetes/server/bin ; directory to cwd to before exec (def no cwd)
  6. autostart=true ; start at supervisord start (default: true)
  7. autorestart=true ; retstart at unexpected quit (default: true)
  8. startsecs=30 ; number of secs prog must stay running (def. 1)
  9. startretries=3 ; max # of serial start failures (default 3)
  10. exitcodes=0,2 ; 'expected' exit codes for process (default 0,2)
  11. stopsignal=QUIT ; signal used to kill process (default TERM)
  12. stopwaitsecs=10 ; max num secs to wait b4 SIGKILL (default 10)
  13. user=root ; setuid to this UNIX account to run the program
  14. redirect_stderr=true ; redirect proc stderr to stdout (default false)
  15. stdout_logfile=/data/logs/kubernetes/kube-controller-manager/controller.stdout.log ; stderr log path, NONE for none; default AUTO
  16. stdout_logfile_maxbytes=64MB ; max # logfile bytes b4 rotation (default 50MB)
  17. stdout_logfile_backups=4 ; # of stdout logfile backups (default 10)
  18. stdout_capture_maxbytes=1MB ; number of bytes in 'capturemode' (default 0)
  19. stdout_events_enabled=false ; emit events on stdout writes (default false)
  1. [root@hdss7-21 ~]# supervisorctl update
  2. kube-controller-manager-7-21: stopped
  3. kube-controller-manager-7-21: updated process group
  4. [root@hdss7-21 ~]# supervisorctl status
  5. etcd-server-7-21 RUNNING pid 23637, uptime 1 day, 0:16:54
  6. kube-apiserver-7-21 RUNNING pid 32591, uptime 1:56:23
  7. kube-controller-manager-7-21 RUNNING pid 33357, uptime 0:00:38

3.5. kube-scheduler安装

kube-scheduler 涉及的服务器:hdss7-21,hdss7-22
kube-scheduler 设置为只调用当前机器的 apiserver,走127.0.0.1网卡,因此不配制SSL证书

  1. [root@hdss7-21 ~]# vim /opt/apps/kubernetes/server/bin/kube-scheduler-startup.sh
  2. #!/bin/sh
  3. WORK_DIR=$(dirname $(readlink -f $0))
  4. [ $? -eq 0 ] && cd $WORK_DIR || exit
  5. /opt/apps/kubernetes/server/bin/kube-scheduler \
  6. --leader-elect \
  7. --log-dir /data/logs/kubernetes/kube-scheduler \
  8. --master http://127.0.0.1:8080 \
  9. --v 2
  10. [root@hdss7-21 ~]# chmod u+x /opt/apps/kubernetes/server/bin/kube-scheduler-startup.sh
  11. [root@hdss7-21 ~]# mkdir -p /data/logs/kubernetes/kube-scheduler
  1. [root@hdss7-21 ~]# vim /etc/supervisord.d/kube-scheduler.ini
  2. [program:kube-scheduler-7-21]
  3. command=/opt/apps/kubernetes/server/bin/kube-scheduler-startup.sh
  4. numprocs=1
  5. directory=/opt/apps/kubernetes/server/bin
  6. autostart=true
  7. autorestart=true
  8. startsecs=30
  9. startretries=3
  10. exitcodes=0,2
  11. stopsignal=QUIT
  12. stopwaitsecs=10
  13. user=root
  14. redirect_stderr=true
  15. stdout_logfile=/data/logs/kubernetes/kube-scheduler/scheduler.stdout.log
  16. stdout_logfile_maxbytes=64MB
  17. stdout_logfile_backups=4
  18. stdout_capture_maxbytes=1MB
  19. stdout_events_enabled=false
  1. [root@hdss7-21 ~]# supervisorctl update
  2. kube-scheduler-7-21: stopped
  3. kube-scheduler-7-21: updated process group
  4. [root@hdss7-21 ~]# supervisorctl status
  5. etcd-server-7-21 RUNNING pid 23637, uptime 1 day, 0:26:53
  6. kube-apiserver-7-21 RUNNING pid 32591, uptime 2:06:22
  7. kube-controller-manager-7-21 RUNNING pid 33357, uptime 0:10:37
  8. kube-scheduler-7-21 RUNNING pid 33450, uptime 0:01:18

3.6. 检查主控节点状态

  1. [root@hdss7-21 ~]# ln -s /opt/apps/kubernetes/server/bin/kubectl /usr/local/bin/
  2. [root@hdss7-21 ~]# kubectl get cs
  3. NAME STATUS MESSAGE ERROR
  4. scheduler Healthy ok
  5. controller-manager Healthy ok
  6. etcd-1 Healthy {"health": "true"}
  7. etcd-0 Healthy {"health": "true"}
  8. etcd-2 Healthy {"health": "true"}
  1. [root@hdss7-22 ~]# ln -s /opt/apps/kubernetes/server/bin/kubectl /usr/local/bin/
  2. [root@hdss7-22 ~]# kubectl get cs
  3. NAME STATUS MESSAGE ERROR
  4. controller-manager Healthy ok
  5. scheduler Healthy ok
  6. etcd-2 Healthy {"health": "true"}
  7. etcd-1 Healthy {"health": "true"}
  8. etcd-0 Healthy {"health": "true"}

4. 运算节点部署

4.1. kubelet 部署

4.1.1. 签发证书

证书签发在 hdss7-200 操作

  1. [root@hdss7-200 ~]# cd /opt/certs/
  2. [root@hdss7-200 certs]# vim kubelet-csr.json # 将所有可能的kubelet机器IP添加到hosts中
  3. {
  4. "CN": "k8s-kubelet",
  5. "hosts": [
  6. "127.0.0.1",
  7. "10.4.7.10",
  8. "10.4.7.21",
  9. "10.4.7.22",
  10. "10.4.7.23",
  11. "10.4.7.24",
  12. "10.4.7.25",
  13. "10.4.7.26",
  14. "10.4.7.27",
  15. "10.4.7.28"
  16. ],
  17. "key": {
  18. "algo": "rsa",
  19. "size": 2048
  20. },
  21. "names": [
  22. {
  23. "C": "CN",
  24. "ST": "beijing",
  25. "L": "beijing",
  26. "O": "od",
  27. "OU": "ops"
  28. }
  29. ]
  30. }
  31. [root@hdss7-200 certs]# cfssl gencert -ca=ca.pem -ca-key=ca-key.pem -config=ca-config.json -profile=server kubelet-csr.json | cfssl-json -bare kubelet
  32. 2020/01/06 23:10:56 [INFO] generate received request
  33. 2020/01/06 23:10:56 [INFO] received CSR
  34. 2020/01/06 23:10:56 [INFO] generating key: rsa-2048
  35. 2020/01/06 23:10:56 [INFO] encoded CSR
  36. 2020/01/06 23:10:56 [INFO] signed certificate with serial number 61221942784856969738771370531559555767101820379
  37. 2020/01/06 23:10:56 [WARNING] This certificate lacks a "hosts" field. This makes it unsuitable for
  38. websites. For more information see the Baseline Requirements for the Issuance and Management
  39. of Publicly-Trusted Certificates, v.1.1.6, from the CA/Browser Forum (https://cabforum.org);
  40. specifically, section 10.2.3 ("Information Requirements").
  41. [root@hdss7-200 certs]# ls kubelet* -l
  42. -rw-r--r-- 1 root root 1115 Jan 6 23:10 kubelet.csr
  43. -rw-r--r-- 1 root root 452 Jan 6 23:10 kubelet-csr.json
  44. -rw------- 1 root root 1675 Jan 6 23:10 kubelet-key.pem
  45. -rw-r--r-- 1 root root 1468 Jan 6 23:10 kubelet.pem
  46. [root@hdss7-200 certs]# scp kubelet.pem kubelet-key.pem hdss7-21:/opt/apps/kubernetes/server/bin/certs/
  47. [root@hdss7-200 certs]# scp kubelet.pem kubelet-key.pem hdss7-22:/opt/apps/kubernetes/server/bin/certs/

4.1.2. 创建kubelet配置

kubelet配置在 hdss7-21 hdss7-22 操作

  • set-cluster # 创建需要连接的集群信息,可以创建多个k8s集群信息
  1. [root@hdss7-21 ~]# kubectl config set-cluster myk8s \
  2. --certificate-authority=/opt/apps/kubernetes/server/bin/certs/ca.pem \
  3. --embed-certs=true \
  4. --server=https://10.4.7.10:7443 \
  5. --kubeconfig=/opt/apps/kubernetes/conf/kubelet.kubeconfig
  • set-credentials # 创建用户账号,即用户登陆使用的客户端私有和证书,可以创建多个证书
  1. [root@hdss7-21 ~]# kubectl config set-credentials k8s-node \
  2. --client-certificate=/opt/apps/kubernetes/server/bin/certs/client.pem \
  3. --client-key=/opt/apps/kubernetes/server/bin/certs/client-key.pem \
  4. --embed-certs=true \
  5. --kubeconfig=/opt/apps/kubernetes/conf/kubelet.kubeconfig
  • set-context # 设置context,即确定账号和集群对应关系
  1. [root@hdss7-21 ~]# kubectl config set-context myk8s-context \
  2. --cluster=myk8s \
  3. --user=k8s-node \
  4. --kubeconfig=/opt/apps/kubernetes/conf/kubelet.kubeconfig
  • use-context # 设置当前使用哪个context
  1. [root@hdss7-21 ~]# kubectl config use-context myk8s-context --kubeconfig=/opt/apps/kubernetes/conf/kubelet.kubeconfig

4.1.3. 授权k8s-node用户

此步骤只需要在一台master节点执行
授权 k8s-node 用户绑定集群角色 system:node ,让 k8s-node 成为具备运算节点的权限。

  1. [root@hdss7-21 ~]# vim k8s-node.yaml
  2. apiVersion: rbac.authorization.k8s.io/v1
  3. kind: ClusterRoleBinding
  4. metadata:
  5. name: k8s-node
  6. roleRef:
  7. apiGroup: rbac.authorization.k8s.io
  8. kind: ClusterRole
  9. name: system:node
  10. subjects:
  11. - apiGroup: rbac.authorization.k8s.io
  12. kind: User
  13. name: k8s-node
  14. [root@hdss7-21 ~]# kubectl create -f k8s-node.yaml
  15. clusterrolebinding.rbac.authorization.k8s.io/k8s-node created
  16. [root@hdss7-21 ~]# kubectl get clusterrolebinding k8s-node
  17. NAME AGE
  18. k8s-node 36s

4.1.4. 装备pause镜像

将pause镜像放入到harbor私有仓库中,仅在 hdss7-200 操作:

  1. [root@hdss7-200 ~]# docker image pull kubernetes/pause
  2. [root@hdss7-200 ~]# docker image tag kubernetes/pause:latest harbor.od.com/public/pause:latest
  3. [root@hdss7-200 ~]# docker login -u admin harbor.od.com
  4. [root@hdss7-200 ~]# docker image push harbor.od.com/public/pause:latest

4.1.5. 创建启动脚本

在node节点创建脚本并启动kubelet,涉及服务器: hdss7-21 hdss7-22

  1. [root@hdss7-21 ~]# vim /opt/apps/kubernetes/server/bin/kubelet-startup.sh
  2. #!/bin/sh
  3. WORK_DIR=$(dirname $(readlink -f $0))
  4. [ $? -eq 0 ] && cd $WORK_DIR || exit
  5. /opt/apps/kubernetes/server/bin/kubelet \
  6. --anonymous-auth=false \
  7. --cgroup-driver systemd \
  8. --cluster-dns 192.168.0.2 \
  9. --cluster-domain cluster.local \
  10. --runtime-cgroups=/systemd/system.slice \
  11. --kubelet-cgroups=/systemd/system.slice \
  12. --fail-swap-on="false" \
  13. --client-ca-file ./certs/ca.pem \
  14. --tls-cert-file ./certs/kubelet.pem \
  15. --tls-private-key-file ./certs/kubelet-key.pem \
  16. --hostname-override hdss7-21.host.com \
  17. --image-gc-high-threshold 20 \
  18. --image-gc-low-threshold 10 \
  19. --kubeconfig ../../conf/kubelet.kubeconfig \
  20. --log-dir /data/logs/kubernetes/kube-kubelet \
  21. --pod-infra-container-image harbor.od.com/public/pause:latest \
  22. --root-dir /data/kubelet
  23. [root@hdss7-21 ~]# chmod u+x /opt/apps/kubernetes/server/bin/kubelet-startup.sh
  24. [root@hdss7-21 ~]# mkdir -p /data/logs/kubernetes/kube-kubelet /data/kubelet
  25. [root@hdss7-21 ~]# vim /etc/supervisord.d/kube-kubelet.ini
  26. [program:kube-kubelet-7-21]
  27. command=/opt/apps/kubernetes/server/bin/kubelet-startup.sh
  28. numprocs=1
  29. directory=/opt/apps/kubernetes/server/bin
  30. autostart=true
  31. autorestart=true
  32. startsecs=30
  33. startretries=3
  34. exitcodes=0,2
  35. stopsignal=QUIT
  36. stopwaitsecs=10
  37. user=root
  38. redirect_stderr=true
  39. stdout_logfile=/data/logs/kubernetes/kube-kubelet/kubelet.stdout.log
  40. stdout_logfile_maxbytes=64MB
  41. stdout_logfile_backups=5
  42. stdout_capture_maxbytes=1MB
  43. stdout_events_enabled=false
  1. [root@hdss7-21 ~]# supervisorctl update
  2. [root@hdss7-21 ~]# supervisorctl status
  3. etcd-server-7-21 RUNNING pid 23637, uptime 1 day, 14:56:25
  4. kube-apiserver-7-21 RUNNING pid 32591, uptime 16:35:54
  5. kube-controller-manager-7-21 RUNNING pid 33357, uptime 14:40:09
  6. kube-kubelet-7-21 RUNNING pid 37232, uptime 0:01:08
  7. kube-scheduler-7-21 RUNNING pid 33450, uptime 14:30:50
  8. [root@hdss7-21 ~]# kubectl get node
  9. NAME STATUS ROLES AGE VERSION
  10. hdss7-21.host.com Ready <none> 3m13s v1.15.2
  11. hdss7-22.host.com Ready <none> 3m13s v1.15.2

4.1.6. 修改节点角色

使用 kubectl get nodes 获取的Node节点角色为空,可以按照以下方式修改

  1. [root@hdss7-21 ~]# kubectl get node
  2. NAME STATUS ROLES AGE VERSION
  3. hdss7-21.host.com Ready <none> 3m13s v1.15.2
  4. hdss7-22.host.com Ready <none> 3m13s v1.15.2
  5. [root@hdss7-21 ~]# kubectl label node hdss7-21.host.com node-role.kubernetes.io/node=
  6. node/hdss7-21.host.com labeled
  7. [root@hdss7-21 ~]# kubectl label node hdss7-21.host.com node-role.kubernetes.io/master=
  8. node/hdss7-21.host.com labeled
  9. [root@hdss7-21 ~]# kubectl label node hdss7-22.host.com node-role.kubernetes.io/master=
  10. node/hdss7-22.host.com labeled
  11. [root@hdss7-21 ~]# kubectl label node hdss7-22.host.com node-role.kubernetes.io/node=
  12. node/hdss7-22.host.com labeled
  13. [root@hdss7-21 ~]# kubectl get node
  14. NAME STATUS ROLES AGE VERSION
  15. hdss7-21.host.com Ready master,node 7m44s v1.15.2
  16. hdss7-22.host.com Ready master,node 7m44s v1.15.2

4.2. kube-proxy部署

4.2.1. 签发证书

证书签发在 hdss7-200 操作

  1. [root@hdss7-200 ~]# cd /opt/certs/
  2. [root@hdss7-200 certs]# vim kube-proxy-csr.json # CN 其实是k8s中的角色
  3. {
  4. "CN": "system:kube-proxy",
  5. "key": {
  6. "algo": "rsa",
  7. "size": 2048
  8. },
  9. "names": [
  10. {
  11. "C": "CN",
  12. "ST": "beijing",
  13. "L": "beijing",
  14. "O": "od",
  15. "OU": "ops"
  16. }
  17. ]
  18. }
  19. [root@hdss7-200 certs]# cfssl gencert -ca=ca.pem -ca-key=ca-key.pem -config=ca-config.json -profile=client kube-proxy-csr.json |cfssl-json -bare kube-proxy-client
  20. 2020/01/07 21:45:53 [INFO] generate received request
  21. 2020/01/07 21:45:53 [INFO] received CSR
  22. 2020/01/07 21:45:53 [INFO] generating key: rsa-2048
  23. 2020/01/07 21:45:53 [INFO] encoded CSR
  24. 2020/01/07 21:45:53 [INFO] signed certificate with serial number 620191685968917036075463174423999296907693104226
  25. 2020/01/07 21:45:53 [WARNING] This certificate lacks a "hosts" field. This makes it unsuitable for
  26. websites. For more information see the Baseline Requirements for the Issuance and Management
  27. of Publicly-Trusted Certificates, v.1.1.6, from the CA/Browser Forum (https://cabforum.org);
  28. [root@hdss7-200 certs]# ls kube-proxy-c* -l # 因为kube-proxy使用的用户是kube-proxy,不能使用client证书,必须要重新签发自己的证书
  29. -rw-r--r-- 1 root root 1005 Jan 7 21:45 kube-proxy-client.csr
  30. -rw------- 1 root root 1675 Jan 7 21:45 kube-proxy-client-key.pem
  31. -rw-r--r-- 1 root root 1375 Jan 7 21:45 kube-proxy-client.pem
  32. -rw-r--r-- 1 root root 267 Jan 7 21:45 kube-proxy-csr.json
  33. [root@hdss7-200 certs]# scp kube-proxy-client-key.pem kube-proxy-client.pem hdss7-21:/opt/apps/kubernetes/server/bin/certs/ 100% 1375 870.6KB/s 00:00
  34. [root@hdss7-200 certs]# scp kube-proxy-client-key.pem kube-proxy-client.pem hdss7-22:/opt/apps/kubernetes/server/bin/certs/

4.2.2. 创建kube-proxy配置

在所有node节点创建,涉及服务器:hdss7-21 ,hdss7-22

  1. [root@hdss7-21 ~]# kubectl config set-cluster myk8s \
  2. --certificate-authority=/opt/apps/kubernetes/server/bin/certs/ca.pem \
  3. --embed-certs=true \
  4. --server=https://10.4.7.10:7443 \
  5. --kubeconfig=/opt/apps/kubernetes/conf/kube-proxy.kubeconfig
  6. [root@hdss7-21 ~]# kubectl config set-credentials kube-proxy \
  7. --client-certificate=/opt/apps/kubernetes/server/bin/certs/kube-proxy-client.pem \
  8. --client-key=/opt/apps/kubernetes/server/bin/certs/kube-proxy-client-key.pem \
  9. --embed-certs=true \
  10. --kubeconfig=/opt/apps/kubernetes/conf/kube-proxy.kubeconfig
  11. [root@hdss7-21 ~]# kubectl config set-context myk8s-context \
  12. --cluster=myk8s \
  13. --user=kube-proxy \
  14. --kubeconfig=/opt/apps/kubernetes/conf/kube-proxy.kubeconfig
  15. [root@hdss7-21 ~]# kubectl config use-context myk8s-context --kubeconfig=/opt/apps/kubernetes/conf/kube-proxy.kubeconfig

4.2.3. 加载ipvs模块

kube-proxy 共有3种流量调度模式,分别是 namespace,iptables,ipvs,其中ipvs性能最好。

  1. [root@hdss7-21 ~]# for i in $(ls /usr/lib/modules/$(uname -r)/kernel/net/netfilter/ipvs|grep -o "^[^.]*");do echo $i; /sbin/modinfo -F filename $i >/dev/null 2>&1 && /sbin/modprobe $i;done
  2. [root@hdss7-21 ~]# lsmod | grep ip_vs # 查看ipvs模块

4.2.4. 创建启动脚本

  1. [root@hdss7-21 ~]# vim /opt/apps/kubernetes/server/bin/kube-proxy-startup.sh
  2. #!/bin/sh
  3. WORK_DIR=$(dirname $(readlink -f $0))
  4. [ $? -eq 0 ] && cd $WORK_DIR || exit
  5. /opt/apps/kubernetes/server/bin/kube-proxy \
  6. --cluster-cidr 172.7.0.0/16 \
  7. --hostname-override hdss7-21.host.com \
  8. --proxy-mode=ipvs \
  9. --ipvs-scheduler=nq \
  10. --kubeconfig ../../conf/kube-proxy.kubeconfig
  11. [root@hdss7-21 ~]# chmod u+x /opt/apps/kubernetes/server/bin/kube-proxy-startup.sh
  12. [root@hdss7-21 ~]# mkdir -p /data/logs/kubernetes/kube-proxy
  13. [root@hdss7-21 ~]# vim /etc/supervisord.d/kube-proxy.ini
  14. [program:kube-proxy-7-21]
  15. command=/opt/apps/kubernetes/server/bin/kube-proxy-startup.sh
  16. numprocs=1
  17. directory=/opt/apps/kubernetes/server/bin
  18. autostart=true
  19. autorestart=true
  20. startsecs=30
  21. startretries=3
  22. exitcodes=0,2
  23. stopsignal=QUIT
  24. stopwaitsecs=10
  25. user=root
  26. redirect_stderr=true
  27. stdout_logfile=/data/logs/kubernetes/kube-proxy/proxy.stdout.log
  28. stdout_logfile_maxbytes=64MB
  29. stdout_logfile_backups=5
  30. stdout_capture_maxbytes=1MB
  31. stdout_events_enabled=false
  32. [root@hdss7-21 ~]# supervisorctl update

4.2.5. 验证集群

  1. [root@hdss7-21 ~]# supervisorctl status
  2. etcd-server-7-21 RUNNING pid 23637, uptime 2 days, 0:27:18
  3. kube-apiserver-7-21 RUNNING pid 32591, uptime 1 day, 2:06:47
  4. kube-controller-manager-7-21 RUNNING pid 33357, uptime 1 day, 0:11:02
  5. kube-kubelet-7-21 RUNNING pid 37232, uptime 9:32:01
  6. kube-proxy-7-21 RUNNING pid 47088, uptime 0:06:19
  7. kube-scheduler-7-21 RUNNING pid 33450, uptime 1 day, 0:01:43
  8. [root@hdss7-21 ~]# yum install -y ipvsadm
  9. [root@hdss7-21 ~]# ipvsadm -Ln
  10. IP Virtual Server version 1.2.1 (size=4096)
  11. Prot LocalAddress:Port Scheduler Flags
  12. -> RemoteAddress:Port Forward Weight ActiveConn InActConn
  13. TCP 192.168.0.1:443 nq
  14. -> 10.4.7.21:6443 Masq 1 0 0
  15. -> 10.4.7.22:6443 Masq 1 0 0
  1. [root@hdss7-21 ~]# curl -I 172.7.21.2
  2. HTTP/1.1 200 OK
  3. Server: nginx/1.17.6
  4. Date: Tue, 07 Jan 2020 14:28:46 GMT
  5. Content-Type: text/html
  6. Content-Length: 612
  7. Last-Modified: Tue, 19 Nov 2019 12:50:08 GMT
  8. Connection: keep-alive
  9. ETag: "5dd3e500-264"
  10. Accept-Ranges: bytes
  11. [root@hdss7-21 ~]# curl -I 172.7.22.2 # 缺少网络插件,无法跨节点通信

5. 核心插件部署

5.1. CNI网络插件

kubernetes设计了网络模型,但是pod之间通信的具体实现交给了CNI往插件。常用的CNI网络插件有:Flannel 、Calico、Canal、Contiv等,其中Flannel和Calico占比接近80%,Flannel占比略多于Calico。本次部署使用Flannel作为网络插件。涉及的机器 hdss7-21,hdss7-22

5.1.1. 安装Flannel

github地址:https://github.com/coreos/flannel/releases
涉及的机器 hdss7-21,hdss7-22

  1. [root@hdss7-21 ~]# cd /opt/src/
  2. [root@hdss7-21 src]# wget https://github.com/coreos/flannel/releases/download/v0.11.0/flannel-v0.11.0-linux-amd64.tar.gz
  3. [root@hdss7-21 src]# mkdir /opt/release/flannel-v0.11.0 # 因为flannel压缩包内部没有套目录
  4. [root@hdss7-21 src]# tar -xf flannel-v0.11.0-linux-amd64.tar.gz -C /opt/release/flannel-v0.11.0
  5. [root@hdss7-21 src]# ln -s /opt/release/flannel-v0.11.0 /opt/apps/flannel
  6. [root@hdss7-21 src]# ll /opt/apps/flannel
  7. lrwxrwxrwx 1 root root 28 Jan 9 22:33 /opt/apps/flannel -> /opt/release/flannel-v0.11.0

5.1.2. 拷贝证书

  1. # flannel 需要以客户端的身份访问etcd,需要相关证书
  2. [root@hdss7-21 src]# mkdir /opt/apps/flannel/certs
  3. [root@hdss7-200 ~]# cd /opt/certs/
  4. [root@hdss7-200 certs]# scp ca.pem client-key.pem client.pem hdss7-21:/opt/apps/flannel/certs/

5.1.3. 创建启动脚本

涉及的机器 hdss7-21,hdss7-22

  1. [root@hdss7-21 src]# vim /opt/apps/flannel/subnet.env # 创建子网信息,7-22的subnet需要修改
  2. FLANNEL_NETWORK=172.7.0.0/16
  3. FLANNEL_SUBNET=172.7.21.1/24
  4. FLANNEL_MTU=1500
  5. FLANNEL_IPMASQ=false
  6. [root@hdss7-21 src]# /opt/apps/etcd/etcdctl set /coreos.com/network/config '{"Network": "172.7.0.0/16", "Backend": {"Type": "host-gw"}}'
  7. [root@hdss7-21 src]# /opt/apps/etcd/etcdctl get /coreos.com/network/config # 只需要在一台etcd机器上设置就可以了
  8. {"Network": "172.7.0.0/16", "Backend": {"Type": "host-gw"}}
  1. # public-ip 为本机IP,iface 为当前宿主机对外网卡
  2. [root@hdss7-21 src]# vim /opt/apps/flannel/flannel-startup.sh
  3. #!/bin/sh
  4. WORK_DIR=$(dirname $(readlink -f $0))
  5. [ $? -eq 0 ] && cd $WORK_DIR || exit
  6. /opt/apps/flannel/flanneld \
  7. --public-ip=10.4.7.21 \
  8. --etcd-endpoints=https://10.4.7.12:2379,https://10.4.7.21:2379,https://10.4.7.22:2379 \
  9. --etcd-keyfile=./certs/client-key.pem \
  10. --etcd-certfile=./certs/client.pem \
  11. --etcd-cafile=./certs/ca.pem \
  12. --iface=ens32 \
  13. --subnet-file=./subnet.env \
  14. --healthz-port=2401
  15. [root@hdss7-21 src]# chmod u+x /opt/apps/flannel/flannel-startup.sh
  1. [root@hdss7-21 src]# vim /etc/supervisord.d/flannel.ini
  2. [program:flanneld-7-21]
  3. command=/opt/apps/flannel/flannel-startup.sh ; the program (relative uses PATH, can take args)
  4. numprocs=1 ; number of processes copies to start (def 1)
  5. directory=/opt/apps/flannel ; directory to cwd to before exec (def no cwd)
  6. autostart=true ; start at supervisord start (default: true)
  7. autorestart=true ; retstart at unexpected quit (default: true)
  8. startsecs=30 ; number of secs prog must stay running (def. 1)
  9. startretries=3 ; max # of serial start failures (default 3)
  10. exitcodes=0,2 ; 'expected' exit codes for process (default 0,2)
  11. stopsignal=QUIT ; signal used to kill process (default TERM)
  12. stopwaitsecs=10 ; max num secs to wait b4 SIGKILL (default 10)
  13. user=root ; setuid to this UNIX account to run the program
  14. redirect_stderr=true ; redirect proc stderr to stdout (default false)
  15. stdout_logfile=/data/logs/flanneld/flanneld.stdout.log ; stderr log path, NONE for none; default AUTO
  16. stdout_logfile_maxbytes=64MB ; max # logfile bytes b4 rotation (default 50MB)
  17. stdout_logfile_backups=5 ; # of stdout logfile backups (default 10)
  18. stdout_capture_maxbytes=1MB ; number of bytes in 'capturemode' (default 0)
  19. stdout_events_enabled=false ; emit events on stdout writes (default false)
  20. [root@hdss7-21 src]# mkdir -p /data/logs/flanneld/
  21. [root@hdss7-21 src]# supervisorctl update
  22. flanneld-7-21: added process group
  23. [root@hdss7-21 src]# supervisorctl status
  24. etcd-server-7-21 RUNNING pid 1058, uptime -1 day, 16:33:25
  25. flanneld-7-21 RUNNING pid 13154, uptime 0:00:30
  26. kube-apiserver-7-21 RUNNING pid 1061, uptime -1 day, 16:33:25
  27. kube-controller-manager-7-21 RUNNING pid 1068, uptime -1 day, 16:33:25
  28. kube-kubelet-7-21 RUNNING pid 1052, uptime -1 day, 16:33:25
  29. kube-proxy-7-21 RUNNING pid 1082, uptime -1 day, 16:33:25
  30. kube-scheduler-7-21 RUNNING pid 1089, uptime -1 day, 16:33:25

5.1.4. 验证跨网络访问

  1. [root@hdss7-21 src]# kubectl get pods -o wide
  2. NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
  3. nginx-ds-7db29 1/1 Running 1 2d 172.7.22.2 hdss7-22.host.com <none> <none>
  4. nginx-ds-vvsz7 1/1 Running 1 2d 172.7.21.2 hdss7-21.host.com <none> <none>
  5. [root@hdss7-21 src]# curl -I 172.7.22.2
  6. HTTP/1.1 200 OK
  7. Server: nginx/1.17.6
  8. Date: Thu, 09 Jan 2020 14:55:21 GMT
  9. Content-Type: text/html
  10. Content-Length: 612
  11. Last-Modified: Tue, 19 Nov 2019 12:50:08 GMT
  12. Connection: keep-alive
  13. ETag: "5dd3e500-264"
  14. Accept-Ranges: bytes

5.1.5. 解决pod间IP透传问题

所有Node上操作,即优化NAT网络

  1. # 从pod a跨宿主机访问pod b时,在pod b中能看到的地址为 pod a 宿主机地址
  2. [root@nginx-ds-jdp7q /]# tail -f /usr/local/nginx/logs/access.log
  3. 10.4.7.22 - - [13/Jan/2020:13:13:39 +0000] "GET / HTTP/1.1" 200 12 "-" "curl/7.29.0"
  4. 10.4.7.22 - - [13/Jan/2020:13:14:27 +0000] "GET / HTTP/1.1" 200 12 "-" "curl/7.29.0"
  5. 10.4.7.22 - - [13/Jan/2020:13:54:20 +0000] "HEAD / HTTP/1.1" 200 0 "-" "curl/7.29.0"
  6. 10.4.7.22 - - [13/Jan/2020:13:54:25 +0000] "HEAD / HTTP/1.1" 200 0 "-" "curl/7.29.0"
  7. [root@hdss7-21 ~]# iptables-save |grep POSTROUTING|grep docker # 引发问题的规则
  8. -A POSTROUTING -s 172.7.21.0/24 ! -o docker0 -j MASQUERADE
  1. [root@hdss7-21 ~]# yum install -y iptables-services
  2. [root@hdss7-21 ~]# systemctl start iptables.service ; systemctl enable iptables.service
  3. # 需要处理的规则:
  4. [root@hdss7-21 ~]# iptables-save |grep POSTROUTING|grep docker
  5. -A POSTROUTING -s 172.7.21.0/24 ! -o docker0 -j MASQUERADE
  6. [root@hdss7-21 ~]# iptables-save | grep -i reject
  7. -A INPUT -j REJECT --reject-with icmp-host-prohibited
  8. -A FORWARD -j REJECT --reject-with icmp-host-prohibited
  9. # 处理方式:
  10. [root@hdss7-21 ~]# iptables -t nat -D POSTROUTING -s 172.7.21.0/24 ! -o docker0 -j MASQUERADE
  11. [root@hdss7-21 ~]# iptables -t nat -I POSTROUTING -s 172.7.21.0/24 ! -d 172.7.0.0/16 ! -o docker0 -j MASQUERADE
  12. [root@hdss7-21 ~]# iptables -t filter -D INPUT -j REJECT --reject-with icmp-host-prohibited
  13. [root@hdss7-21 ~]# iptables -t filter -D FORWARD -j REJECT --reject-with icmp-host-prohibited
  14. [root@hdss7-21 ~]# iptables-save > /etc/sysconfig/iptables
  1. # 此时跨宿主机访问pod时,显示pod的IP
  2. [root@nginx-ds-jdp7q /]# tail -f /usr/local/nginx/logs/access.log
  3. 172.7.22.2 - - [13/Jan/2020:14:15:39 +0000] "HEAD / HTTP/1.1" 200 0 "-" "curl/7.29.0"
  4. 172.7.22.2 - - [13/Jan/2020:14:15:47 +0000] "HEAD / HTTP/1.1" 200 0 "-" "curl/7.29.0"
  5. 172.7.22.2 - - [13/Jan/2020:14:15:48 +0000] "HEAD / HTTP/1.1" 200 0 "-" "curl/7.29.0"
  6. 172.7.22.2 - - [13/Jan/2020:14:15:48 +0000] "HEAD / HTTP/1.1" 200 0 "-" "curl/7.29.0"

5.2. CoreDNS

CoreDNS用于实现 service —> cluster IP 的DNS解析。以容器的方式交付到k8s集群,由k8s自行管理,降低人为操作的复杂度。

5.2.1. 配置yaml文件库

在hdss7-200中配置yaml文件库,后期通过Http方式去使用yaml清单文件。

  • 配置nginx虚拟主机( hdss7-200 )
  1. [root@hdss7-200 ~]# vim /etc/nginx/conf.d/k8s-yaml.od.com.conf
  2. server {
  3. listen 80;
  4. server_name k8s-yaml.od.com;
  5. location / {
  6. autoindex on;
  7. default_type text/plain;
  8. root /data/k8s-yaml;
  9. }
  10. }
  11. [root@hdss7-200 ~]# mkdir /data/k8s-yaml;
  12. [root@hdss7-200 ~]# nginx -qt && nginx -s reload
  • 配置dns解析(hdss7-11)
  1. [root@hdss7-11 ~]# vim /var/named/od.com.zone
  2. [root@hdss7-11 ~]# cat /var/named/od.com.zone
  3. $ORIGIN od.com.
  4. $TTL 600 ; 10 minutes
  5. @ IN SOA dns.od.com. dnsadmin.od.com. (
  6. 2020011301 ; serial
  7. 10800 ; refresh (3 hours)
  8. 900 ; retry (15 minutes)
  9. 604800 ; expire (1 week)
  10. 86400 ; minimum (1 day)
  11. )
  12. NS dns.od.com.
  13. $TTL 60 ; 1 minute
  14. dns A 10.4.7.11
  15. harbor A 10.4.7.200
  16. k8s-yaml A 10.4.7.200
  17. [root@hdss7-11 ~]# systemctl restart named

5.2.2. coredns的资源清单文件

清单文件存放到 hdss7-200:/data/k8s-yaml/coredns/coredns_1.6.1/

  • rabc.yaml
  1. apiVersion: v1
  2. kind: ServiceAccount
  3. metadata:
  4. name: coredns
  5. namespace: kube-system
  6. labels:
  7. kubernetes.io/cluster-service: "true"
  8. addonmanager.kubernetes.io/mode: Reconcile
  9. ---
  10. apiVersion: rbac.authorization.k8s.io/v1
  11. kind: ClusterRole
  12. metadata:
  13. labels:
  14. kubernetes.io/bootstrapping: rbac-defaults
  15. addonmanager.kubernetes.io/mode: Reconcile
  16. name: system:coredns
  17. rules:
  18. - apiGroups:
  19. - ""
  20. resources:
  21. - endpoints
  22. - services
  23. - pods
  24. - namespaces
  25. verbs:
  26. - list
  27. - watch
  28. ---
  29. apiVersion: rbac.authorization.k8s.io/v1
  30. kind: ClusterRoleBinding
  31. metadata:
  32. annotations:
  33. rbac.authorization.kubernetes.io/autoupdate: "true"
  34. labels:
  35. kubernetes.io/bootstrapping: rbac-defaults
  36. addonmanager.kubernetes.io/mode: EnsureExists
  37. name: system:coredns
  38. roleRef:
  39. apiGroup: rbac.authorization.k8s.io
  40. kind: ClusterRole
  41. name: system:coredns
  42. subjects:
  43. - kind: ServiceAccount
  44. name: coredns
  45. namespace: kube-system
  • configmap.yaml
  1. apiVersion: v1
  2. kind: ConfigMap
  3. metadata:
  4. name: coredns
  5. namespace: kube-system
  6. data:
  7. Corefile: |
  8. .:53 {
  9. errors
  10. log
  11. health
  12. ready
  13. kubernetes cluster.local 192.168.0.0/16
  14. forward . 10.4.7.11
  15. cache 30
  16. loop
  17. reload
  18. loadbalance
  19. }
  • deployment.yaml
  1. apiVersion: apps/v1
  2. kind: Deployment
  3. metadata:
  4. name: coredns
  5. namespace: kube-system
  6. labels:
  7. k8s-app: coredns
  8. kubernetes.io/name: "CoreDNS"
  9. spec:
  10. replicas: 1
  11. selector:
  12. matchLabels:
  13. k8s-app: coredns
  14. template:
  15. metadata:
  16. labels:
  17. k8s-app: coredns
  18. spec:
  19. priorityClassName: system-cluster-critical
  20. serviceAccountName: coredns
  21. containers:
  22. - name: coredns
  23. image: harbor.od.com/public/coredns:v1.6.1
  24. args:
  25. - -conf
  26. - /etc/coredns/Corefile
  27. volumeMounts:
  28. - name: config-volume
  29. mountPath: /etc/coredns
  30. ports:
  31. - containerPort: 53
  32. name: dns
  33. protocol: UDP
  34. - containerPort: 53
  35. name: dns-tcp
  36. protocol: TCP
  37. - containerPort: 9153
  38. name: metrics
  39. protocol: TCP
  40. livenessProbe:
  41. httpGet:
  42. path: /health
  43. port: 8080
  44. scheme: HTTP
  45. initialDelaySeconds: 60
  46. timeoutSeconds: 5
  47. successThreshold: 1
  48. failureThreshold: 5
  49. dnsPolicy: Default
  50. volumes:
  51. - name: config-volume
  52. configMap:
  53. name: coredns
  54. items:
  55. - key: Corefile
  56. path: Corefile
  • service.yaml
  1. apiVersion: v1
  2. kind: Service
  3. metadata:
  4. name: coredns
  5. namespace: kube-system
  6. labels:
  7. k8s-app: coredns
  8. kubernetes.io/cluster-service: "true"
  9. kubernetes.io/name: "CoreDNS"
  10. spec:
  11. selector:
  12. k8s-app: coredns
  13. clusterIP: 192.168.0.2
  14. ports:
  15. - name: dns
  16. port: 53
  17. protocol: UDP
  18. - name: dns-tcp
  19. port: 53
  20. - name: metrics
  21. port: 9153
  22. protocol: TCP

5.2.3. 交付coredns到K8s

  1. # 准备镜像
  2. [root@hdss7-200 ~]# docker pull coredns/coredns:1.6.1
  3. [root@hdss7-200 ~]# docker image tag coredns/coredns:1.6.1 harbor.od.com/public/coredns:v1.6.1
  4. [root@hdss7-200 ~]# docker image push harbor.od.com/public/coredns:v1.6.1
  1. # 交付coredns
  2. [root@hdss7-21 ~]# kubectl apply -f http://k8s-yaml.od.com/coredns/coredns_1.6.1/rbac.yaml
  3. [root@hdss7-21 ~]# kubectl apply -f http://k8s-yaml.od.com/coredns/coredns_1.6.1/configmap.yaml
  4. [root@hdss7-21 ~]# kubectl apply -f http://k8s-yaml.od.com/coredns/coredns_1.6.1/deployment.yaml
  5. [root@hdss7-21 ~]# kubectl apply -f http://k8s-yaml.od.com/coredns/coredns_1.6.1/service.yaml
  6. [root@hdss7-21 ~]# kubectl get all -n kube-system -o wide
  7. NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
  8. pod/coredns-6b6c4f9648-4vtcl 1/1 Running 0 38s 172.7.21.3 hdss7-21.host.com <none> <none>
  9. NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE SELECTOR
  10. service/coredns ClusterIP 192.168.0.2 <none> 53/UDP,53/TCP,9153/TCP 29s k8s-app=coredns
  11. NAME READY UP-TO-DATE AVAILABLE AGE CONTAINERS IMAGES SELECTOR
  12. deployment.apps/coredns 1/1 1 1 39s coredns harbor.od.com/public/coredns:v1.6.1 k8s-app=coredns
  13. NAME DESIRED CURRENT READY AGE CONTAINERS IMAGES SELECTOR
  14. replicaset.apps/coredns-6b6c4f9648 1 1 1 39s coredns harbor.od.com/public/coredns:v1.6.1 k8s-app=coredns,pod-template-hash=6b6c4f9648

5.2.4. 测试dns

  1. # 创建service
  2. [root@hdss7-21 ~]# kubectl create deployment nginx-web --image=harbor.od.com/public/nginx:src_1.14.2
  3. [root@hdss7-21 ~]# kubectl expose deployment nginx-web --port=80 --target-port=80
  4. [root@hdss7-21 ~]# kubectl get svc
  5. NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
  6. kubernetes ClusterIP 192.168.0.1 <none> 443/TCP 8d
  7. nginx-web ClusterIP 192.168.164.230 <none> 80/TCP 8s
  8. # 测试DNS,集群外必须使用FQDN(Fully Qualified Domain Name),全域名
  9. [root@hdss7-21 ~]# dig -t A nginx-web.default.svc.cluster.local @192.168.0.2 +short # 内网解析OK
  10. 192.168.164.230
  11. [root@hdss7-21 ~]# dig -t A www.baidu.com @192.168.0.2 +short # 外网解析OK
  12. www.a.shifen.com.
  13. 180.101.49.11
  14. 180.101.49.12

5.3. Ingress-Controller

service是将一组pod管理起来,提供了一个cluster ip和service name的统一访问入口,屏蔽了pod的ip变化。 ingress 是一种基于七层的流量转发策略,即将符合条件的域名或者location流量转发到特定的service上,而ingress仅仅是一种规则,k8s内部并没有自带代理程序完成这种规则转发。
ingress-controller 是一个代理服务器,将ingress的规则能真正实现的方式,常用的有 nginx,traefik,haproxy。但是在k8s集群中,建议使用traefik,性能比haroxy强大,更新配置不需要重载服务,是首选的ingress-controller。github地址:https://github.com/containous/traefik

5.3.1. 配置traefik资源清单

清单文件存放到 hdss7-200:/data/k8s-yaml/traefik/traefik_1.7.2

  • rbac.yaml
  1. apiVersion: v1
  2. kind: ServiceAccount
  3. metadata:
  4. name: traefik-ingress-controller
  5. namespace: kube-system
  6. ---
  7. apiVersion: rbac.authorization.k8s.io/v1beta1
  8. kind: ClusterRole
  9. metadata:
  10. name: traefik-ingress-controller
  11. rules:
  12. - apiGroups:
  13. - ""
  14. resources:
  15. - services
  16. - endpoints
  17. - secrets
  18. verbs:
  19. - get
  20. - list
  21. - watch
  22. - apiGroups:
  23. - extensions
  24. resources:
  25. - ingresses
  26. verbs:
  27. - get
  28. - list
  29. - watch
  30. ---
  31. kind: ClusterRoleBinding
  32. apiVersion: rbac.authorization.k8s.io/v1beta1
  33. metadata:
  34. name: traefik-ingress-controller
  35. roleRef:
  36. apiGroup: rbac.authorization.k8s.io
  37. kind: ClusterRole
  38. name: traefik-ingress-controller
  39. subjects:
  40. - kind: ServiceAccount
  41. name: traefik-ingress-controller
  42. namespace: kube-system
  • daemonset.yaml
  1. apiVersion: extensions/v1beta1
  2. kind: DaemonSet
  3. metadata:
  4. name: traefik-ingress
  5. namespace: kube-system
  6. labels:
  7. k8s-app: traefik-ingress
  8. spec:
  9. template:
  10. metadata:
  11. labels:
  12. k8s-app: traefik-ingress
  13. name: traefik-ingress
  14. spec:
  15. serviceAccountName: traefik-ingress-controller
  16. terminationGracePeriodSeconds: 60
  17. containers:
  18. - image: harbor.od.com/public/traefik:v1.7.2
  19. name: traefik-ingress
  20. ports:
  21. - name: controller
  22. containerPort: 80
  23. hostPort: 81
  24. - name: admin-web
  25. containerPort: 8080
  26. securityContext:
  27. capabilities:
  28. drop:
  29. - ALL
  30. add:
  31. - NET_BIND_SERVICE
  32. args:
  33. - --api
  34. - --kubernetes
  35. - --logLevel=INFO
  36. - --insecureskipverify=true
  37. - --kubernetes.endpoint=https://10.4.7.10:7443
  38. - --accesslog
  39. - --accesslog.filepath=/var/log/traefik_access.log
  40. - --traefiklog
  41. - --traefiklog.filepath=/var/log/traefik.log
  42. - --metrics.prometheus
  • service.yaml
  1. kind: Service
  2. apiVersion: v1
  3. metadata:
  4. name: traefik-ingress-service
  5. namespace: kube-system
  6. spec:
  7. selector:
  8. k8s-app: traefik-ingress
  9. ports:
  10. - protocol: TCP
  11. port: 80
  12. name: controller
  13. - protocol: TCP
  14. port: 8080
  15. name: admin-web
  • ingress.yaml
  1. apiVersion: extensions/v1beta1
  2. kind: Ingress
  3. metadata:
  4. name: traefik-web-ui
  5. namespace: kube-system
  6. annotations:
  7. kubernetes.io/ingress.class: traefik
  8. spec:
  9. rules:
  10. - host: traefik.od.com
  11. http:
  12. paths:
  13. - path: /
  14. backend:
  15. serviceName: traefik-ingress-service
  16. servicePort: 8080
  • 准备镜像
  1. [root@hdss7-200 traefik_1.7.2]# docker pull traefik:v1.7.2-alpine
  2. [root@hdss7-200 traefik_1.7.2]# docker image tag traefik:v1.7.2-alpine harbor.od.com/public/traefik:v1.7.2
  3. [root@hdss7-200 traefik_1.7.2]# docker push harbor.od.com/public/traefik:v1.7.2

5.3.2. 交付traefik到k8s

  1. [root@hdss7-21 ~]# kubectl apply -f http://k8s-yaml.od.com/traefik/traefik_1.7.2/rbac.yaml
  2. [root@hdss7-21 ~]# kubectl apply -f http://k8s-yaml.od.com/traefik/traefik_1.7.2/daemonset.yaml
  3. [root@hdss7-21 ~]# kubectl apply -f http://k8s-yaml.od.com/traefik/traefik_1.7.2/service.yaml
  4. [root@hdss7-21 ~]# kubectl apply -f http://k8s-yaml.od.com/traefik/traefik_1.7.2/ingress.yaml
  1. [root@hdss7-21 ~]# kubectl get pods -n kube-system -o wide
  2. NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
  3. coredns-6b6c4f9648-4vtcl 1/1 Running 1 24h 172.7.21.3 hdss7-21.host.com <none> <none>
  4. traefik-ingress-4gm4w 1/1 Running 0 77s 172.7.21.5 hdss7-21.host.com <none> <none>
  5. traefik-ingress-hwr2j 1/1 Running 0 77s 172.7.22.3 hdss7-22.host.com <none> <none>
  6. [root@hdss7-21 ~]# kubectl get ds -n kube-system
  7. NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
  8. traefik-ingress 2 2 2 2 2 <none> 107s

5.3.3. 配置外部nginx负载均衡

  • 在hdss7-11,hdss7-12 配置nginx L7转发
  1. [root@hdss7-11 ~]# vim /etc/nginx/conf.d/od.com.conf
  2. server {
  3. server_name *.od.com;
  4. location / {
  5. proxy_pass http://default_backend_traefik;
  6. proxy_set_header Host $http_host;
  7. proxy_set_header x-forwarded-for $proxy_add_x_forwarded_for;
  8. }
  9. }
  10. upstream default_backend_traefik {
  11. # 所有的nodes都放到upstream中
  12. server 10.4.7.21:81 max_fails=3 fail_timeout=10s;
  13. server 10.4.7.22:81 max_fails=3 fail_timeout=10s;
  14. }
  15. [root@hdss7-11 ~]# nginx -tq && nginx -s reload
  • 配置dns解析
  1. [root@hdss7-11 ~]# vim /var/named/od.com.zone
  2. $ORIGIN od.com.
  3. $TTL 600 ; 10 minutes
  4. @ IN SOA dns.od.com. dnsadmin.od.com. (
  5. 2020011302 ; serial
  6. 10800 ; refresh (3 hours)
  7. 900 ; retry (15 minutes)
  8. 604800 ; expire (1 week)
  9. 86400 ; minimum (1 day)
  10. )
  11. NS dns.od.com.
  12. $TTL 60 ; 1 minute
  13. dns A 10.4.7.11
  14. harbor A 10.4.7.200
  15. k8s-yaml A 10.4.7.200
  16. traefik A 10.4.7.10
  17. [root@hdss7-11 ~]# systemctl restart named
  • 查看traefik网页

image.png

5.4. dashboard

5.4.1. 配置资源清单

清单文件存放到 hdss7-200:/data/k8s-yaml/dashboard/dashboard_1.10.1

  • 准备镜像
  1. # 镜像准备
  2. # 因不可描述原因,无法访问k8s.gcr.io,改成registry.aliyuncs.com/google_containers
  3. [root@hdss7-200 ~]# docker image pull registry.aliyuncs.com/google_containers/kubernetes-dashboard-amd64:v1.10.1
  4. [root@hdss7-200 ~]# docker image tag f9aed6605b81 harbor.od.com/public/kubernetes-dashboard-amd64:v1.10.1
  5. [root@hdss7-200 ~]# docker image push harbor.od.com/public/kubernetes-dashboard-amd64:v1.10.1
  • rbac.yaml
  1. apiVersion: v1
  2. kind: ServiceAccount
  3. metadata:
  4. labels:
  5. k8s-app: kubernetes-dashboard
  6. addonmanager.kubernetes.io/mode: Reconcile
  7. name: kubernetes-dashboard-admin
  8. namespace: kube-system
  9. ---
  10. apiVersion: rbac.authorization.k8s.io/v1
  11. kind: ClusterRoleBinding
  12. metadata:
  13. name: kubernetes-dashboard-admin
  14. namespace: kube-system
  15. labels:
  16. k8s-app: kubernetes-dashboard
  17. addonmanager.kubernetes.io/mode: Reconcile
  18. roleRef:
  19. apiGroup: rbac.authorization.k8s.io
  20. kind: ClusterRole
  21. name: cluster-admin
  22. subjects:
  23. - kind: ServiceAccount
  24. name: kubernetes-dashboard-admin
  25. namespace: kube-system
  • deployment.yaml
  1. apiVersion: apps/v1
  2. kind: Deployment
  3. metadata:
  4. name: kubernetes-dashboard
  5. namespace: kube-system
  6. labels:
  7. k8s-app: kubernetes-dashboard
  8. kubernetes.io/cluster-service: "true"
  9. addonmanager.kubernetes.io/mode: Reconcile
  10. spec:
  11. selector:
  12. matchLabels:
  13. k8s-app: kubernetes-dashboard
  14. template:
  15. metadata:
  16. labels:
  17. k8s-app: kubernetes-dashboard
  18. annotations:
  19. scheduler.alpha.kubernetes.io/critical-pod: ''
  20. spec:
  21. priorityClassName: system-cluster-critical
  22. containers:
  23. - name: kubernetes-dashboard
  24. image: harbor.od.com/public/kubernetes-dashboard-amd64:v1.10.1
  25. resources:
  26. limits:
  27. cpu: 100m
  28. memory: 300Mi
  29. requests:
  30. cpu: 50m
  31. memory: 100Mi
  32. ports:
  33. - containerPort: 8443
  34. protocol: TCP
  35. args:
  36. # PLATFORM-SPECIFIC ARGS HERE
  37. - --auto-generate-certificates
  38. volumeMounts:
  39. - name: tmp-volume
  40. mountPath: /tmp
  41. livenessProbe:
  42. httpGet:
  43. scheme: HTTPS
  44. path: /
  45. port: 8443
  46. initialDelaySeconds: 30
  47. timeoutSeconds: 30
  48. volumes:
  49. - name: tmp-volume
  50. emptyDir: {}
  51. serviceAccountName: kubernetes-dashboard-admin
  52. tolerations:
  53. - key: "CriticalAddonsOnly"
  54. operator: "Exists"
  • service.yaml
  1. apiVersion: v1
  2. kind: Service
  3. metadata:
  4. name: kubernetes-dashboard
  5. namespace: kube-system
  6. labels:
  7. k8s-app: kubernetes-dashboard
  8. kubernetes.io/cluster-service: "true"
  9. addonmanager.kubernetes.io/mode: Reconcile
  10. spec:
  11. selector:
  12. k8s-app: kubernetes-dashboard
  13. ports:
  14. - port: 443
  15. targetPort: 8443
  • ingress.yaml
  1. apiVersion: extensions/v1beta1
  2. kind: Ingress
  3. metadata:
  4. name: kubernetes-dashboard
  5. namespace: kube-system
  6. annotations:
  7. kubernetes.io/ingress.class: traefik
  8. spec:
  9. rules:
  10. - host: dashboard.od.com
  11. http:
  12. paths:
  13. - backend:
  14. serviceName: kubernetes-dashboard
  15. servicePort: 443

5.4.2. 交付dashboard到k8s

  1. [root@hdss7-21 ~]# kubectl apply -f http://k8s-yaml.od.com/dashboard/dashboard_1.10.1/rbac.yaml
  2. [root@hdss7-21 ~]# kubectl apply -f http://k8s-yaml.od.com/dashboard/dashboard_1.10.1/deployment.yaml
  3. [root@hdss7-21 ~]# kubectl apply -f http://k8s-yaml.od.com/dashboard/dashboard_1.10.1/service.yaml
  4. [root@hdss7-21 ~]# kubectl apply -f http://k8s-yaml.od.com/dashboard/dashboard_1.10.1/ingress.yaml

5.4.3. 配置DNS解析

  1. [root@hdss7-11 ~]# vim /var/named/od.com.zone
  2. $ORIGIN od.com.
  3. $TTL 600 ; 10 minutes
  4. @ IN SOA dns.od.com. dnsadmin.od.com. (
  5. 2020011303 ; serial
  6. 10800 ; refresh (3 hours)
  7. 900 ; retry (15 minutes)
  8. 604800 ; expire (1 week)
  9. 86400 ; minimum (1 day)
  10. )
  11. NS dns.od.com.
  12. $TTL 60 ; 1 minute
  13. dns A 10.4.7.11
  14. harbor A 10.4.7.200
  15. k8s-yaml A 10.4.7.200
  16. traefik A 10.4.7.10
  17. dashboard A 10.4.7.10
  18. [root@hdss7-11 ~]# systemctl restart named.service

5.4.4. 签发SSL证书

  1. [root@hdss7-200 ~]# cd /opt/certs/
  2. [root@hdss7-200 certs]# (umask 077; openssl genrsa -out dashboard.od.com.key 2048)
  3. [root@hdss7-200 certs]# openssl req -new -key dashboard.od.com.key -out dashboard.od.com.csr -subj "/CN=dashboard.od.com/C=CN/ST=BJ/L=Beijing/O=OldboyEdu/OU=ops"
  4. [root@hdss7-200 certs]# openssl x509 -req -in dashboard.od.com.csr -CA ca.pem -CAkey ca-key.pem -CAcreateserial -out dashboard.od.com.crt -days 3650
  5. [root@hdss7-200 certs]# ll dashboard.od.com.*
  6. -rw-r--r-- 1 root root 1196 Jan 29 20:52 dashboard.od.com.crt
  7. -rw-r--r-- 1 root root 1005 Jan 29 20:51 dashboard.od.com.csr
  8. -rw------- 1 root root 1675 Jan 29 20:51 dashboard.od.com.key
  9. [root@hdss7-200 certs]# scp dashboard.od.com.key dashboard.od.com.crt hdss7-11:/etc/nginx/certs/
  10. [root@hdss7-200 certs]# scp dashboard.od.com.key dashboard.od.com.crt hdss7-12:/etc/nginx/certs/

5.4.5. 配置Nginx

  1. # hdss7-11和hdss7-12都需要操作
  2. [root@hdss7-11 ~]# vim /etc/nginx/conf.d/dashborad.conf
  3. server {
  4. listen 80;
  5. server_name dashboard.od.com;
  6. rewrite ^(.*)$ https://${server_name}$1 permanent;
  7. }
  8. server {
  9. listen 443 ssl;
  10. server_name dashboard.od.com;
  11. ssl_certificate "certs/dashboard.od.com.crt";
  12. ssl_certificate_key "certs/dashboard.od.com.key";
  13. ssl_session_cache shared:SSL:1m;
  14. ssl_session_timeout 10m;
  15. ssl_ciphers HIGH:!aNULL:!MD5;
  16. ssl_prefer_server_ciphers on;
  17. location / {
  18. proxy_pass http://default_backend_traefik;
  19. proxy_set_header Host $http_host;
  20. proxy_set_header x-forwarded-for $proxy_add_x_forwarded_for;
  21. }
  22. }
  23. [root@hdss7-11 ~]# nginx -t && nginx -s reload

image.png

5.4.6. 测试token登陆

  1. [root@hdss7-21 ~]# kubectl get secret -n kube-system|grep kubernetes-dashboard-token
  2. kubernetes-dashboard-token-hr5rj kubernetes.io/service-account-token 3 17m
  3. [root@hdss7-21 ~]# kubectl describe secret kubernetes-dashboard-token-hr5rj -n kube-system|grep ^token
  4. token: eyJhbGciOiJSUzI1NiIsImtpZCI6IiJ9.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJrdWJlLXN5c3RlbSIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VjcmV0Lm5hbWUiOiJrdWJlcm5ldGVzLWRhc2hib2FyZC10b2tlbi1ocjVyaiIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VydmljZS1hY2NvdW50Lm5hbWUiOiJrdWJlcm5ldGVzLWRhc2hib2FyZCIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VydmljZS1hY2NvdW50LnVpZCI6ImZhNzAxZTRmLWVjMGItNDFkNS04NjdmLWY0MGEwYmFkMjFmNSIsInN1YiI6InN5c3RlbTpzZXJ2aWNlYWNjb3VudDprdWJlLXN5c3RlbTprdWJlcm5ldGVzLWRhc2hib2FyZCJ9.SDUZEkH_N0B6rjm6bW_jN03F4pHCPafL3uKD2HU0ksM0oenB2425jxvfi16rUbTRCsfcGqYXRrE2x15gpb03fb3jJy-IhnInUnPrw6ZwEdqWagen_Z4tdFhUgCpdjdShHy40ZPfql_iuVKbvv7ASt8w8v13Ar3FxztyDyLScVO3rNEezT7JUqMI4yj5LYQ0IgpSXoH12tlDSTyX8Rk2a_3QlOM_yT5GB_GEZkwIESttQKVr7HXSCrQ2tEdYA4cYO2AbF1NgAo_CVBNNvZLvdDukWiQ_b5zwOiO0cUbbiu46x_p6gjNWzVb7zHNro4gh0Shr4hIhiRQot2DJ-sq94Ag

image.png