二進(jìn)制部署kubernetes1.12.1

環(huán)境準(zhǔn)備

192.168.241.130 master
192.168.241.131 node1
192.168.241.132 node1

設(shè)置永久主機(jī)名稱，然后重新登錄

hostnamectl set-hostname master
hostnamectl set-hostname node1
hostnamectl set-hostname node2

修改 /etc/hostname 文件,添加主機(jī)名和 IP 的對應(yīng)關(guān)系：

$ vim /etc/hosts
192.168.241.130 master
192.168.241.131 node1
192.168.241.132 node1

在每臺機(jī)器上關(guān)閉防火墻：

$ systemctl stop firewalld
$ systemctl disable firewalld

如果開啟了swap分區(qū),kubelet 會啟動失敗(可以通過將參數(shù) --fail-swap-on 設(shè)置為false 來忽略 swap on),故需要在每臺機(jī)器上關(guān)閉 swap 分區(qū)：

$ swapoff -a

關(guān)閉 SELinux，否則后續(xù) K8S 掛載目錄時(shí)可能報(bào)錯(cuò) Permission denied ：

$  setenforce 0
修改配置文件，永久生效；
$ grep SELINUX /etc/selinux/config
SELINUX=disabled

更新系統(tǒng)時(shí)間

$ yum -y install ntpdate
$ ntpdate cn.pool.ntp.org

以上環(huán)境準(zhǔn)備完成

開始部署etcd集群

二進(jìn)制包下載地址：https://gitlub.com/etcd-io/etcd/releases

分別創(chuàng)建以下目錄 后期好管理

[root@master ~]# mkdir -p /root/k8s/k8s-cert   //存放k8s證書
[root@master ~]# mkdir -p /root/k8s/etcd-cert  //存放etcd證書

上傳腳本到/root/k8s/etcd-cert路勁下(總腳本 以下會分開執(zhí)行)

[root@master ~]# cat /root/k8s/etcd-cert/etcd-cert.sh
cat > ca-config.json <<EOF
{
  "signing": {
    "default": {
      "expiry": "87600h"
    },
    "profiles": {
      "www": {
         "expiry": "87600h",
         "usages": [
            "signing",
            "key encipherment",
            "server auth",
            "client auth"
        ]
      }
    }
  }
}
EOF

cat > ca-csr.json <<EOF
{
    "CN": "etcd CA",
    "key": {
        "algo": "rsa",
        "size": 2048
    },
    "names": [
        {
            "C": "CN",
            "L": "Beijing",
            "ST": "Beijing"
        }
    ]
}
EOF

cfssl gencert -initca ca-csr.json | cfssljson -bare ca -

#-----------------------

cat > server-csr.json <<EOF
{
    "CN": "etcd",
    "hosts": [
    "192.168.241.130",
    "192.168.241.131",
    "192.168.241.132"
    ],
    "key": {
        "algo": "rsa",
        "size": 2048
    },
    "names": [
        {
            "C": "CN",
            "L": "BeiJing",
            "ST": "BeiJing"
        }
    ]
}
EOF

cfssl gencert -ca=ca.pem -ca-key=ca-key.pem -config=ca-config.json -profile=www server-csr.json | cfssljson -bare server

下載生成etcd證書工具cssl

執(zhí)行腳本
[root@master ~]# bash /root/k8s/etcd-cert/cfssl.sh
curl -L https://pkg.cfssl.org/R1.2/cfssl_linux-amd64 -o /usr/local/bin/cfssl
curl -L https://pkg.cfssl.org/R1.2/cfssljson_linux-amd64 -o /usr/local/bin/cfssljson
curl -L https://pkg.cfssl.org/R1.2/cfssl-certinfo_linux-amd64 -o /usr/local/bin/cfssl-certinfo
chmod +x /usr/local/bin/cfssl /usr/local/bin/cfssljson /usr/local/bin/cfssl-certinfo

輸入cf再按tab鍵3查看是否安裝成功

執(zhí)行以下腳本生成ca證書json文件

cat > ca-config.json <<EOF
{
  "signing": {
    "default": {
      "expiry": "87600h"
    },
    "profiles": {
      "www": {
         "expiry": "87600h",
         "usages": [
            "signing",
            "key encipherment",
            "server auth",
            "client auth"
        ]
      }
    }
  }
}
EOF

cat > ca-csr.json <<EOF
{
    "CN": "etcd CA",
    "key": {
        "algo": "rsa",
        "size": 2048
    },
    "names": [
        {
            "C": "CN",
            "L": "Beijing",
            "ST": "Beijing"
        }
    ]
}
EOF


[root@master etcd-cert]# ls /root/k8s/etcd-cert   //查看json文件

再執(zhí)行：
[root@master etcd-cert]# cfssl gencert -initca ca-csr.json | cfssljson -bare ca -    //生成根證書
會生成ca-key.pem    and  ca.pem文件

生成一個(gè)etcd的域名證書

