kubernetes 1.7.2 + Calico部署

最新推荐文章于 2024-08-23 13:56:31 发布
最新推荐文章于 2024-08-23 13:56:31 发布
阅读量1.6k 收藏 1
点赞数
分类专栏： kubetnetes 文章标签： k8s
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/qq_21816375/article/details/79841776
版权

系统环境

系统

[root@kubernetes-master-1 ~]# cat /etc/redhat-release 
CentOS Linux release 7.4.1708 (Core)

hosts 

[root@kubernetes-master-1 ~]# cat /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.1.109 kubernetes-master-1
192.168.1.110 kubernetes-master-2
192.168.1.111 k8s-node-1

创建 验证

安装 cfssl

mkdir -p /opt/local/cfssl

cd /opt/local/cfssl

wget https://pkg.cfssl.org/R1.2/cfssl_linux-amd64
mv cfssl_linux-amd64 cfssl

wget https://pkg.cfssl.org/R1.2/cfssljson_linux-amd64
mv cfssljson_linux-amd64 cfssljson

wget https://pkg.cfssl.org/R1.2/cfssl-certinfo_linux-amd64
mv cfssl-certinfo_linux-amd64 cfssl-certinfo

chmod +x *

ls -l
总用量 18808
-rwxr-xr-x 1 root root 10376657 3月  30 2016 cfssl
-rwxr-xr-x 1 root root  6595195 3月  30 2016 cfssl-certinfo
-rwxr-xr-x 1 root root  2277873 3月  30 2016 cfssljson

创建 CA 证书配置

mkdir /opt/ssl

cd /opt/ssl

/opt/local/cfssl/cfssl print-defaults config > config.json

/opt/local/cfssl/cfssl print-defaults csr > csr.json

[root@k8s-node-1 ssl]# cat config.json csr.json 
{
  "signing": {
    "default": {
      "expiry": "87600h"
    },
    "profiles": {
      "kubernetes": {
        "usages": [
            "signing",
            "key encipherment",
            "server auth",
            "client auth"
        ],
        "expiry": "87600h"
      }
    }
  }
}
{
  "CN": "kubernetes",
  "key": {
    "algo": "rsa",
    "size": 2048
  },
  "names": [
    {
      "C": "CN",
      "ST": "ShenZhen",
      "L": "ShenZhen",
      "O": "k8s",
      "OU": "System"
    }
  ]
}

生成 CA 证书和私钥

cd /opt/ssl/

/opt/local/cfssl/cfssl gencert -initca csr.json | /opt/local/cfssl/cfssljson -bare ca

[root@k8s-node-1 ssl]# ls -l
总用量 20
-rw-r--r-- 1 root root 1005 4月   7 15:29 ca.csr
-rw------- 1 root root 1675 4月   7 15:29 ca-key.pem
-rw-r--r-- 1 root root 1363 4月   7 15:29 ca.pem
-rw-r--r-- 1 root root  292 4月   7 15:27 config.json
-rw-r--r-- 1 root root  210 4月   7 15:27 csr.json

分发证书

# 创建证书目录
mkdir -p /etc/kubernetes/ssl

# 拷贝所有文件到目录下
cp * /etc/kubernetes/ssl

# 这里要将文件拷贝到所有的k8s 机器上,也要创建相应的目录

scp * root@192.168.1.110:/etc/kubernetes/ssl/

scp * root@192.168.1.111:/etc/kubernetes/ssl/

etcd 集群

yum install etcd3 -y

创建 etcd 证书

cd /opt/ssl/

[root@kubernetes-master-1 ssl]# vi etcd-csr.json

{
  "CN": "etcd",
  "hosts": [
    "127.0.0.1",
    "192.168.1.109",
    "192.168.1.110",
    "192.168.1.111"
  ],
  "key": {
    "algo": "rsa",
    "size": 2048
  },
  "names": [
    {
      "C": "CN",
      "ST": "ShenZhen",
      "L": "ShenZhen",
      "O": "k8s",
      "OU": "System"
    }
  ]
}


# 生成 etcd   密钥

/opt/local/cfssl/cfssl gencert -ca=/opt/ssl/ca.pem \
  -ca-key=/opt/ssl/ca-key.pem \
  -config=/opt/ssl/config.json \
  -profile=kubernetes etcd-csr.json | /opt/local/cfssl/cfssljson -bare etcd
# 查看生成

[root@k8s-node-1 ssl]# ls -l etcd*
-rw-r--r-- 1 root root 1066 4月   7 15:38 etcd.csr
-rw-r--r-- 1 root root  301 4月   7 15:37 etcd-csr.json
-rw------- 1 root root 1675 4月   7 15:38 etcd-key.pem
-rw-r--r-- 1 root root 1440 4月   7 15:38 etcd.pem



# 拷贝到etcd服务器

# etcd-1 
cp etcd*.pem /etc/kubernetes/ssl/

# etcd-2
scp etcd* root@192.168.1.110:/etc/kubernetes/ssl/

# etcd-3
scp etcd* root@192.168.1.111:/etc/kubernetes/ssl/



# 如果 etcd 非 root 用户，读取证书会提示没权限

chmod 644 /etc/kubernetes/ssl/etcd-key.pem

修改 etcd 配置

# etcd-1


vi /usr/lib/systemd/system/etcd.service

[Unit]
Description=Etcd Server
After=network.target
After=network-online.target
Wants=network-online.target

[Service]
Type=notify
WorkingDirectory=/var/lib/etcd/
User=etcd
# set GOMAXPROCS to number of processors
ExecStart=/usr/bin/etcd \
  --name=etcd1 \
  --cert-file=/etc/kubernetes/ssl/etcd.pem \
  --key-file=/etc/kubernetes/ssl/etcd-key.pem \
  --peer-cert-file=/etc/kubernetes/ssl/etcd.pem \
  --peer-key-file=/etc/kubernetes/ssl/etcd-key.pem \
  --trusted-ca-file=/etc/kubernetes/ssl/ca.pem \
  --peer-trusted-ca-file=/etc/kubernetes/ssl/ca.pem \
  --initial-advertise-peer-urls=https://192.168.1.109:2380 \
  --listen-peer-urls=https://192.168.1.109:2380 \
  --listen-client-urls=https://192.168.1.109:2379,http://127.0.0.1:2379 \
  --advertise-client-urls=https://192.168.1.109:2379 \
  --initial-cluster-token=k8s-etcd-cluster \
  --initial-cluster=etcd1=https://192.168.1.109:2380,etcd2=https://192.168.1.110:2380,etcd3=https://192.168.1.111:2380 \
  --initial-cluster-state=new \
  --data-dir=/var/lib/etcd
Restart=on-failure
RestartSec=5
LimitNOFILE=65536

[Install]
WantedBy=multi-user.target

# etcd-2


vi /usr/lib/systemd/system/etcd.service


[Unit]
Description=Etcd Server
After=network.target
After=network-online.target
Wants=network-online.target

[Service]
Type=notify
WorkingDirectory=/var/lib/etcd/
User=etcd
# set GOMAXPROCS to number of processors
ExecStart=/usr/bin/etcd \
  --name=etcd2 \
  --cert-file=/etc/kubernetes/ssl/etcd.pem \
  --key-file=/etc/kubernetes/ssl/etcd-key.pem \
  --peer-cert-file=/etc/kubernetes/ssl/etcd.pem \
  --peer-key-file=/etc/kubernetes/ssl/etcd-key.pem \
  --trusted-ca-file=/etc/kubernetes/ssl/ca.pem \
  --peer-trusted-ca-file=/etc/kubernetes/ssl/ca.pem \
  --initial-advertise-peer-urls=https://192.168.1.110:2380 \
  --listen-peer-urls=https://192.168.1.110:2380 \
  --listen-client-urls=https://192.168.1.110:2379,http://127.0.0.1:2379 \
  --advertise-client-urls=https://192.168.1.110:2379 \
  --initial-cluster-token=k8s-etcd-cluster \
  --initial-cluster=etcd1=https://192.168.1.109:2380,etcd2=https://192.168.1.110:2380,etcd3=https://192.168.1.111:2380 \
  --initial-cluster-state=new \
  --data-dir=/var/lib/etcd
Restart=on-failure
RestartSec=5
LimitNOFILE=65536

[Install]
WantedBy=multi-user.target
# etcd-3

vi /usr/lib/systemd/system/etcd.service

[Unit]
Description=Etcd Server
After=network.target
After=network-online.target
Wants=network-online.target

[Service]
Type=notify
WorkingDirectory=/var/lib/etcd/
User=etcd
# set GOMAXPROCS to number of processors
ExecStart=/usr/bin/etcd \
  --name=etcd3 \
  --cert-file=/etc/kubernetes/ssl/etcd.pem \
  --key-file=/etc/kubernetes/ssl/etcd-key.pem \
  --peer-cert-file=/etc/kubernetes/ssl/etcd.pem \
  --peer-key-file=/etc/kubernetes/ssl/etcd-key.pem \
  --trusted-ca-file=/etc/kubernetes/ssl/ca.pem \
  --peer-trusted-ca-file=/etc/kubernetes/ssl/ca.pem \
  --initial-advertise-peer-urls=https://192.168.1.111:2380 \
  --listen-peer-urls=https://192.168.1.111:2380 \
  --listen-client-urls=https://192.168.1.111:2379,http://127.0.0.1:2379 \
  --advertise-client-urls=https://192.168.1.111:2379 \
  --initial-cluster-token=k8s-etcd-cluster \
  --initial-cluster=etcd1=https://192.168.1.109:2380,etcd2=https://192.168.1.110:2380,etcd3=https://192.168.1.111:2380 \
  --initial-cluster-state=new \
  --data-dir=/var/lib/etcd