cat > server-csr.json <<EOF
{
    "CN": "etcd",
    "hosts": [
    "192.168.241.130",
    "192.168.241.131",
    "192.168.241.132"
    ],
    "key": {
        "algo": "rsa",
        "size": 2048
    },
    "names": [
        {
            "C": "CN",
            "L": "BeiJing",
            "ST": "BeiJing"
        }
    ]
}
EOF
##注意修改ip

[root@master etcd-cert]# ls
ca-config.json  ca-csr.json  ca.pem    etcd-cert.sh  server-csr.json  server.pem
ca.csr          ca-key.pem   cfssl.sh  server.csr    server-key.pem


再執(zhí)行：
[root@master etcd-cert]#    cfssl gencert -ca=ca.pem -ca-key=ca-key.pem -config=ca-config.json -profile=www server-csr.json | cfssljson -bare server
##出現(xiàn)警告可以忽略

以上證書準(zhǔn)備完成

接下來安裝etcd

[root@master ~]#  mkdir  /root/soft //存放安裝包
 etcd-v3.3.10-linux-amd64.tar.gz
解壓文件
[root@master soft]# tar -xf etcd-v3.3.10-linux-amd64.tar.gz 

創(chuàng)建etcd安裝目錄
[root@master ~]#  mkdir -p /opt/etcd/{cfg,bin,ssl}

講解壓出來的兩個(gè)文件移動到安裝etcd的bin目錄中
[root@master ~]#  cd  /root/soft/etcd-v3.3.10-linux-amd64
[root@master etcd-v3.3.10-linux-amd64]# mv etcd etcdctl /opt/etcd/bin/

編寫創(chuàng)建etcd腳本

#!/bin/bash
# example: ./etcd.sh etcd01 192.168.241.130 etcd02=https://192.168.241.131:2380,etcd03=https://192.168.241.132:2380

ETCD_NAME=$1
ETCD_IP=$2
ETCD_CLUSTER=$3

WORK_DIR=/opt/etcd

cat <<EOF >$WORK_DIR/cfg/etcd
#[Member]
ETCD_NAME="${ETCD_NAME}"
ETCD_DATA_DIR="/var/lib/etcd/default.etcd"
ETCD_LISTEN_PEER_URLS="https://${ETCD_IP}:2380"
ETCD_LISTEN_CLIENT_URLS="https://${ETCD_IP}:2379"

#[Clustering]
ETCD_INITIAL_ADVERTISE_PEER_URLS="https://${ETCD_IP}:2380"
ETCD_ADVERTISE_CLIENT_URLS="https://${ETCD_IP}:2379"
ETCD_INITIAL_CLUSTER="etcd01=https://${ETCD_IP}:2380,${ETCD_CLUSTER}"
ETCD_INITIAL_CLUSTER_TOKEN="etcd-cluster"
ETCD_INITIAL_CLUSTER_STATE="new"
EOF

cat <<EOF >/usr/lib/systemd/system/etcd.service
[Unit]
Description=Etcd Server
After=network.target
After=network-online.target
Wants=network-online.target

[Service]
Type=notify
EnvironmentFile=${WORK_DIR}/cfg/etcd
ExecStart=${WORK_DIR}/bin/etcd \
--name=\${ETCD_NAME} \
--data-dir=\${ETCD_DATA_DIR} \
--listen-peer-urls=\${ETCD_LISTEN_PEER_URLS} \
--listen-client-urls=\${ETCD_LISTEN_CLIENT_URLS},http://127.0.0.1:2379 \
--advertise-client-urls=\${ETCD_ADVERTISE_CLIENT_URLS} \
--initial-advertise-peer-urls=\${ETCD_INITIAL_ADVERTISE_PEER_URLS} \
--initial-cluster=\${ETCD_INITIAL_CLUSTER} \
--initial-cluster-token=\${ETCD_INITIAL_CLUSTER_TOKEN} \
--initial-cluster-state=new \
--cert-file=${WORK_DIR}/ssl/server.pem \
--key-file=${WORK_DIR}/ssl/server-key.pem \
--peer-cert-file=${WORK_DIR}/ssl/server.pem \
--peer-key-file=${WORK_DIR}/ssl/server-key.pem \
--trusted-ca-file=${WORK_DIR}/ssl/ca.pem \
--peer-trusted-ca-file=${WORK_DIR}/ssl/ca.pem
Restart=on-failure
LimitNOFILE=65536

[Install]
WantedBy=multi-user.target
EOF

systemctl daemon-reload
systemctl enable etcd
systemctl start etcd

增加腳本權(quán)限
[root@master ~]#  chmod +x /root/k8s/etcd.sh

執(zhí)行腳本
[root@master k8s]#  ./etcd.sh etcd01 192.168.241.130 etcd02=https://192.168.241.131:2380,etcd03=https://192.168.241.132:2380

##會出現(xiàn)報(bào)錯(cuò)
可以查看/opt/etcd/cfg/etcd和/use/lib/systemd/system/etcd.service文件

講證書拷貝到/opt/etcd/ssl下

[root@master k8s]# cp /root/k8s/etcd-cert/{ca,server-key,server}.pem /opt/etcd/ssl/

啟動etcd

[root@master k8s]#  systemctl start etcd
會出現(xiàn)錯(cuò)誤 但是主節(jié)點(diǎn)是啟動狀態(tài)
tail -f /var/log/messages 查看日志

分別向node1和node2拷貝文件

scp -r /opt/etcd/ 192.168.241.131:/opt/

scp -r /opt/etcd/ 192.168.241.132:/opt/

scp /usr/lib/systemd/system/etcd.service 192.168.241.131:/usr/lib/systemd/system

scp /usr/lib/systemd/system/etcd.service 192.168.241.132:/usr/lib/systemd/system

此時(shí)還不能夠啟動etcd集群
要修改node1和node2配置文件中的ip和etcd名字

[root@master cfg]# vim /opt/etcd/cfg/etcd 
#[Member]
ETCD_NAME="etcd01"  //要修改
ETCD_DATA_DIR="/var/lib/etcd/default.etcd"
ETCD_LISTEN_PEER_URLS="https://192.168.241.130:2380"  //ip修改
ETCD_LISTEN_CLIENT_URLS="https://192.168.241.130:2379"  ////ip修改

#[Clustering]
ETCD_INITIAL_ADVERTISE_PEER_URLS="https://192.168.241.130:2380" //ip修改
ETCD_ADVERTISE_CLIENT_URLS="https://192.168.241.130:2379"   ////ip修改
ETCD_INITIAL_CLUSTER="etcd01=https://192.168.241.130:2380,etcd02=https://192.168.241.131:2380,etcd03=https://192.168.241.
132:2380"
ETCD_INITIAL_CLUSTER_TOKEN="etcd-cluster"
ETCD_INITIAL_CLUSTER_STATE="new"

三臺機(jī)器分別執(zhí)行

systemctl daemon-reload 
systemctl start etcd 
ps -ef |grep etcd //查看進(jìn)程

查看集群狀態(tài)

[root@master k8s]# /opt/etcd/bin/etcdctl --ca-file=/opt/etcd/ssl/ca.pem --cert-file=/opt/etcd/ssl/server.pem --key-file=/opt/etcd/ssl/server-key.pem --endpoints="https://192.168.241.130:2379,https://192.168.241.131:2379,https://192.168.241.132:2379" cluster-health
member 951e78d92214d87b is healthy: got healthy result from https://192.168.241.132:2379
member a8d3d8b4942ac39e is healthy: got healthy result from https://192.168.241.130:2379
member c1e11c263eb397b7 is healthy: got healthy result from https://192.168.241.131:2379
cluster is healthy
說明etcd集群創(chuàng)建成功

安裝docker(略)

kubernetes網(wǎng)絡(luò)模型(CNI)

Container Network Interface(CNI):容器網(wǎng)絡(luò)接口
kubernetes網(wǎng)絡(luò)模型設(shè)計(jì)要求

一個(gè)pod一個(gè)ip
每個(gè)pod獨(dú)立ip，pod內(nèi)所有容器共享網(wǎng)絡(luò)(同一個(gè)ip)
所有容器都可以與所有其他容器通信
所有節(jié)點(diǎn)都可以與所有容器通信

部署flannel網(wǎng)絡(luò)

步驟

1,寫入分配的子網(wǎng)段到etcd，供flannel使用

/opt/etcd/bin/etcdctl --ca-file=/opt/etcd/ssl/ca.pem --cert-file=/opt/etcd/ssl/server.pem --key-file=/opt/etcd/ssl/server-key.pem --endpoints="https://192.168.241.130:2379,https://192.168.241.131:2379,https://192.168.241.132:2379" set /coreos.com/network/config '{ "Network": "172.17.0.0/16", "Backend": {"Type": "vxlan"}}'

2,下載二進(jìn)制包：https://github.com/coreos/flannel/releases
3,部署與配置flannel
4,systemd管理flannel
5,配置docker使用flannel生成的子網(wǎng)
6,啟動flannel

開始

編寫flannel腳本
[root@slave1 ~]# vim flannel.sh

#!/bin/bash

ETCD_ENDPOINTS=${1:-"http://127.0.0.1:2379"}
#生成flannel文件

cat <<EOF >/opt/kubernetes/cfg/flanneld

FLANNEL_OPTIONS="--etcd-endpoints=${ETCD_ENDPOINTS} \
-etcd-cafile=/opt/etcd/ssl/ca.pem \
-etcd-certfile=/opt/etcd/ssl/server.pem \
-etcd-keyfile=/opt/etcd/ssl/server-key.pem"

EOF
#生成flannel service配置文件
cat <<EOF >/usr/lib/systemd/system/flanneld.service
[Unit]
Description=Flanneld overlay address etcd agent
After=network-online.target network.target
Before=docker.service

[Service]
Type=notify
EnvironmentFile=/opt/kubernetes/cfg/flanneld
ExecStart=/opt/kubernetes/bin/flanneld --ip-masq \$FLANNEL_OPTIONS
ExecStartPost=/opt/kubernetes/bin/mk-docker-opts.sh -k DOCKER_NETWORK_OPTIONS -d /run/flannel/subnet.env
Restart=on-failure