Restart=on-failure
RestartSec=5
LimitNOFILE=65536

[Install]
WantedBy=multi-user.target

启动 etcd

在每个节点执行

systemctl enable etcd

systemctl start etcd

systemctl status etcd

# 如果报错 请使用
journalctl -f -t etcd  和 journalctl -u etcd 来定位问题

验证 etcd 集群状态
查看 etcd 集群状态：

etcdctl --endpoints=https://192.168.1.110:2379 \
        --cert-file=/etc/kubernetes/ssl/etcd.pem \
        --ca-file=/etc/kubernetes/ssl/ca.pem \
        --key-file=/etc/kubernetes/ssl/etcd-key.pem \
        cluster-health

member 69fb6a35f1ce3d83 is healthy: got healthy result from https://192.168.1.109:2379
member 95605c07b7eb732b is healthy: got healthy result from https://192.168.1.111:2379
member fdb0d4304dcee33c is healthy: got healthy result from https://192.168.1.110:2379
cluster is healthy

查看 etcd 集群成员

etcdctl --endpoints=https://192.168.1.110:2379 \
        --cert-file=/etc/kubernetes/ssl/etcd.pem \
        --ca-file=/etc/kubernetes/ssl/ca.pem \
        --key-file=/etc/kubernetes/ssl/etcd-key.pem \
        member list

69fb6a35f1ce3d83: name=etcd1 peerURLs=https://192.168.1.109:2380 clientURLs=https://192.168.1.109:2379 isLeader=true
95605c07b7eb732b: name=etcd3 peerURLs=https://192.168.1.111:2380 clientURLs=https://192.168.1.111:2379 isLeader=false
fdb0d4304dcee33c: name=etcd2 peerURLs=https://192.168.1.110:2380 clientURLs=https://192.168.1.110:2379 isLeader=false

安装 docker

# 导入 yum 源

# 安装 yum-config-manager

yum -y install yum-utils

# 导入
yum-config-manager \
    --add-repo \
    https://download.docker.com/linux/centos/docker-ce.repo


# 更新 repo
yum makecache

# 安装

yum install docker-ce

添加dockerhub加速器

[root@kubernetes-master-1 ~]# cat /etc/docker/daemon.json 
{"registry-mirrors": ["http://579fe187.m.daocloud.io","https://pee6w651.mirror.aliyuncs.com"]}

启动docker

systemctl daemon-reload
systemctl start docker
systemctl enable docker

安装 kubectl 工具

Master 端

# 首先安装 kubectl

wget https://dl.k8s.io/v1.7.2/kubernetes-client-linux-amd64.tar.gz

tar -xzvf kubernetes-client-linux-amd64.tar.gz