[Install]
WantedBy=multi-user.target

EOF
#修改docker service文件
cat <<EOF >/usr/lib/systemd/system/docker.service

[Unit]
Description=Docker Application Container Engine
Documentation=https://docs.docker.com
After=network-online.target firewalld.service
Wants=network-online.target

[Service]
Type=notify
EnvironmentFile=/run/flannel/subnet.env
ExecStart=/usr/bin/dockerd \$DOCKER_NETWORK_OPTIONS
ExecReload=/bin/kill -s HUP \$MAINPID
LimitNOFILE=infinity
LimitNPROC=infinity
LimitCORE=infinity
TimeoutStartSec=0
Delegate=yes
KillMode=process
Restart=on-failure
StartLimitBurst=3
StartLimitInterval=60s

[Install]
WantedBy=multi-user.target

EOF

systemctl daemon-reload
systemctl enable flanneld
systemctl restart flanneld
systemctl restart docker

可以在master上操作，我在node上操作的

node1

創(chuàng)建flannel工作目錄
[root@slave1 ~]# mkdir -p /opt/kubernetes/{bin,cfg,ssl}
解壓安裝包
[root@slave1 ~]# tar -xf flannel-v0.10.0-linux-amd64.tar.gz
移動解壓出的配置文件到安裝目錄
[root@slave1 ~]# mv flanneld mk-docker-opts.sh /opt/kubernetes/bin/
執(zhí)行腳本
[root@slave1 ~]# ./flannel.sh 
重啟docker
[root@slave1 ~]# systemctl restart docker
驗(yàn)證docker ip和flannel ip是否在一個(gè)網(wǎng)段

node2節(jié)點(diǎn)直接拷貝文件就行

[root@slave1 ~]# scp /usr/lib/systemd/system/{flanneld,docker}.service node2:/usr/lib/systemd/system
node2:/usr/lib/systemd/system
[root@slave1 ~]# scp -r /opt/kubernetes node2:/opt/
啟動flannel
[root@slave2 ~]# systemctl start flanneld
重啟docker
[root@slave2 ~]# systemctl daemon-reload
[root@slave1 ~]# systemctl restart docker
驗(yàn)證docker ip和flannel ip是否在一個(gè)網(wǎng)段

在node1和node2分別創(chuàng)建一個(gè)容器，測試網(wǎng)絡(luò)連通信(容器與容器之間，宿主機(jī)與容器之間)
以上flannel環(huán)境部署完成

開始部署master組件

1,kube-apiserver  //必須先部署
2,kube-controller-manager
3,kube-scheduler
下載地址目前github下載不了

部署kube-apiserver
編寫apiserver腳本
[root@master k8s]# vim apiserver.sh

#!/bin/bash

MASTER_ADDRESS=$1   //apiserver地址
ETCD_SERVERS=$2        //etcd地址
cat <<EOF >/opt/kubernetes/cfg/kube-apiserver

KUBE_APISERVER_OPTS="--logtostderr=true \\
--v=4 \\
--etcd-servers=${ETCD_SERVERS} \\
--bind-address=${MASTER_ADDRESS} \\
--secure-port=6443 \\
--advertise-address=${MASTER_ADDRESS} \\
--allow-privileged=true \\
--service-cluster-ip-range=10.0.0.0/24 \\
--enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,ResourceQuota,NodeRestriction \\
--authorization-mode=RBAC,Node \\
--kubelet-https=true \\
--enable-bootstrap-token-auth \\
--token-auth-file=/opt/kubernetes/cfg/token.csv \\
--service-node-port-range=30000-50000 \\
--tls-cert-file=/opt/kubernetes/ssl/server.pem  \\
--tls-private-key-file=/opt/kubernetes/ssl/server-key.pem \\
--client-ca-file=/opt/kubernetes/ssl/ca.pem \\
--service-account-key-file=/opt/kubernetes/ssl/ca-key.pem \\
--etcd-cafile=/opt/etcd/ssl/ca.pem \\
--etcd-certfile=/opt/etcd/ssl/server.pem \\
--etcd-keyfile=/opt/etcd/ssl/server-key.pem"
EOF

cat <<EOF >/usr/lib/systemd/system/kube-apiserver.service
[Unit]
Description=Kubernetes API Server
Documentation=https://github.com/kubernetes/kubernetes

[Service]
EnvironmentFile=-/opt/kubernetes/cfg/kube-apiserver
ExecStart=/opt/kubernetes/bin/kube-apiserver \$KUBE_APISERVER_OPTS
Restart=on-failure

[Install]
WantedBy=multi-user.target
EOF

systemctl daemon-reload
systemctl enable kube-apiserver
systemctl restart kube-apiserver

解壓安裝包

[root@master ~]#  mkdir -p /opt/kubernetes/{bin,ssl,cfg}  //創(chuàng)建kubernetes安裝目錄
[root@master soft]#  tar -xf kubernetes-server-linux-amd64.tar.gz

進(jìn)入/root/soft/kubernetes/server/bin這個(gè)目錄下拷貝以下內(nèi)容
[root@master bin]#  cp kube-apiserver kube-controller-manager kube-scheduler /opt/kubernetes/bin/

執(zhí)行apiserver腳本

[root@master k8s]# ./apiserver.sh 192.168.241.130 https://192.168.241.130:2379,https://192.168.241.131:2379,https://192.168.241.132:2379

指定日志路勁
[root@master cfg]# vim /opt/kubernetes/cfg/kube-apiserver

將KUBE_APISERVER_OPTS="--logtostderr=true 
改為
KUBE_APISERVER_OPTS="--logtostderr=false
再添加
--log-dir=日志路勁
重新執(zhí)行腳本即可

生成k8s證書

編寫腳本
vim /root/k8s/k8s-cert/k8s-cert.sh

cat > ca-config.json <<EOF
{
  "signing": {
    "default": {
      "expiry": "87600h"
    },
    "profiles": {
      "kubernetes": {
         "expiry": "87600h",
         "usages": [
            "signing",
            "key encipherment",
            "server auth",
            "client auth"
        ]
      }
    }
  }
}
EOF

cat > ca-csr.json <<EOF
{
    "CN": "kubernetes",
    "key": {
        "algo": "rsa",
        "size": 2048
    },
    "names": [
        {
            "C": "CN",
            "L": "Beijing",
            "ST": "Beijing",
            "O": "k8s",
            "OU": "System"
        }
    ]
}
EOF

cfssl gencert -initca ca-csr.json | cfssljson -bare ca -

#-----------------------

cat > server-csr.json <<EOF
{
    "CN": "kubernetes",
    "hosts": [
      "10.0.0.1",
      "127.0.0.1",
      "192.168.241.130",
      "192.168.241.131",
      "192.168.241.132",
      "192.168.241.133",
      "192.168.241.134",
      "192.168.241.135",
      "kubernetes",
      "kubernetes.default",
      "kubernetes.default.svc",
      "kubernetes.default.svc.cluster",
      "kubernetes.default.svc.cluster.local"
    ],
    "key": {
        "algo": "rsa",
        "size": 2048
    },
    "names": [
        {
            "C": "CN",
            "L": "BeiJing",
            "ST": "BeiJing",
            "O": "k8s",
            "OU": "System"
        }
    ]
}
EOF

cfssl gencert -ca=ca.pem -ca-key=ca-key.pem -config=ca-config.json -profile=kubernetes server-csr.json | cfssljson -bare server

#-----------------------

cat > admin-csr.json <<EOF
{
  "CN": "admin",
  "hosts": [],
  "key": {
    "algo": "rsa",
    "size": 2048
  },
  "names": [
    {
      "C": "CN",
      "L": "BeiJing",
      "ST": "BeiJing",
      "O": "system:masters",
      "OU": "System"
    }
  ]
}
EOF

cfssl gencert -ca=ca.pem -ca-key=ca-key.pem -config=ca-config.json -profile=kubernetes admin-csr.json | cfssljson -bare admin

#-----------------------

cat > kube-proxy-csr.json <<EOF
{
  "CN": "system:kube-proxy",
  "hosts": [],
  "key": {
    "algo": "rsa",
    "size": 2048
  },
  "names": [
    {
      "C": "CN",
      "L": "BeiJing",
      "ST": "BeiJing",
      "O": "k8s",
      "OU": "System"
    }
  ]
}
EOF

cfssl gencert -ca=ca.pem -ca-key=ca-key.pem -config=ca-config.json -profile=kubernetes kube-proxy-csr.json | cfssljson -bare kube-pro
xy

執(zhí)行腳本生成證書和文件

[root@master k8s-cert]# bahs k8s-cert.sh

將生成的證書拷貝到k8s工作目錄下

[root@master k8s-cert]# cp ca.pem ca-key.pem server.pem server-key.pem /opt/kubernetes/ssl/

接下來生成token文件

BOOTSTRAP_TOKEN=$(head -c 16 /dev/urandom | od -An -t -x | tr -d ' ')  //官方生成token命令

我使用已經(jīng)生成的
[root@master k8s-cert]# BOOTSTRAP_TOKEN=0fb61c46f8991b718eb38d27b605b008
[root@master k8s-cert]#  cat > token.csv <<EOF
>${BOOTSTRAP_TOKEN},,kubelet-bootstrap,10001,"system:kubelet-bootstrap"
>EOF
將生成的token.sh文件放到k8s工作目錄下
[root@master k8s-cert]# mv token.sh /opt/kubernetes/cfg

啟動kube-apiserver

[root@master ~]#  systemctl start kube-apiserver

注意：如果apiserver啟動失敗 可以進(jìn)行如下操作排查

[root@master ~]# source /opt/kubernetes/cfg/kube-apiserver 
[root@master ~]# /opt/kubernetes/bin/kube-apiserver $KUBE_APISERVER_OPTS

部署kube-controller-manage
編寫腳本

[root@master k8s]# vim controller-manager.sh

#!/bin/bash

MASTER_ADDRESS=$1

cat <<EOF >/opt/kubernetes/cfg/kube-controller-manager