cp kubernetes/client/bin/* /usr/local/bin/

chmod a+x /usr/local/bin/kube*


# 验证安装

kubectl version
[root@kubernetes-master-1 ~]# kubectl version
Client Version: version.Info{Major:"1", Minor:"7", GitVersion:"v1.7.2", GitCommit:"922a86cfcd65915a9b2f69f3f193b8907d741d9c", GitTreeState:"clean", BuildDate:"2017-07-21T08:23:22Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}

创建 admin 证书

cd /opt/ssl/

vi admin-csr.json
{
  "CN": "admin",
  "hosts": [],
  "key": {
    "algo": "rsa",
    "size": 2048
  },
  "names": [
    {
      "C": "CN",
      "ST": "ShenZhen",
      "L": "ShenZhen",
      "O": "system:masters",
      "OU": "System"
    }
  ]
}
# 生成 admin 证书和私钥
cd /opt/ssl/

/opt/local/cfssl/cfssl gencert -ca=/etc/kubernetes/ssl/ca.pem \
  -ca-key=/etc/kubernetes/ssl/ca-key.pem \
  -config=/etc/kubernetes/ssl/config.json \
  -profile=kubernetes admin-csr.json | /opt/local/cfssl/cfssljson -bare admin


# 查看生成

[root@k8s-master-1 ssl]# ls admin*
admin.csr  admin-csr.json  admin-key.pem  admin.pem

cp admin*.pem /etc/kubernetes/ssl/

scp admin*.pem root@192.168.1.110:/etc/kubernetes/ssl/
scp admin*.pem root@192.168.1.111:/etc/kubernetes/ssl/

配置 kubectl kubeconfig 文件

# 配置 kubernetes 集群

kubectl config set-cluster kubernetes \
  --certificate-authority=/etc/kubernetes/ssl/ca.pem \
  --embed-certs=true \
  --server=https://192.168.1.109:6443


# 配置 客户端认证

kubectl config set-credentials admin \
  --client-certificate=/etc/kubernetes/ssl/admin.pem \
  --embed-certs=true \
  --client-key=/etc/kubernetes/ssl/admin-key.pem



kubectl config set-context kubernetes \
  --cluster=kubernetes \
  --user=admin


kubectl config use-context kubernetes

分发 kubectl config 文件

# 将上面配置的 kubeconfig 文件分发到其他机器

# 其他服务器创建目录

mkdir /root/.kube //在其他节点也要创建该目录

scp /root/.kube/config root@192.168.1.110:/root/.kube/

scp /root/.kube/config root@192.168.1.111:/root/.kube/

部署 kubernetes Master 节点

Master 需要部署 kube-apiserver , kube-scheduler , kube-controller-manager 这三个组件

安装组件

# 从github 上下载版本

cd /tmp

wget https://dl.k8s.io/v1.7.2/kubernetes-server-linux-amd64.tar.gz

tar -xzvf kubernetes-server-linux-amd64.tar.gz

cd kubernetes

cp -r server/bin/{kube-apiserver,kube-controller-manager,kube-scheduler,kubectl,kube-proxy,kubelet} /usr/local/bin/

创建 kubernetes 证书

cd /opt/ssl

vi kubernetes-csr.json

{
  "CN": "kubernetes",
  "hosts": [
    "127.0.0.1",
    "192.168.1.109",
    "192.168.1.110",
    "192.254.0.1",
    "kubernetes",
    "kubernetes.default",
    "kubernetes.default.svc",
    "kubernetes.default.svc.cluster",
    "kubernetes.default.svc.cluster.local"
  ],
  "key": {
    "algo": "rsa",
    "size": 2048
  },
  "names": [
    {
      "C": "CN",
      "ST": "ShenZhen",
      "L": "ShenZhen",
      "O": "k8s",
      "OU": "System"
    }
  ]
}


## 这里 hosts 字段中 三个 IP 分别为 127.0.0.1 本机， 192.168.1.109, 192.168.1.111 为 Master 的IP， 192.254.0.1 为 kubernetes SVC 的 IP， 一般是 部署网络的第一个IP , 如: 192.254.0.1 ， 在启动完成后，我们使用   kubectl get svc ， 就可以查看到

生成 kubernetes 证书和私钥

/opt/local/cfssl/cfssl gencert -ca=/etc/kubernetes/ssl/ca.pem \
  -ca-key=/etc/kubernetes/ssl/ca-key.pem \
  -config=/etc/kubernetes/ssl/config.json \
  -profile=kubernetes kubernetes-csr.json | /opt/local/cfssl/cfssljson -bare kubernetes

# 查看生成

[root@k8s-node-1 ssl]# ls -lt kubernetes*
-rw-r--r-- 1 root root 1253 4月   7 16:57 kubernetes.csr
-rw------- 1 root root 1679 4月   7 16:57 kubernetes-key.pem
-rw-r--r-- 1 root root 1627 4月   7 16:57 kubernetes.pem
-rw-r--r-- 1 root root  461 4月   7 16:56 kubernetes-csr.json


# 拷贝到目录
cp -r kubernetes* /etc/kubernetes/ssl/
scp kubernetes* root@192.168.1.110:/etc/kubernetes/ssl/
scp kubernetes* root@192.168.1.111:/etc/kubernetes/ssl/

配置 kube-apiserver

kubelet 首次启动时向 kube-apiserver 发送 TLS Bootstrapping 请求，kube-apiserver 验证 kubelet 请求中的 token 是否与它配置的 token 一致，如果一致则自动为 kubelet生成证书和秘钥。

# 生成 token

[root@k8s-node-1 ssl]# head -c 16 /dev/urandom | od -An -t x | tr -d ' '
cdc7201eb10d76842ff5b6e35bfbb516


# 创建 token.csv 文件

cd /opt/ssl

vi token.csv

cdc7201eb10d76842ff5b6e35bfbb516,kubelet-bootstrap,10001,"system:kubelet-bootstrap"


# 拷贝

cp token.csv /etc/kubernetes/
scp token.csv root@192.168.1.110:/etc/kubernetes/
scp token.csv root@192.168.1.111:/etc/kubernetes/

创建 kube-apiserver.service 文件

# 自定义 系统 service 文件一般存于 /etc/systemd/system/ 下

vi /etc/systemd/system/kube-apiserver.service

[Unit]
Description=kubernetes API Server
Documentation=https://github.com/GoogleCloudPlatform/kubernetes
After=network.target

[Service]
User=root
ExecStart=/usr/local/bin/kube-apiserver \
  --admission-control=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,ResourceQuota \
  --advertise-address=192.168.1.109 \
  --allow-privileged=true \
  --apiserver-count=3 \
  --audit-log-maxage=30 \
  --audit-log-maxbackup=3 \
  --audit-log-maxsize=100 \
  --audit-log-path=/var/lib/audit.log \
  --authorization-mode=RBAC \
  --bind-address=192.168.1.109 \
  --client-ca-file=/etc/kubernetes/ssl/ca.pem \
  --enable-swagger-ui=true \
  --etcd-cafile=/etc/kubernetes/ssl/ca.pem \
  --etcd-certfile=/etc/kubernetes/ssl/etcd.pem \
  --etcd-keyfile=/etc/kubernetes/ssl/etcd-key.pem \
  --etcd-servers=https://192.168.1.109:2379,https://192.168.1.110:2379,https://192.168.1.111:2379 \
  --event-ttl=1h \
  --kubelet-https=true \
  --insecure-bind-address=192.168.1.109 \
  --runtime-config=rbac.authorization.k8s.io/v1alpha1 \
  --service-account-key-file=/etc/kubernetes/ssl/ca-key.pem \
  --service-cluster-ip-range=192.254.0.0/16 \
  --service-node-port-range=30000-32000 \
  --tls-cert-file=/etc/kubernetes/ssl/kubernetes.pem \
  --tls-private-key-file=/etc/kubernetes/ssl/kubernetes-key.pem \
  --experimental-bootstrap-token-auth \
  --token-auth-file=/etc/kubernetes/token.csv \
  --v=2
Restart=on-failure
RestartSec=5
Type=notify
LimitNOFILE=65536

[Install]
WantedBy=multi-user.target
# 这里面要注意的是 --service-node-port-range=30000-32000
# 这个地方是 映射外部端口时 的端口范围，随机映射也在这个范围内映射，指定映射端口必须也在这个范围内。

启动 kube-apiserver

systemctl daemon-reload
systemctl enable kube-apiserver
systemctl start kube-apiserver
systemctl status kube-apiserver

配置 kube-controller-manager

# 创建 kube-controller-manager.service 文件

vi /etc/systemd/system/kube-controller-manager.service


[Unit]
Description=kubernetes Controller Manager
Documentation=https://github.com/GoogleCloudPlatform/kubernetes

[Service]
ExecStart=/usr/local/bin/kube-controller-manager \
  --address=127.0.0.1 \
  --master=http://192.168.1.109:8080 \
  --allocate-node-cidrs=true \
  --service-cluster-ip-range=192.254.0.0/16 \
  --cluster-cidr=192.233.0.0/16 \
  --cluster-name=kubernetes \
  --cluster-signing-cert-file=/etc/kubernetes/ssl/ca.pem \
  --cluster-signing-key-file=/etc/kubernetes/ssl/ca-key.pem \
  --service-account-private-key-file=/etc/kubernetes/ssl/ca-key.pem \
  --root-ca-file=/etc/kubernetes/ssl/ca.pem \
  --leader-elect=true \
  --v=2
Restart=on-failure
RestartSec=5

[Install]
WantedBy=multi-user.target

启动 kube-controller-manager

systemctl daemon-reload
systemctl enable kube-controller-manager
systemctl start kube-controller-manager
systemctl status kube-controller-manager

配置 kube-scheduler

# 创建 kube-cheduler.service 文件

vi /etc/systemd/system/kube-scheduler.service


[Unit]
Description=kubernetes Scheduler
Documentation=https://github.com/GoogleCloudPlatform/kubernetes

[Service]
ExecStart=/usr/local/bin/kube-scheduler \
  --address=127.0.0.1 \
  --master=http://192.168.1.109:8080 \
  --leader-elect=true \
  --v=2
Restart=on-failure
RestartSec=5

[Install]
WantedBy=multi-user.target

启动 kube-scheduler

systemctl daemon-reload
systemctl enable kube-scheduler
systemctl start kube-scheduler
systemctl status kube-scheduler

验证 Master 节点

[root@kubernetes-master-1 kubernetes]# kubectl get componentstatuses
NAME                 STATUS    MESSAGE              ERROR
scheduler            Healthy   ok                   
controller-manager   Healthy   ok                   
etcd-0               Healthy   {"health": "true"}   
etcd-1               Healthy   {"health": "true"}   
etcd-2               Healthy   {"health": "true"}

部署 kubernetes Node 节点

Node 节点 需要部署的组件有 docker calico kubectl kubelet kube-proxy 这几个组件。

配置 kubelet
kubelet 启动时向 kube-apiserver 发送 TLS bootstrapping 请求，需要先将 bootstrap token 文件中的 kubelet-bootstrap 用户赋予 system:node-bootstrapper 角色，然后 kubelet 才有权限创建认证请求(certificatesigningrequests)。

# 先创建认证请求
# user 为 master 中 token.csv 文件里配置的用户
# 只需在一个node中创建一次就可以

kubectl create clusterrolebinding kubelet-bootstrap --clusterrole=system:node-bootstrapper --user=kubelet-bootstrap

创建 kubelet kubeconfig 文件

# 配置集群

kubectl config set-cluster kubernetes \
  --certificate-authority=/etc/kubernetes/ssl/ca.pem \
  --embed-certs=true \
  --server=https://192.168.1.109:6443 \
  --kubeconfig=bootstrap.kubeconfig

# 配置客户端认证

kubectl config set-credentials kubelet-bootstrap \
  --token=cdc7201eb10d76842ff5b6e35bfbb516 \
  --kubeconfig=bootstrap.kubeconfig


# 配置关联

kubectl config set-context default \
  --cluster=kubernetes \
  --user=kubelet-bootstrap \
  --kubeconfig=bootstrap.kubeconfig


# 配置默认关联
kubectl config use-context default --kubeconfig=bootstrap.kubeconfig

# 拷贝生成的 bootstrap.kubeconfig 文件

mv bootstrap.kubeconfig /etc/kubernetes/

scp /etc/kubernetes/bootstrap.kubeconfig root@192.168.1.110:/etc/kubernetes/

scp /etc/kubernetes/bootstrap.kubeconfig root@192.168.1.111:/etc/kubernetes/

创建 kubelet.service 文件

# 创建 kubelet 目录

mkdir /var/lib/kubelet

vi /etc/systemd/system/kubelet.service


[Unit]
Description=kubernetes Kubelet
Documentation=https://github.com/GoogleCloudPlatform/kubernetes
After=docker.service
Requires=docker.service

[Service]
WorkingDirectory=/var/lib/kubelet
ExecStart=/usr/local/bin/kubelet \
  --address=192.168.1.110 \
  --hostname-override=192.168.1.110 \
  --pod-infra-container-image=gcr.io/google_containers/pause-amd64:3.0 \
  --experimental-bootstrap-kubeconfig=/etc/kubernetes/bootstrap.kubeconfig \
  --kubeconfig=/etc/kubernetes/kubelet.kubeconfig \
  --require-kubeconfig \
  --cert-dir=/etc/kubernetes/ssl \
  --cluster_dns=192.254.0.2 \
  --cluster_domain=cluster.local. \
  --hairpin-mode promiscuous-bridge \
  --allow-privileged=true \
  --serialize-image-pulls=false \
  --logtostderr=true \
  --cgroup-driver=systemd \
  --v=2
ExecStopPost=/sbin/iptables -A INPUT -s 10.0.0.0/8 -p tcp --dport 4194 -j ACCEPT
ExecStopPost=/sbin/iptables -A INPUT -s 172.16.0.0/12 -p tcp --dport 4194 -j ACCEPT
ExecStopPost=/sbin/iptables -A INPUT -s 192.168.0.0/16 -p tcp --dport 4194 -j ACCEPT
ExecStopPost=/sbin/iptables -A INPUT -p tcp --dport 4194 -j DROP
Restart=on-failure
RestartSec=5

[Install]
WantedBy=multi-user.target
# 如上配置:
192.168.1.110      为本机的IP
192.254.0.2       预分配的 dns 地址
cluster.local.   为 kubernetes 集群的 domain
gcr.io/google_containers/pause-amd64:3.0 镜像，

启动 kubelet

systemctl daemon-reload
systemctl enable kubelet
systemctl start kubelet
systemctl status kubelet

启动失败报错

kubelet cgroup driver: "cgroupfs" is different from docker cgroup driver: "systemd"

参考 kubernetes.io
在kubelet启动文件中添加参数--cgroup-driver=systemd \ 问题解决

配置 TLS 认证
注意 每添加一个节点 都要进行认证

# 查看 csr 的名称

[root@kubernetes-master-1 kubernetes]# kubectl get csr
NAME                                                   AGE       REQUESTOR           CONDITION
node-csr-CB1uNi3e6099Jk-uYgJJHP1DdLIcOf9jxrJ2eH-PDZg   1m        kubelet-bootstrap   Pending


# 增加 认证

[root@kubernetes-master-1 kubernetes]# kubectl certificate approve node-csr-CB1uNi3e6099Jk-uYgJJHP1DdLIcOf9jxrJ2eH-PDZg
certificatesigningrequest "node-csr-CB1uNi3e6099Jk-uYgJJHP1DdLIcOf9jxrJ2eH-PDZg" approved

验证 nodes

[root@k8s-node-1 ssl]# kubectl get nodes 
NAME            STATUS    AGE       VERSION
192.168.1.110   Ready     11s       v1.7.2

# 成功以后会自动生成配置文件与密钥

# 配置文件

ls /etc/kubernetes/kubelet.kubeconfig   
/etc/kubernetes/kubelet.kubeconfig


# 密钥文件

ls /etc/kubernetes/ssl/kubelet*
/etc/kubernetes/ssl/kubelet-client.crt  /etc/kubernetes/ssl/kubelet.crt
/etc/kubernetes/ssl/kubelet-client.key  /etc/kubernetes/ssl/kubelet.key

[root@kubernetes-master-1 kubernetes]# kubectl get csr
NAME                                                   AGE       REQUESTOR           CONDITION
node-csr-5sjslkPdNqpYZL8jRYp10seyVW4F91au7ftGQHG8YwM   2m        kubelet-bootstrap   Pending
node-csr-CB1uNi3e6099Jk-uYgJJHP1DdLIcOf9jxrJ2eH-PDZg   24m       kubelet-bootstrap   Approved,Issued
[root@kubernetes-master-1 kubernetes]# kubectl certificate approve node-csr-5sjslkPdNqpYZL8jRYp10seyVW4F91au7ftGQHG8YwM
certificatesigningrequest "node-csr-5sjslkPdNqpYZL8jRYp10seyVW4F91au7ftGQHG8YwM" approved
[root@kubernetes-master-1 kubernetes]# kubectl get nodes 
NAME            STATUS    AGE       VERSION
192.168.1.110   Ready     7s        v1.7.2
192.168.1.111   Ready     11m       v1.7.2

配置 kube-proxy

创建 kube-proxy 证书

# 证书方面由于我们node端没有装 cfssl
# 我们回到 master 端 机器 去配置证书，然后拷贝过来

[root@k8s-master-1 ~]# cd /opt/ssl


vi kube-proxy-csr.json

{
  "CN": "system:kube-proxy",
  "hosts": [],
  "key": {
    "algo": "rsa",
    "size": 2048
  },
  "names": [
    {
      "C": "CN",
      "ST": "ShenZhen",
      "L": "ShenZhen",
      "O": "k8s",
      "OU": "System"
    }
  ]
}

生成 kube-proxy 证书和私钥

/opt/local/cfssl/cfssl gencert -ca=/etc/kubernetes/ssl/ca.pem \
  -ca-key=/etc/kubernetes/ssl/ca-key.pem \
  -config=/etc/kubernetes/ssl/config.json \
  -profile=kubernetes  kube-proxy-csr.json | /opt/local/cfssl/cfssljson -bare kube-proxy

# 查看生成
ls kube-proxy*
kube-proxy.csr  kube-proxy-csr.json  kube-proxy-key.pem  kube-proxy.pem

# 拷贝到目录
cp kube-proxy*.pem /etc/kubernetes/ssl/

 scp kube-proxy*.pem root@192.168.1.110:/etc/kubernetes/ssl/
 scp kube-proxy*.pem root@192.168.1.111:/etc/kubernetes/ssl/

创建 kube-proxy kubeconfig 文件

# 配置集群

kubectl config set-cluster kubernetes \
  --certificate-authority=/etc/kubernetes/ssl/ca.pem \
  --embed-certs=true \
  --server=https://192.168.1.109:6443 \
  --kubeconfig=kube-proxy.kubeconfig


# 配置客户端认证

kubectl config set-credentials kube-proxy \
  --client-certificate=/etc/kubernetes/ssl/kube-proxy.pem \
  --client-key=/etc/kubernetes/ssl/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

# 拷贝到目录
mv kube-proxy.kubeconfig /etc/kubernetes/
scp /etc/kubernetes/kube-proxy.kubeconfig root@192.168.1.110:/etc/kubernetes/
scp /etc/kubernetes/kube-proxy.kubeconfig root@192.168.1.111:/etc/kubernetes/

创建 kube-proxy.service 文件

# 创建 kube-proxy 目录

mkdir -p /var/lib/kube-proxy


vi /etc/systemd/system/kube-proxy.service

[Unit]
Description=kubernetes Kube-Proxy Server
Documentation=https://github.com/GoogleCloudPlatform/kubernetes
After=network.target

[Service]
WorkingDirectory=/var/lib/kube-proxy
ExecStart=/usr/local/bin/kube-proxy \
  --bind-address=192.168.1.109 \
  --hostname-override=192.168.1.109 \
  --cluster-cidr=192.254.0.0/16 \
  --kubeconfig=/etc/kubernetes/kube-proxy.kubeconfig \
  --logtostderr=true \
  --v=2
Restart=on-failure
RestartSec=5
LimitNOFILE=65536

[Install]
WantedBy=multi-user.target

启动 kube-proxy

systemctl daemon-reload
systemctl enable kube-proxy
systemctl start kube-proxy
systemctl status kube-proxy

部署其他Node 节点

仿照之上面部署的kubelet kube-proxy 部署其他节点，结果如下

[root@kubernetes-master-2 kubernetes]# kubectl get nodes
NAME            STATUS    AGE       VERSION
192.168.1.109   Ready     7m        v1.7.2
192.168.1.110   Ready     7m        v1.7.2
192.168.1.111   Ready     8m        v1.7.2

Calico 网络

修改 Node kubelet.service

vi /etc/systemd/system/kubelet.service

# 增加 如下配置

  --network-plugin=cni \


# 重新加载配置
systemctl daemon-reload
systemctl restart kubelet.service
systemctl status kubelet.service

重启Node kube-proxy.service

# 重新加载配置
systemctl daemon-reload
systemctl restart kube-proxy.service
systemctl status kube-proxy.service

安装 Calico

官网地址

wget http://docs.projectcalico.org/v2.3/getting-started/kubernetes/installation/hosted/calico.yaml

wget http://docs.projectcalico.org/v2.3/getting-started/kubernetes/installation/rbac.yaml


# 镜像
[root@kubernetes-master-1 ~]# cat calico.yaml | grep image
          image: quay.io/calico/node:v1.3.0
          image: quay.io/calico/cni:v1.9.1
          image: quay.io/calico/kube-policy-controller:v0.6.0

配置 calico

 vi calico.yaml

# 注意修改如下选项:


  etcd_endpoints: "https://192.168.1.109:2379,https://192.168.1.110:2379,https://192.168.1.111:2379"

    etcd_ca: "/calico-secrets/etcd-ca"  
    etcd_cert: "/calico-secrets/etcd-cert"
    etcd_key: "/calico-secrets/etcd-key"  


# 这里面要写入 base64 的信息
# 分别执行括号内的命令，填写到 etcd-key , etcd-cert, etcd-ca 中，不用括号。


data:
  etcd-key: (cat /etc/kubernetes/ssl/etcd-key.pem | base64 | tr -d '\n')
  etcd-cert: (cat /etc/kubernetes/ssl/etcd.pem | base64 | tr -d '\n')
  etcd-ca: (cat /etc/kubernetes/ssl/ca.pem | base64 | tr -d '\n')


    - name: CALICO_IPV4POOL_CIDR
      value: "192.168.0.0/16"

导入 yaml 文件

root@kubernetes-master-2 ~]# kubectl apply -f calico.yaml 
configmap "calico-config" created
secret "calico-etcd-secrets" created
daemonset "calico-node" created
deployment "calico-policy-controller" created
serviceaccount "calico-policy-controller" created
serviceaccount "calico-node" created

[root@kubernetes-master-2 ~]# kubectl apply -f rbac.yaml 
clusterrole "calico-policy-controller" created
clusterrolebinding "calico-policy-controller" created
clusterrole "calico-node" created
clusterrolebinding "calico-node" created

验证 Calico

[root@kubernetes-master-1 ssl]# kubectl get pods -n kube-system
NAME                                        READY     STATUS    RESTARTS   AGE
calico-node-3jdz4                           2/2       Running   0          1m
calico-node-d8986                           2/2       Running   0          1m
calico-node-fz92l                           2/2       Running   0          1m
calico-policy-controller-3271399580-rnn7b   1/1       Running   0          1m
[root@kubernetes-master-1 ssl]# kubectl get ds -n kube-system
NAME          DESIRED   CURRENT   READY     UP-TO-DATE   AVAILABLE   NODE-SELECTOR   AGE
calico-node   3         3         3         3            3           <none>          1m

安装 Calicoctl

[root@kubernetes-node-1 kubernetes]# cd /usr/local/bin/

[root@kubernetes-node-1 kubernetes]# wget -c  https://github.com/projectcalico/calicoctl/releases/download/v1.3.0/calicoctl

[root@kubernetes-node-1 kubernetes]# chmod +x calicoctl


## 创建 calicoctl 配置文件

# 配置文件， 在 安装了 calico 网络的 机器下

[root@kubernetes-node-1 kubernetes]# calicoctl version
Version:      v1.3.0
Build date:   
Git commit:   d2babb6
[root@kubernetes-node-1 kubernetes]# mkdir /etc/calico
[root@kubernetes-node-1 kubernetes]# vi /etc/calico/calicoctl.cfg
apiVersion: v1
kind: calicoApiConfig
metadata:
spec:
  datastoreType: "etcdv2"
  etcdEndpoints: "https://192.168.1.109:2379,https://192.168.1.110:2379,https://192.168.1.111:2379"
  etcdKeyFile: "/etc/kubernetes/ssl/etcd-key.pem"
  etcdCertFile: "/etc/kubernetes/ssl/etcd.pem"
  etcdCACertFile: "/etc/kubernetes/ssl/ca.pem"

[root@kubernetes-node-1 kubernetes]# calicoctl node status
Calico process is running.

IPv4 BGP status
+---------------+-------------------+-------+----------+-------------+
| PEER ADDRESS  |     PEER TYPE     | STATE |  SINCE   |    INFO     |
+---------------+-------------------+-------+----------+-------------+
| 192.168.1.109 | node-to-node mesh | up    | 08:32:07 | Established |
| 192.168.1.110 | node-to-node mesh | up    | 08:32:08 | Established |
+---------------+-------------------+-------+----------+-------------+

IPv6 BGP status
No IPv6 peers found.

测试集群

# 创建一个 nginx deplyment

apiVersion: extensions/v1beta1 
kind: Deployment 
metadata: 
  name: nginx-dm
spec: 
  replicas: 2
  template: 
    metadata: 
      labels: 
        name: nginx 
    spec: 
      containers: 
        - name: nginx 
          image: nginx:alpine 
          imagePullPolicy: IfNotPresent
          ports: 
            - containerPort: 80

---

apiVersion: v1 
kind: Service
metadata: 
  name: nginx-svc 
spec: 
  ports: 
    - port: 80
      targetPort: 80
      protocol: TCP 
  selector: 
    name: nginx

[root@kubernetes-master-1 tmp]# vi deplyment.yaml
[root@kubernetes-master-1 tmp]# kubectl create -f deplyment.yaml 
deployment "nginx-dm" created
service "nginx-svc" created

[root@kubernetes-master-1 tmp]# kubectl get pods 
NAME                        READY     STATUS    RESTARTS   AGE
nginx-dm-2214564181-cshnp   1/1       Running   0          8m
nginx-dm-2214564181-w56bx   1/1       Running   0          8m
[root@kubernetes-master-1 tmp]# kubectl get deployment
NAME       DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
nginx-dm   2         2         2            2           8m
[root@kubernetes-master-1 tmp]# kubectl get svc
NAME         CLUSTER-IP       EXTERNAL-IP   PORT(S)   AGE
kubernetes   192.254.0.1      <none>        443/TCP   1h
nginx-svc    192.254.236.70   <none>        80/TCP    8m

# 在 node 里 curl

[root@kubernetes-node-1 kubernetes]# curl 192.254.236.70
<!DOCTYPE html>
<html>
<head>
<title>Welcome to nginx!</title>
<style>
    body {
        width: 35em;
        margin: 0 auto;
        font-family: Tahoma, Verdana, Arial, sans-serif;
    }
</style>
</head>
<body>
<h1>Welcome to nginx!</h1>
<p>If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.</p>

<p>For online documentation and support please refer to
<a href="http://nginx.org/">nginx.org</a>.<br/>
Commercial support is available at
<a href="http://nginx.com/">nginx.com</a>.</p>

<p><em>Thank you for using nginx.</em></p>
</body>
</html>

配置 KubeDNS

官方 github yaml 相关

https://github.com/kubernetes/kubernetes/tree/v1.7.2/cluster/addons/dns

下载镜像
docker pull gcr.io/google_containers/k8s-dns-sidecar-amd64:1.14.4
docker pull gcr.io/google_containers/k8s-dns-kube-dns-amd64:1.14.4
docker pull gcr.io/google_containers/k8s-dns-dnsmasq-nanny-amd64:1.14.4

下载 yaml 文件

mkdir /tmp/dns 
cd /tmp/dns

https://github.com/kubernetes/kubernetes/tree/v1.7.2/cluster/addons/dns/kubedns-cm.yaml


https://github.com/kubernetes/kubernetes/tree/v1.7.2/cluster/addons/dns/kubedns-sa.yaml


https://github.com/kubernetes/kubernetes/tree/v1.7.2/cluster/addons/dns/kubedns-controller.yaml.base


https://github.com/kubernetes/kubernetes/tree/v1.7.2/cluster/addons/dns/kubedns-svc.yaml.base


# 修改后缀

mv kubedns-controller.yaml.base kubedns-controller.yaml

mv kubedns-svc.yaml.base kubedns-svc.yaml

系统预定义的 RoleBinding
预定义的 RoleBinding system:kube-dns 将 kube-system 命名空间的 kube-dns ServiceAccount 与 system:kube-dns Role 绑定， 该 Role 具有访问 kube-apiserver DNS 相关 API 的权限；

[root@kubernetes-master-1 dns]# kubectl get clusterrolebindings system:kube-dns -o yaml
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: ClusterRoleBinding
metadata:
  annotations:
    rbac.authorization.kubernetes.io/autoupdate: "true"
  creationTimestamp: 2018-04-14T07:50:27Z
  labels:
    kubernetes.io/bootstrapping: rbac-defaults
  name: system:kube-dns
  resourceVersion: "107"
  selfLink: /apis/rbac.authorization.k8s.io/v1beta1/clusterrolebindings/system%3Akube-dns
  uid: 7f5cc1bd-3fb8-11e8-912e-080027d7a4ad
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: system:kube-dns
subjects:
- kind: ServiceAccount
  name: kube-dns
  namespace: kube-system

修改 kubedns-svc.yaml

# kubedns-svc.yaml 中 clusterIP: __PILLAR__DNS__SERVER__ 修改为我们之前定义的 dns IP 192.254.0.2

[root@kubernetes-master-1 dns]# cat kubedns-svc.yaml 
apiVersion: v1
kind: Service
metadata:
  name: kube-dns
  namespace: kube-system
  labels:
    k8s-app: kube-dns
    kubernetes.io/cluster-service: "true"
    addonmanager.kubernetes.io/mode: Reconcile
    kubernetes.io/name: "KubeDNS"
spec:
  selector:
    k8s-app: kube-dns
  clusterIP: 192.254.0.2
  ports:
  - name: dns
    port: 53
    protocol: UDP
  - name: dns-tcp
    port: 53
    protocol: TCP

修改 kubedns-controller.yaml

1. # 修改 --domain=__PILLAR__DNS__DOMAIN__.   为 我们之前 预定的 domain 名称 --domain=cluster.local.

2. # 修改 --server=/__PILLAR__DNS__DOMAIN__/127.0.0.1#10053  中 domain 为我们之前预定的 --server=/cluster.local./127.0.0.1#10053

3. # 修改 --probe=kubedns,127.0.0.1:10053,kubernetes.default.svc.__PILLAR__DNS__DOMAIN__, 中的 domain 为我们之前预定的  --probe=kubedns,127.0.0.1:10053,kubernetes.default.svc.cluster.local.,

4. # 修改 --probe=dnsmasq,127.0.0.1:53,kubernetes.default.svc.__PILLAR__DNS__DOMAIN__,  中的 domain 为我们之前预定的  --probe=dnsmasq,127.0.0.1:53,kubernetes.default.svc.cluster.local.,

导入 yaml 文件

[root@k8s-master-1 kubedns]# kubectl create -f .
configmap "kube-dns" created
deployment "kube-dns" created
serviceaccount "kube-dns" created
service "kube-dns" created

查看 kubedns 服务

[root@kubernetes-master-1 dns]# kubectl get all --namespace=kube-system
NAME                                           READY     STATUS    RESTARTS   AGE
po/calico-node-3jdz4                           2/2       Running   0          48m
po/calico-node-d8986                           2/2       Running   0          48m
po/calico-node-fz92l                           2/2       Running   0          48m
po/calico-policy-controller-3271399580-rnn7b   1/1       Running   0          48m
po/kube-dns-2873899911-mr8c4                   3/3       Running   0          1m

NAME           CLUSTER-IP    EXTERNAL-IP   PORT(S)         AGE
svc/kube-dns   192.254.0.2   <none>        53/UDP,53/TCP   1m

NAME                              DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
deploy/calico-policy-controller   1         1         1            1           48m
deploy/kube-dns                   1         1         1            1           1m

NAME                                     DESIRED   CURRENT   READY     AGE
rs/calico-policy-controller-3271399580   1         1         1         48m
rs/kube-dns-2873899911                   1         1         1         1m

验证 dns 服务
在验证 dns 之前，在 dns 未部署之前创建的 pod 与 deployment 等，都必须删除，重新部署，否则无法解析

# 导入之前的 nginx-dm yaml文件
[root@kubernetes-master-1 tmp]# kubectl delete -f deplyment.yaml 
deployment "nginx-dm" deleted
service "nginx-svc" deleted

[root@kubernetes-master-1 tmp]# kubectl create -f deplyment.yaml 
deployment "nginx-dm" created
service "nginx-svc" created

[root@kubernetes-master-1 tmp]# kubectl get svc nginx-svc
NAME         CLUSTER-IP        EXTERNAL-IP   PORT(S)   AGE
nginx-svc    192.254.230.234   <none>        80/TCP    40s

# 创建一个 pods 来测试一下 nameserver

apiVersion: v1
kind: Pod
metadata:
  name: alpine
spec:
  containers:
  - name: alpine
    image: alpine
    command:
    - sh
    - -c
    - while true; do sleep 1; done



# 查看 pods
[root@kubernetes-master-1 tmp]# kubectl get pods 
NAME                        READY     STATUS    RESTARTS   AGE
alpine                      1/1       Running   0          1m
nginx-dm-2214564181-5fr75   1/1       Running   0          3m
nginx-dm-2214564181-jtqg0   1/1       Running   0          3m



# 测试

[root@kubernetes-master-1 tmp]# kubectl exec -it alpine ping nginx-svc
PING nginx-svc (192.254.230.234): 56 data bytes
64 bytes from 192.254.230.234: seq=0 ttl=61 time=302.746 ms
64 bytes from 192.254.230.234: seq=1 ttl=61 time=327.175 ms


[root@kubernetes-master-1 tmp]# kubectl exec -it alpine nslookup nginx-svc
nslookup: can't resolve '(null)': Name does not resolve

Name:      nginx-svc
Address 1: 192.254.230.234 nginx-svc.default.svc.cluster.local

部署 Ingress 与 Dashboard

部署 dashboard
官方 dashboard 的github https://github.com/kubernetes/dashboard

下载 dashboard 镜像

gcr.io/google_containers/kubernetes-dashboard-amd64:v1.6.1

下载 yaml 文件

mkdir /tmp/dashboard
cd /tmp/dashboard

https://sourcegraph.com/github.com/kubernetes/kubernetes@v1.7.2/-/blob/cluster/addons/dashboard/dashboard-controller.yaml

https://sourcegraph.com/github.com/kubernetes/kubernetes@v1.7.2/-/blob/cluster/addons/dashboard/dashboard-service.yaml

# 因为开启了 RBAC 所以这里需要创建一个 RBAC 认证

vi dashboard-rbac.yaml


apiVersion: v1
kind: ServiceAccount
metadata:
  name: dashboard
  namespace: kube-system

---

kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1alpha1
metadata:
  name: dashboard
subjects:
  - kind: ServiceAccount
    name: dashboard
    namespace: kube-system
roleRef:
  kind: ClusterRole
  name: cluster-admin
  apiGroup: rbac.authorization.k8s.io

导入 yaml

# dashboard-controller.yaml 增加 rbac 授权


# 在第二个 spec 下面 增加

    spec:
      serviceAccountName: dashboard


[root@kubernetes-master-1 dashboard]# kubectl create -f .
deployment "kubernetes-dashboard" created
serviceaccount "dashboard" created
clusterrolebinding "dashboard" created
service "kubernetes-dashboard" created

[root@kubernetes-master-1 dashboard]# kubectl get svc -n kube-system kubernetes-dashboard
NAME                   CLUSTER-IP        EXTERNAL-IP   PORT(S)   AGE
kubernetes-dashboard   192.254.221.197   <none>        80/TCP    58s

访问dashboard
官网

kubectl proxy模式

[root@kubernetes-master-1 dashboard]# kubectl cluster-info
Kubernetes master is running at https://192.168.1.109:6443
KubeDNS is running at https://192.168.1.109:6443/api/v1/namespaces/kube-system/services/kube-dns/proxy
kubernetes-dashboard is running at https://192.168.1.109:6443/api/v1/namespaces/kube-system/services/kubernetes-dashboard/proxy

To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
[root@kubernetes-master-1 dashboard]# kubectl proxy --address='192.168.1.109'
Starting to serve on 192.168.1.109:8001

NodePort 模式


把 `type: ClusterIP` 用 `type: NodePort` 替换

[root@kubernetes-master-1 dashboard]# kubectl -n kube-system edit service kubernetes-dashboard
service "kubernetes-dashboard" edited
[root@kubernetes-master-1 dashboard]# kubectl -n kube-system get service kubernetes-dashboard
NAME                   CLUSTER-IP        EXTERNAL-IP   PORT(S)        AGE
kubernetes-dashboard   192.254.221.197   <nodes>       80:30897/TCP   11m

部署 Nginx Ingress

https://master-ip:30897 就可以访问了dashboard

部署 Nginx Ingress

kubernetes 暴露服务的方式目前只有三种：LoadBlancer Service、NodePort Service、Ingress；
什么是 Ingress ? Ingress 就是利用 Nginx Haproxy 等负载均衡工具来暴露 kubernetes 服务。

官方 Nginx Ingress github
https://github.com/kubernetes/ingress-nginx/tree/nginx-0.9.0-beta.11

# 官方镜像
gcr.io/google_containers/defaultbackend:1.0
gcr.io/google_containers/nginx-ingress-controller:0.9.0-beta.11
# 部署 Nginx  backend , Nginx backend 用于统一转发 没有的域名 到指定页面。


https://github.com/kubernetes/ingress-nginx/blob/nginx-0.9.0-beta.11/examples/deployment/nginx/default-backend.yaml

直接导入既可, 这里不需要修改
[root@kubernetes-master-1 nignx]# kubectl apply -f default-backend.yaml 
deployment "default-http-backend" created
service "default-http-backend" created
[root@kubernetes-master-1 nignx]# kubectl get pods -n kube-system
NAME                                        READY     STATUS    RESTARTS   AGE
calico-node-3jdz4                           2/2       Running   0          1h
calico-node-d8986                           2/2       Running   0          1h
calico-node-fz92l                           2/2       Running   0          1h
calico-policy-controller-3271399580-rnn7b   1/1       Running   0          1h
default-http-backend-726995137-4c6d5        1/1       Running   0          18s
kube-dns-2873899911-mr8c4                   3/3       Running   0          54m
kubernetes-dashboard-2273427214-lpngv       1/1       Running   0          31m

# 部署 Ingress RBAC 认证

https://github.com/kubernetes/ingress-nginx/blob/nginx-0.9.0-beta.11/examples/rbac/nginx/nginx-ingress-controller-rbac.yml

# 修改 namespace
[root@kubernetes-master-1 nignx]# sed -i 's/namespace: nginx-ingress/namespace: kube-system/g' nginx-ingress-controller-rbac.yml



[root@kubernetes-master-1 nignx]# kubectl apply -f nginx-ingress-controller-rbac.yml
namespace "nginx-ingress" created
serviceaccount "nginx-ingress-serviceaccount" created
clusterrole "nginx-ingress-clusterrole" created
role "nginx-ingress-role" created
rolebinding "nginx-ingress-role-nisa-binding" created
clusterrolebinding "nginx-ingress-clusterrole-nisa-binding" created

# 部署 Ingress Controller 组件
https://github.com/kubernetes/ingress-nginx/blob/nginx-0.9.0-beta.11/examples/daemonset/nginx/nginx-ingress-daemonset.yaml

# 修改 yaml 文件 增加 rbac 认证 和 hostNetwork , 第二个 spec 下 增加

    spec:
      hostNetwork: true
      serviceAccountName: nginx-ingress-serviceaccount


[root@kubernetes-master-1 nignx]# kubectl apply -f nginx-ingress-daemonset.yaml 
daemonset "nginx-ingress-lb" created


[root@kubernetes-master-1 nignx]# kubectl get daemonset -n kube-system
NAME               DESIRED   CURRENT   READY     UP-TO-DATE   AVAILABLE   NODE-SELECTOR   AGE
calico-node        3         3         3         3            3           <none>          1h
nginx-ingress-lb   3         3         3         3            3           <none>          23s
# 创建一个 ingress

# 查看我们原有的 svc
[root@kubernetes-master-1 nignx]# kubectl get svc nginx-svc
NAME        CLUSTER-IP        EXTERNAL-IP   PORT(S)   AGE
nginx-svc   192.254.230.234   <none>        80/TCP    58m

[[root@kubernetes-master-1 nignx]# cat nginx-ingress.yaml 
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: nginx-ingress
spec:
  rules:
  - host: nginx.qinzhao.me
    http:
      paths:
      - backend:
          serviceName: nginx-svc
          servicePort: 80
[root@kubernetes-master-1 nignx]# kubectl apply -f nginx-ingress.yaml
ingress "nginx-ingress" created
[root@kubernetes-master-1 nignx]# kubectl get ingress
NAME            HOSTS              ADDRESS            PORTS     AGE
nginx-ingress   nginx.qinzhao.me   192.168.1.109...   80        3m

curl -I nginx.qinzhao.me

# 配置一个 Dashboard Ingress


[root@kubernetes-master-1 nignx]# kubectl get svc -n kube-system kubernetes-dashboard
NAME                   CLUSTER-IP        EXTERNAL-IP   PORT(S)        AGE
kubernetes-dashboard   192.254.221.197   <nodes>       80:30897/TCP   50m
[root@kubernetes-master-1 nignx]# vi  dashboard-ingress.yaml
[root@kubernetes-master-1 nignx]# cat dashboard-ingress.yaml 
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: dashboard-ingress
  namespace: kube-system
spec:
  rules:
  - host: dashboard.jicki.me
    http:
      paths:
      - backend:
          serviceName: kubernetes-dashboard
          servicePort: 80

[root@kubernetes-master-1 nignx]# kubectl get ingress -n kube-system
No resources found.
[root@kubernetes-master-1 nignx]# kubectl create -f  dashboard-ingress.yaml
ingress "dashboard-ingress" created
[root@kubernetes-master-1 nignx]# kubectl get ingress -n kube-system
NAME                HOSTS                ADDRESS   PORTS     AGE
dashboard-ingress   dashboard.jicki.me             80        2s
[root@kubernetes-master-1 nignx]# curl -I dashboard.jicki.me

Master HA

基于 Nginx 负载 API 做 Master HA

# master 之间除 api server 以外其他组件通过 etcd 选举，api server 默认不作处理；在每个 node 上启动一个 nginx，每个 nginx 反向代理所有 api server，node 上 kubelet、kube-proxy 连接本地的 nginx 代理端口，当 nginx 发现无法连接后端时会自动踢掉出问题的 api server，从而实现 api server 的 HA

# 下载 二进制 文件

wget https://dl.k8s.io/v1.7.2/kubernetes-server-linux-amd64.tar.gz

tar -xzvf kubernetes-server-linux-amd64.tar.gz

cd kubernetes

cp -r server/bin/{kube-apiserver,kube-controller-manager,kube-scheduler,kubectl,kube-proxy,kubelet} /usr/local/bin/

# 拷贝 Matser-1 的密钥到  Master-2

# 这里我为了方便偷懒，我把所有的密钥都拷贝过去了

[root@k8s-master-1 ~]# cd /etc/kubernetes/ssl

[root@k8s-master-1 ssl]# scp -r * root@192.168.1.110:/etc/kubernetes/ssl/


# 拷贝 token.csv 文件

[root@k8s-master-1 ~]# cd /etc/kubernetes

[root@k8s-master-1 ssl]# scp -r token.csv root@192.168.1.110:/etc/kubernetes/
# 配置 Master kube-apiserver
vi /etc/systemd/system/kube-apiserver.service

[Unit]
Description=kubernetes API Server
Documentation=https://github.com/GoogleCloudPlatform/kubernetes
After=network.target

[Service]
User=root
ExecStart=/usr/local/bin/kube-apiserver \
  --admission-control=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,ResourceQuota \
  --advertise-address=192.168.1.110 \
  --allow-privileged=true \
  --apiserver-count=3 \
  --audit-log-maxage=30 \
  --audit-log-maxbackup=3 \
  --audit-log-maxsize=100 \
  --audit-log-path=/var/lib/audit.log \
  --authorization-mode=RBAC \
  --bind-address=192.168.1.110 \
  --client-ca-file=/etc/kubernetes/ssl/ca.pem \
  --enable-swagger-ui=true \
  --etcd-cafile=/etc/kubernetes/ssl/ca.pem \
  --etcd-certfile=/etc/kubernetes/ssl/etcd.pem \
  --etcd-keyfile=/etc/kubernetes/ssl/etcd-key.pem \
  --etcd-servers=https://192.168.1.109:2379,https://192.168.1.110:2379,https://192.168.1.111:2379 \
  --event-ttl=1h \
  --kubelet-https=true \
  --insecure-bind-address=192.168.1.110 \
  --runtime-config=rbac.authorization.k8s.io/v1alpha1 \
  --service-account-key-file=/etc/kubernetes/ssl/ca-key.pem \
  --service-cluster-ip-range=192.254.0.0/16 \
  --service-node-port-range=30000-32000 \
  --tls-cert-file=/etc/kubernetes/ssl/kubernetes.pem \
  --tls-private-key-file=/etc/kubernetes/ssl/kubernetes-key.pem \
  --experimental-bootstrap-token-auth \
  --token-auth-file=/etc/kubernetes/token.csv \
  --v=2
Restart=on-failure
RestartSec=5
Type=notify
LimitNOFILE=65536

# 启动 kube-apiserver
systemctl daemon-reload
systemctl enable kube-apiserver
systemctl start kube-apiserver
systemctl status kube-apiserver

# 部署 kube-controller-manager


vi /etc/systemd/system/kube-controller-manager.service

[Unit]
Description=kubernetes Controller Manager
Documentation=https://github.com/GoogleCloudPlatform/kubernetes

[Service]
ExecStart=/usr/local/bin/kube-controller-manager \
  --address=127.0.0.1 \
  --master=http://192.168.1.110:8080 \
  --allocate-node-cidrs=true \
  --service-cluster-ip-range=192.254.0.0/16 \
  --cluster-cidr=192.233.0.0/16 \
  --cluster-name=kubernetes \
  --cluster-signing-cert-file=/etc/kubernetes/ssl/ca.pem \
  --cluster-signing-key-file=/etc/kubernetes/ssl/ca-key.pem \
  --service-account-private-key-file=/etc/kubernetes/ssl/ca-key.pem \
  --root-ca-file=/etc/kubernetes/ssl/ca.pem \
  --leader-elect=true \
  --v=2
Restart=on-failure
RestartSec=5

[Install]
WantedBy=multi-user.target
# 启动 kube-controller-manager

systemctl daemon-reload
systemctl enable kube-controller-manager
systemctl start kube-controller-manager
systemctl status kube-controller-manager
# 部署 kube-scheduler

vi /etc/systemd/system/kube-scheduler.service

[Unit]
Description=kubernetes Scheduler
Documentation=https://github.com/GoogleCloudPlatform/kubernetes

[Service]
ExecStart=/usr/local/bin/kube-scheduler \
  --address=127.0.0.1 \
  --master=http://192.168.1.110:8080 \
  --leader-elect=true \
  --v=2
Restart=on-failure
RestartSec=5

[Install]
WantedBy=multi-user.target
# 启动 kube-scheduler

systemctl daemon-reload
systemctl enable kube-scheduler
systemctl start kube-scheduler
systemctl status kube-scheduler
# Master-2 里验证

[root@kubernetes-master-2 kubernetes]# kubectl get componentstatuses
NAME                 STATUS    MESSAGE              ERROR
controller-manager   Healthy   ok                   
scheduler            Healthy   ok                   
etcd-0               Healthy   {"health": "true"}   
etcd-2               Healthy   {"health": "true"}   
etcd-1               Healthy   {"health": "true"}

修改 node 配置

# kubelet

# 首先 重新创建 kubelet kubeconfig 文件

# 配置集群 (server 这里配置为127.0.0.1 既是 Master 又是 Node 的请配置为 Node IP)

kubectl config set-cluster kubernetes \
  --certificate-authority=/etc/kubernetes/ssl/ca.pem \
  --embed-certs=true \
  --server=https://127.0.0.1:6443 \
  --kubeconfig=bootstrap.kubeconfig


# 配置客户端认证

kubectl config set-credentials kubelet-bootstrap \
  --token=cdc7201eb10d76842ff5b6e35bfbb516 \
  --kubeconfig=bootstrap.kubeconfig


# 配置关联

kubectl config set-context default \
  --cluster=kubernetes \
  --user=kubelet-bootstrap \
  --kubeconfig=bootstrap.kubeconfig


# 配置默认关联
kubectl config use-context default --kubeconfig=bootstrap.kubeconfig

# 拷贝生成的 bootstrap.kubeconfig 文件

mv bootstrap.kubeconfig /etc/kubernetes/
# 重新创建 kube-proxy kubeconfig 文件

# 配置集群 (server 这里配置为 127.0.0.1 既是 Master 又是 Node 的请配置为 Node IP)

kubectl config set-cluster kubernetes \
  --certificate-authority=/etc/kubernetes/ssl/ca.pem \
  --embed-certs=true \
  --server=https://127.0.0.1:6443 \
  --kubeconfig=kube-proxy.kubeconfig


# 配置客户端认证

kubectl config set-credentials kube-proxy \
  --client-certificate=/etc/kubernetes/ssl/kube-proxy.pem \
  --client-key=/etc/kubernetes/ssl/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

# 拷贝到目录
mv kube-proxy.kubeconfig /etc/kubernetes/

创建Nginx 代理

在每个 node 都必须创建一个 Nginx 代理， 这里特别注意， 当 Master 也做为 Node 的时候 不需要配置 Nginx-proxy

# 创建配置目录
mkdir -p /etc/nginx

# 写入代理配置

cat << EOF >> /etc/nginx/nginx.conf
error_log stderr notice;

worker_processes auto;
events {
  multi_accept on;
  use epoll;
  worker_connections 1024;
}

stream {
    upstream kube_apiserver {
        least_conn;
        server 192.168.1.109:6443;
        server 192.168.1.110:6443;
    }

    server {
        listen        0.0.0.0:6443;
        proxy_pass    kube_apiserver;
        proxy_timeout 10m;
        proxy_connect_timeout 1s;
    }
}
EOF

# 配置 Nginx 基于 docker 进程，然后配置 systemd 来启动

cat << EOF >> /etc/systemd/system/nginx-proxy.service

[Unit]
Description=kubernetes apiserver docker wrapper
Wants=docker.socket
After=docker.service

[Service]
User=root
PermissionsStartOnly=true
ExecStart=/usr/bin/docker run -p 6443:6443 \\
                              -v /etc/nginx:/etc/nginx \\
                              --name nginx-proxy \\
                              --net=host \\
                              --restart=on-failure:5 \\
                              --memory=512M \\
                              nginx:1.13.3-alpine
ExecStartPre=-/usr/bin/docker rm -f nginx-proxy
ExecStop=/usr/bin/docker stop nginx-proxy
Restart=always
RestartSec=15s
TimeoutStartSec=30s

[Install]
WantedBy=multi-user.target
EOF
[root@kubernetes-master-2 kubernetes]# kubectl get nodes -owide
NAME            STATUS    AGE       VERSION   EXTERNAL-IP   OS-IMAGE                KERNEL-VERSION
192.168.1.109   Ready     2h        v1.7.2    <none>        CentOS Linux 7 (Core)   3.10.0-327.el7.x86_64
192.168.1.110   Ready     2h        v1.7.2    <none>        CentOS Linux 7 (Core)   3.10.0-327.el7.x86_64
192.168.1.111   Ready     2h        v1.7.2    <none>        CentOS Linux 7 (Core)   3.10.0-327.el7.x86_64

END
参考
https://jicki.me/2017/07/25/kubernetes-1.7.2/#%E9%AA%8C%E8%AF%81-dns-%E6%9C%8D%E5%8A%A1

qinzhao168
关注
专栏目录
【k8s集群部署篇】使用containerd运行时部署kubernetes集群（V1.27版本）
jks212454的博客
08-02 979
【k8s集群部署】使用containerd运行时部署kubernetes集群（V1.27版本）
三、搭建基于Haproxy和Keepalive的高可用k8s集群
IT谢彪的博客
09-20 386
搭建基于Haproxy和Keepalive的高可用k8s集群
kubernetes集群calico网络部署
虾米的博客
12-21 1万+
kubernetes集群calico网络部署 一. 部署环境及架构 操作系统:ubuntu14.04 Kubernetes:1.3.5 Etcd版本:2.2.1 Docker版本:1.10.1 calicoctl版本：v0.23.0 calico版本：v1.4.3 calico-ipam版本：v1.4.3 loopback版本：v0.3
22.Kubernetes（四）-----集群部署（calico、网络策略、service-Ingress、lngress TLS认证，重定向）
qq_44060147的博客
07-29 571
这里写目录标题一、pod管理1.创建Pod应用2.删除后，会重新拉取3.负载均衡4.更新回滚5.Pod的扩容与缩容二、资源清单三、生命周期 一、pod管理 1.创建Pod应用 Pod是可以创建和管理Kubernetes计算的最小可部署单元，一个Pod代表着集群中运行的一个进程，每个pod都有一个唯一的ip。 [root@server4 ~]# kubectl run demo --image=myapp:v1 ##创建一个pod应用，nginx是名字，myapp是景象 #--repli
基于calico部署k8s集群k8s-1.23.6
最新发布
shyboyandgirl的博客
08-23 1192
swap分区指的是虚拟内存分区，它的作用是物理内存使用完，之后将磁盘空间虚拟成内存来使用，启用swap设备会对系统的性能产生非常负面的影响，因此kubernetes要求每个节点都要禁用swap设备，但是如果因为某些原因确实不能关闭swap分区，就需要在集群安装过程中通过明确的参数进行配置说明。在Kubernetes中Service有两种带来模型，一种是基于iptables的，一种是基于ipvs的两者比较的话，ipvs的性能明显要高一些，但是如果要使用它，需要手动载入ipvs模块。6、禁用swap分区。
kubernetes集群（k8s）之安装部署Calico 网络
2302_77582029的博客
08-14 1万+
kubernetes集群（k8s）之安装部署Calico 网络
kubernetes+calico安装及总结
03-12
kubernetes calico安装及总结，里面会涉及到kubernetes的安全认证、serviceaccount pod认证。
从小白到大神之路之学习运维第79天-------Kubernetes网络组件详解
2302_77582029的博客
08-14 494
从小白到大神之路之学习运维第79天-------Kubernetes网络组件详解
《Kubernetes部署篇：Ubuntu20.04基于外部etcd+部署kubernetes1.24.17集群(多主多从）》
东城绝神
08-16 1049
《Kubernetes部署篇：Ubuntu20.04基于外部etcd+部署kubernetes1.24.16集群(多主多从）》
《Kubernetes部署篇：Ubuntu20.04基于containerd部署kubernetes1.25.14集群(多主多从)》
东城绝神
09-15 418
《Kubernetes部署篇：Ubuntu20.04基于containerd部署kubernetes1.25.14集群(多主多从)》
ECS+KubeSphere+KubeEdge+Rock3A(rk3568) 部署过程
u010985539的博客
05-03 1884
阿里云ECS + KubeSphere + KubeEdge + Rock3A(rk3568) 部署过程
k8s集群安装与配置
蛋蛋的碎碎念
04-27 220
本地虚拟机搭建k8s集群学习环境
kubernetes系列文章六：网络插件calico部署
zxy1981742484的博客
08-22 223
kuberentes部署calico网络插件
Kubernetes集群—Calico的介绍和部署
迷逝
10-06 1503
容器网络概述 容器网络是容器选择连接到其他容器、主机和外部网络的机制。容器的 runtime 提供了各种网络模式，每种模式都会产生不同的体验。例如，Docker 默认情况下可以为容器配置以下网络： none： 将容器添加到一个容器专门的网络堆栈中，没有对外连接。 host： 将容器添加到主机的网络堆栈中，没有隔离。 default bridge： 默认网络模式。每个容器可以通过 IP 地址相互连接。 自定义网桥： 用户定义的网桥，具有更多的灵活性、隔离性和其他便利功能。 什么是 CNI CNI(Cont
httpClient post对长参数接口的测试
热门推荐
zq24zq的博客
12-14 32万+
//测试方法 对于参数特别长的如base64解析过的图片 public static void main(String[] args) throws Exception {             String url = "localhost:8081/teach/teached/user/setInfor.ht";             Map map = new HashMap(
signature=3eda655e9e4dbd6ac0cf4fcd2462751b,PayPal
weixin_31002075的博客
05-29 4万+
To: opes-archive@ietf.orgSubject: SAGE PARMESAN UPSIDE DOWNDate: Fri, 8 Sep 2006 17:30:40 -0200MIME-Version: 1.0Content-Type: multipart/related;type="multipart/alternative";boundary="----=_NextPart_...
uni-app中使用自定义图标库
qq_43579525的博客
06-30 7993
方法一： 1.进入阿里图标库下载并解压字体图标库到本地(下载Unicode格式的) 2.在项目根目录下创建common目录，并把iconfont.css文件放入common目录中 3.修改iconont.css里的@font-face（保留base64字体图标） 3-1：未修改前是这样 @font-face {font-family: "iconfont"; src: url...
K8S 1.19 部署学习记录
qq_31389153的博客
09-08 1401
docker部署OK 准备环境： 防火墙 selinux swap ipforward [root@vms129 ~]# cat <<EOF > /etc/sysctl.d/k8s.conf > net.bridge.bridge-nf-call-ip6tables = 1 > net.bridge.bridge-nf-call-iptables =1 > net.ipv4.ip_forward = 1 > EOF k8s部署安装 （1） 安装基础服务.
使用 kubeadm 安装单master kubernetes 集群（脚本版）
Mo小泽的技术博客
09-22 2489
文章目录使用 kubeadm 安装单master kubernetes 集群配置要求检查 centos / hostname检查网络安装docker及kubelet初始化 master 节点初始化 worker节点获得 join命令参数初始化worker常见错误原因worker 节点不能访问 apiserverworker 节点默认网卡移除worker节点并重试检查初始化结果安装 Ingress Controller 使用 kubeadm 安装单master kubernetes 集群 配置要求 对于 Ku
Kubernetes 1.7.2 安装教程：从基础到实践
5. **部署网络插件**：安装如Flannel或Calico这样的网络插件，以实现跨节点的Pod通信。 6. **验证安装**：通过`kubectl get nodes`检查所有节点是否处于`Ready`状态，确保集群运行正常。 在实际操作中，可能还需要...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值