KUBE_CONTROLLER_MANAGER_OPTS="--logtostderr=true \\
--v=4 \\
--master=${MASTER_ADDRESS}:8080 \\
--leader-elect=true \\
--address=127.0.0.1 \\
--service-cluster-ip-range=10.0.0.0/24 \\
--cluster-name=kubernetes \\
--cluster-signing-cert-file=/opt/kubernetes/ssl/ca.pem \\
--cluster-signing-key-file=/opt/kubernetes/ssl/ca-key.pem  \\
--root-ca-file=/opt/kubernetes/ssl/ca.pem \\
--service-account-private-key-file=/opt/kubernetes/ssl/ca-key.pem \\
--experimental-cluster-signing-duration=87600h0m0s"

EOF

cat <<EOF >/usr/lib/systemd/system/kube-controller-manager.service
[Unit]
Description=Kubernetes Controller Manager
Documentation=https://github.com/kubernetes/kubernetes

[Service]
EnvironmentFile=-/opt/kubernetes/cfg/kube-controller-manager
ExecStart=/opt/kubernetes/bin/kube-controller-manager \$KUBE_CONTROLLER_MANAGER_OPTS
Restart=on-failure

[Install]
WantedBy=multi-user.target
EOF

systemctl daemon-reload
systemctl enable kube-controller-manager
systemctl restart kube-controller-manager

執(zhí)行腳本 只需要指定本地ip就行

[root@master k8s]# ./controller-manager.sh 127.0.0.1

部署kube-scheduler
編寫腳本

[root@master k8s]# vim scheduler.sh 
#!/bin/bash
MASTER_ADDRESS=$1

cat <<EOF >/opt/kubernetes/cfg/kube-scheduler

KUBE_SCHEDULER_OPTS="--logtostderr=true \\
--v=4 \\
--master=${MASTER_ADDRESS}:8080 \\
--leader-elect"

EOF

cat <<EOF >/usr/lib/systemd/system/kube-scheduler.service
[Unit]
Description=Kubernetes Scheduler
Documentation=https://github.com/kubernetes/kubernetes

[Service]
EnvironmentFile=-/opt/kubernetes/cfg/kube-scheduler
ExecStart=/opt/kubernetes/bin/kube-scheduler \$KUBE_SCHEDULER_OPTS
Restart=on-failure

[Install]
WantedBy=multi-user.target
EOF

systemctl daemon-reload
systemctl enable kube-scheduler
systemctl restart kube-scheduler

執(zhí)行腳本 只需要指定本地ip就行

[root@master k8s]# ./scheduler.sh 127.0.0.1

拷貝文件到/usr/bin/下

[root@master ~]# cp /root/soft/kubernetes/server/bin/kubectl /usr/bin/  //可以使用kubectl工具管理了
查看集群狀態(tài)
[root@master ~]# kubectl get cs
NAME                 STATUS    MESSAGE             ERROR
scheduler            Healthy   ok                  
controller-manager   Healthy   ok                  
etcd-0               Healthy   {"health":"true"}   
etcd-2               Healthy   {"health":"true"}   
etcd-1               Healthy   {"health":"true"}   

[root@master ~]# kubectl api-resources //可以查看所有縮寫字母的全拼

將kubelet-bootstrap用戶綁定到系統(tǒng)集群角色

[root@master ~]# kubectl create clusterrolebinding kubelet-bootstrap --clusterrole=system:node-bootstrapper --user=kubelet-bootstrap
主要是為kubelet頒發(fā)證書用的最小權(quán)限

開始部署node組件

創(chuàng)建kubeconfig文件
編寫kubeconfig腳本

[root@master k8s-cert]# vim kubeconfig.sh 
APISERVER=$1
SSL_DIR=$2
BOOTSTRAP_TOKEN=0fb61c46f8991b718eb38d27b605b008
# 創(chuàng)建kubelet bootstrapping kubeconfig 
export KUBE_APISERVER="https://$APISERVER:6443"

# 設(shè)置集群參數(shù)
kubectl config set-cluster kubernetes \
  --certificate-authority=$SSL_DIR/ca.pem \
  --embed-certs=true \
  --server=${KUBE_APISERVER} \
  --kubeconfig=bootstrap.kubeconfig

# 設(shè)置客戶端認(rèn)證參數(shù)
kubectl config set-credentials kubelet-bootstrap \
  --token=${BOOTSTRAP_TOKEN} \
  --kubeconfig=bootstrap.kubeconfig

# 設(shè)置上下文參數(shù)
kubectl config set-context default \
  --cluster=kubernetes \
  --user=kubelet-bootstrap \
  --kubeconfig=bootstrap.kubeconfig

# 設(shè)置默認(rèn)上下文
kubectl config use-context default --kubeconfig=bootstrap.kubeconfig

#----------------------
# 創(chuàng)建kube-proxy kubeconfig文件

kubectl config set-cluster kubernetes \
  --certificate-authority=$SSL_DIR/ca.pem \
  --embed-certs=true \
  --server=${KUBE_APISERVER} \
  --kubeconfig=kube-proxy.kubeconfig

kubectl config set-credentials kube-proxy \
  --client-certificate=$SSL_DIR/kube-proxy.pem \
  --client-key=$SSL_DIR/kube-proxy-key.pem \
  --embed-certs=true \
  --kubeconfig=kube-proxy.kubeconfig

kubectl config set-context default \
  --cluster=kubernetes \
  --user=kube-proxy \
  --kubeconfig=kube-proxy.kubeconfig

kubectl config use-context default --kubeconfig=kube-proxy.kubeconfig

執(zhí)行腳本

[root@master k8s-cert]# bash kubeconfig.sh 192.168.241.130 /root/k8s/k8s-cert/

將生成的文件拷貝到node節(jié)點(diǎn)上

[root@master k8s-cert]# scp bootstrap.kubeconfig kube-proxy.kubeconfig node1:/opt/kubernetes/cfg/
[root@master k8s-cert]# scp bootstrap.kubeconfig kube-proxy.kubeconfig node2:/opt/kubernetes/cfg/

部署kubelet ，kube-proxy組件 在node上執(zhí)行
編寫kubelet腳本

[root@slave1 ~]# vim kubelet.sh 
#!/bin/bash

NODE_ADDRESS=$1
DNS_SERVER_IP=${2:-"10.0.0.2"}

cat <<EOF >/opt/kubernetes/cfg/kubelet

KUBELET_OPTS="--logtostderr=true \\
--v=4 \\
--address=${NODE_ADDRESS} \\
--hostname-override=${NODE_ADDRESS} \\
--kubeconfig=/opt/kubernetes/cfg/kubelet.kubeconfig \\
--experimental-bootstrap-kubeconfig=/opt/kubernetes/cfg/bootstrap.kubeconfig \\
--config=/opt/kubernetes/cfg/kubelet.config \\
--cert-dir=/opt/kubernetes/ssl \\
--pod-infra-container-image=registry.cn-hangzhou.aliyuncs.com/google-containers/pause-amd64:3.0"

EOF
cat <<EOF >/opt/kubernetes/cfg/kubelet.config

kind: KubeletConfiguration
apiVersion: kubelet.config.k8s.io/v1beta1
address: ${NODE_ADDRESS}
port: 10250
cgroupDriver: cgroupfs
clusterDNS:
- ${DNS_SERVER_IP} 
clusterDomain: cluster.local.
failSwapOn: false

EOF
cat <<EOF >/usr/lib/systemd/system/kubelet.service
[Unit]
Description=Kubernetes Kubelet
After=docker.service
Requires=docker.service

[Service]
EnvironmentFile=/opt/kubernetes/cfg/kubelet
ExecStart=/opt/kubernetes/bin/kubelet \$KUBELET_OPTS
Restart=on-failure
KillMode=process

[Install]
WantedBy=multi-user.target
EOF

systemctl daemon-reload
systemctl enable kubelet
systemctl restart kubelet

執(zhí)行腳本

[root@slave1 ~]# bash kubelet.sh 192.168.241.131

把master上解壓出來的kubernetes中的文件拷貝到node節(jié)點(diǎn)

[root@master bin]# scp /root/soft/kubernetes/server/bin/kubelet  kube-proxy node1:/opt/kubernetes/bin/

啟動kubelet

[root@slave1 ~]# systemctl start kubelet

如報(bào)以下錯(cuò)誤

error: failed to run Kubelet: cannot create certificate signing request: certificatesigningrequests.certificates.k8s.io is forbidden: User "kubelet-bootstrap" cannot create certificatesigningrequests.certificates.k8s.io at the cluster scope

原因是：kubelet-bootstrap并沒有權(quán)限創(chuàng)建證書。所以要?jiǎng)?chuàng)建這個(gè)用戶的權(quán)限并綁定到這個(gè)角色上。

解決方法是在master上執(zhí)行kubectl create clusterrolebinding kubelet-bootstrap --clusterrole=system:node-bootstrapper --user=kubelet-bootstrap
————————————————
版權(quán)聲明：本文為CSDN博主「lyzkks」的原創(chuàng)文章，遵循 CC 4.0 BY-SA 版權(quán)協(xié)議，轉(zhuǎn)載請附上原文出處鏈接及本聲明。
原文鏈接：https://blog.csdn.net/sinat_35930259/article/details/79946298
基本上都是證書問題  要細(xì)心

查看kubelet的請求(master執(zhí)行)

[root@master ~]# kubectl get csr

執(zhí)行以下命令使node節(jié)點(diǎn)加入集群中

[root@master ~]# kubectl certificate approve node-csr-c9xfnyCf7Vz1owhwI4yR5knoAxSKA8tNq-gB4C6KAtQ
查看集群
[root@master ~]# kubectl get no
NAME              STATUS   ROLES    AGE    VERSION
192.168.241.131   Ready    <none>   170m   v1.12.1

部署kube-proxy
編寫kube-proxy腳本

[root@slave1 ~]# vim proxy.sh 
#!/bin/bash

NODE_ADDRESS=$1

cat <<EOF >/opt/kubernetes/cfg/kube-proxy

KUBE_PROXY_OPTS="--logtostderr=true \\
--v=4 \\
--hostname-override=${NODE_ADDRESS} \\
--cluster-cidr=10.0.0.0/24 \\
--proxy-mode=ipvs \\
--kubeconfig=/opt/kubernetes/cfg/kube-proxy.kubeconfig"

EOF

cat <<EOF >/usr/lib/systemd/system/kube-proxy.service
[Unit]
Description=Kubernetes Proxy
After=network.target

[Service]
EnvironmentFile=-/opt/kubernetes/cfg/kube-proxy
ExecStart=/opt/kubernetes/bin/kube-proxy \$KUBE_PROXY_OPTS
Restart=on-failure

[Install]
WantedBy=multi-user.target
EOF
systemctl daemon-reload
systemctl enable kube-proxy
systemctl restart kube-proxy

執(zhí)行腳本

[root@slave1 ~]# bash proxy.sh 192.168.241.131
查看狀態(tài)
[root@slave1 ~]# ps -ef |grep proxy
root      17178      1  0 14:42 ?        00:01:00 /opt/kubernetes/bin/kube-proxy --logtostderr=true --v=4 --hostname-override=192.168.241.131 --cluster-cidr=10.0.0.0/24 --proxy-mode=ipvs --kubeconfig=/opt/kubernetes/cfg/kube-proxy.kubeconfig
root      44837  13942  0 17:26 pts/1    00:00:00 grep --color=auto proxy

node1創(chuàng)建完成，接下來部署node2.只需要拷貝文件改ip就行

[root@slave1 ~]#   scp -r /opt/kubernetes node2:/opt/
[root@slave1 ~]#   scp /usr/lib/systemd/system/{kubelet,kube-proxy}.service node2:/usr/lib/systemd/system/

修改配置文件(node2執(zhí)行)

[root@slave2 ssl]#  rm -rf /opt/kubernetes/ssl
修改文件(把ip改成node2ip)
[root@slave2 cfg]#  /opt/kubernetes/cfg/kubelet
[root@slave2 cfg]#  /opt/kubernetes/cfg/kubelet.config 
[root@slave2 cfg]# vim  /opt/kubernetes/cfg/kube-proxy

啟動(node2)

[root@slave2 cfg]# systemctl start kubelet
到master節(jié)點(diǎn)執(zhí)行kubectl get csr查看請求
執(zhí)行命令加入集群
[root@master ~]#  kubectl certificate approve node-csr-aC8xr_qDkBseE1rmAcT1YS40jxsnhpALkZRCQ_Yj_UY

在master查看集群狀態(tài)

[root@master ~]# kubectl get no
NAME              STATUS   ROLES    AGE    VERSION
192.168.241.131   Ready    <none>   3h5m   v1.12.1
192.168.241.132   Ready    <none>   166m   v1.12.1

以上二進(jìn)制部署k8s一主雙從搭建完成

問題排錯(cuò)

問題1
#####使用kubectl不能查看日志顯示以下錯(cuò)誤時(shí)
報(bào)錯(cuò)信息
[root@master yaml]# kubectl -n kube-system logs -f kubernetes-dashboard-fdccbc96-r5srr 
error: You must be logged in to the server (the server has asked for the client to provide credentials ( pods/log kubernetes-dashboard-fdccbc96-r5srr))

解決方法
到node節(jié)點(diǎn)修改kubelet.config文件內(nèi)容
------------------在文件末尾添加，認(rèn)證確認(rèn)
authentication:
  anonymous:
    enabled: true
----------------
# 然后重啟kubelet
systemctl restart kubelet
如果還沒有生效，就在master節(jié)點(diǎn)上重啟kube-apiserver
問題2
如題，部分容器可以進(jìn)入 但是部分容器會有如下錯(cuò)誤
kubectl exec traefik-ingress-controller-6gh2g -i -t -n kube-system -- /bin/bash
OCI runtime exec failed: exec failed: container_linux.go:348: starting container process caused "exec: \"/bin/bash\": stat /bin/bash: no such file or directory": unknown
command terminated with exit code 126

解決方法
你有沒有想過traefik-ingress-controller-6gh2g這樣一個(gè)問題。1.該容器使用的不支持/bin/bash，只有/bin/sh ,或者壓根都沒有提供這種shell接口！
最后編輯于 ：
?著作權(quán)歸作者所有,轉(zhuǎn)載或內(nèi)容合作請聯(lián)系作者
【社區(qū)內(nèi)容提示】社區(qū)部分內(nèi)容疑似由AI輔助生成，瀏覽時(shí)請結(jié)合常識與多方信息審慎甄別。
平臺聲明：文章內(nèi)容（如有圖片或視頻亦包括在內(nèi)）由作者上傳并發(fā)布，文章內(nèi)容僅代表作者本人觀點(diǎn)，簡書系信息發(fā)布平臺，僅提供信息存儲服務(wù)。

相關(guān)閱讀更多精彩內(nèi)容

友情鏈接更多精彩內(nèi)容