关键词：
一、总体框架图：
Master组件：
nkube-apiserver
Kubernetes API，集群的统一入口，各组件协调者，以HTTP API提供接口服务，所有对象资源的增删改查和监听操作都交给APIServer处理后再提交给Etcd存储。
nkube-controller-manager
处理集群中常规后台任务，一个资源对应一个控制器，而ControllerManager就是负责管理这些控制器的。
nkube-scheduler
根据调度算法为新创建的Pod选择一个Node节点。
Node组件：
nkubelet
kubelet是Master在Node节点上的Agent，管理本机运行容器的生命周期，比如创建容器、Pod挂载数据卷、
下载secret、获取容器和节点状态等工作。kubelet将每个Pod转换成一组容器。
nkube-proxy
在Node节点上实现Pod网络代理，维护网络规则和四层负载均衡工作。
ndocker或rocket/rkt
运行容器。
第三方服务：
netcd
分布式键值存储系统。用于保持集群状态，比如Pod、Service等对象信息。
二、部署的步骤：
1、环境规划
2、安装Docker
3、自签TLS证书
4、部署Etcd集群
5、部署Flannel网络
6、创建Node节点kubeconfig文件
7、获取K8S二进制包
8、运行Master组件
9、运行Node组件
10、查询集群状态
11、启动一个测试示例
1、环境规划：
#统一时区和时间信息
timedatectl set-local-rtc 1
timedatectl set-timezone Asia/Shanghai
timedatectl status
#修改主机名
hostnamectl --static set-hostname docker1
hostnamectl status2、安装Docker
#CentOS7
yum install -y yum-utils device-mapper-persistent-data lvm2
yum-config-manager --add-repo https://download.docker.com/linux/centos/docker-ce.repo
yum makecache fast
yum install -y docker-ce
systemctl start docker
docker run hello-world
docker version
echo ‘{
"registry-mirrors": [ "https://registry.docker-cn.com";]
}‘ > /etc/docker/daemon.json
systemctl restart docker3、自签证书：
wget https://pkg.cfssl.org/R1.2/cfssl_linux-amd64
wget https://pkg.cfssl.org/R1.2/cfssljson_linux-amd64
wget https://pkg.cfssl.org/R1.2/cfssl-certinfo_linux-amd64
chmod +x cfssl_linux-amd64 cfssljson_linux-amd64 cfssl-certinfo_linux-amd64
mv cfssl_linux-amd64 /usr/local/bin/cfssl
mv cfssljson_linux-amd64 /usr/local/bin/cfssljson
mv cfssl-certinfo_linux-amd64 /usr/bin/cfssl-certinfo
mkdir -p /opt/kubernetes/{bin,cfg,ssl} #三台docker宿主机上都要执行
cd /opt/kubernetes/ssl
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": [
"127.0.0.1",
"192.168.0.195",
"192.168.0.78",
"192.168.0.101",
"10.10.10.1",
"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-proxy4、部署ETCD集群：
#前提是已经rz etcd的二进制执行文件到/opt/kubernetes/bin/目录下
[[email protected] ~]# ls /opt/kubernetes/bin/
etcd etcdctl
#修改配置文件
[[email protected] ~]# cat /opt/kubernetes/cfg/etcd
#[Member]
ETCD_NAME="etcd03"
ETCD_DATA_DIR="/var/lib/etcd/default.etcd"
ETCD_LISTEN_PEER_URLS="https://192.168.0.195:2380"
ETCD_LISTEN_CLIENT_URLS="https://192.168.0.195:2379"
#[Clustering]
ETCD_INITIAL_ADVERTISE_PEER_URLS="https://192.168.0.195:2380"
ETCD_ADVERTISE_CLIENT_URLS="https://192.168.0.195:2379"
ETCD_INITIAL_CLUSTER="etcd03=https://192.168.0.195:2380,etcd02=https://192.168.0.78:2380,etcd01=https://192.168.0.101:2380"
ETCD_INITIAL_CLUSTER_TOKEN="etcd-cluster"
ETCD_INITIAL_CLUSTER_STATE="new"
#修改启动文件
[[email protected] ~]# cat /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=-/opt/kubernetes/cfg/etcd
ExecStart=/opt/kubernetes/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} --initial-cluster-state=new --cert-file=/opt/kubernetes/ssl/server.pem --key-file=/opt/kubernetes/ssl/server-key.pem --peer-cert-file=/opt/kubernetes/ssl/server.pem --peer-key-file=/opt/kubernetes/ssl/server-key.pem --trusted-ca-file=/opt/kubernetes/ssl/ca.pem --peer-trusted-ca-file=/opt/kubernetes/ssl/ca.pem
Restart=on-failure
LimitNOFILE=65536
[Install]
WantedBy=multi-user.target
#记得直接scp证书到别的node节点！！！ 第二次安装的经验
#启动和开机启动
systemctl start etcd
systemctl enable etcd
#验证下运行情况
[[email protected] ~]# netstat -lntup|grep etcd
tcp 0 0 192.168.0.195:2379 0.0.0.0:* LISTEN 18038/etcd
tcp 0 0 127.0.0.1:2379 0.0.0.0:* LISTEN 18038/etcd
tcp 0 0 192.168.0.195:2380 0.0.0.0:* LISTEN 18038/etcd
[[email protected] ~]#
[[email protected] ~]# systemctl status etcd
● etcd.service - Etcd Server
Loaded: loaded (/usr/lib/systemd/system/etcd.service; disabled; vendor preset: disabled)
Active: activating (start) since Thu 2018-02-01 14:40:44 CST; 3s ago
Main PID: 18272 (etcd)
Memory: 14.8M
CGroup: /system.slice/etcd.service
└─18272 /opt/kubernetes/bin/etcd --name=etcd03 --data-dir=/var/lib/etcd/default.etcd --listen-peer-urls=https://192.168.0.195:2380 ...
Feb 01 14:40:46 docker3 etcd[18272]: request cluster ID mismatch (got 3b51f2169c0d39ba want ee2e162b8c4b542b)
Feb 01 14:40:47 docker3 etcd[18272]: request sent was ignored (cluster ID mismatch: peer[9c97b9b3d6c86056]=3b51f2169c0d39ba, local=ee2...c4b542b)
Feb 01 14:40:47 docker3 etcd[18272]: request sent was ignored (cluster ID mismatch: peer[ea36423e7d6e2441]=3b51f2169c0d39ba, local=ee2...c4b542b)
Feb 01 14:40:47 docker3 etcd[18272]: request sent was ignored (cluster ID mismatch: peer[9c97b9b3d6c86056]=3b51f2169c0d39ba, local=ee2...c4b542b)
Feb 01 14:40:47 docker3 etcd[18272]: request cluster ID mismatch (got 3b51f2169c0d39ba want ee2e162b8c4b542b)
Feb 01 14:40:47 docker3 etcd[18272]: request sent was ignored (cluster ID mismatch: peer[ea36423e7d6e2441]=3b51f2169c0d39ba, local=ee2...c4b542b)
Feb 01 14:40:47 docker3 etcd[18272]: request cluster ID mismatch (got 3b51f2169c0d39ba want ee2e162b8c4b542b)
Feb 01 14:40:47 docker3 etcd[18272]: request cluster ID mismatch (got 3b51f2169c0d39ba want ee2e162b8c4b542b)
Feb 01 14:40:47 docker3 etcd[18272]: request cluster ID mismatch (got 3b51f2169c0d39ba want ee2e162b8c4b542b)
Feb 01 14:40:47 docker3 etcd[18272]: request cluster ID mismatch (got 3b51f2169c0d39ba want ee2e162b8c4b542b)
Hint: Some lines were ellipsized, use -l to show in full.
#查看etcd集群状态：
[[email protected] ~]# cd /opt/kubernetes/ssl
[[email protected] ssl]# ls
ca-key.pem ca.pem server-key.pem server.pem
[[email protected] ssl]# /opt/kubernetes/bin/etcdctl > --ca-file=ca.pem --cert-file=server.pem --key-file=server-key.pem > --endpoints="https://192.168.0.195:2379,https://192.168.0.78:2379,https://192.168.0.101:2379" > cluster-health
member 1867c607b632ef74 is healthy: got healthy result from https://192.168.0.78:2379
member 4f5978bb4e5f8a9e is unreachable: no available published client urls #报错 其中master的etcd不能用啊 ？？？
member f948418339a94dd3 is healthy: got healthy result from https://192.168.0.101:2379
cluster is healthy #但是其他两个节点又没有问题，我日！
[[email protected] ssl]# netstat -lntup|grep etcd
tcp 0 0 192.168.0.195:2379 0.0.0.0:* LISTEN 19136/etcd
tcp 0 0 127.0.0.1:2379 0.0.0.0:* LISTEN 19136/etcd
tcp 0 0 192.168.0.195:2380 0.0.0.0:* LISTEN 19136/etcd
#检测是否正常的语句
/opt/kubernetes/bin/etcdctl --ca-file=ca.pem --cert-file=server.pem --key-file=server-key.pem --endpoints="https://192.168.0.195:2379,https://192.168.0.78:2379,https://192.168.0.101:2379" cluster-health
#第二次安装完美成功！
[[email protected] ssl]# /opt/kubernetes/bin/etcdctl > --ca-file=ca.pem --cert-file=server.pem --key-file=server-key.pem > --endpoints="https://192.168.0.195:2379,https://192.168.0.78:2379,https://192.168.0.101:2379" > cluster-health
member 1867c607b632ef74 is healthy: got healthy result from https://192.168.0.78:2379
member 4f5978bb4e5f8a9e is healthy: got healthy result from https://192.168.0.195:2379
member f948418339a94dd3 is healthy: got healthy result from https://192.168.0.101:2379
cluster is healthy
5、部署flanneld网络
1）写入分配的子网段到etcd，供flanneld使用
/opt/kubernetes/bin/etcdctl
--ca-file=ca.pem --cert-file=server.pem --key-file=server-key.pem
--endpoints="https://192.168.0.211:2379,https://192.168.0.212:2379,https://192.168.0.213:2379"
set /coreos.com/network/config ‘{ "Network": "172.17.0.0/16", "Backend": {"Type": "vxlan"}}‘
2）下载二进制包
wget https://github.com/coreos/flannel/releases/download/v0.9.1/flannel-v0.9.1-linux-amd64.tar.gz
3）配置Flannel cfg
4）systemd管理Flannel
5）配置Docker启动指定子网段
6）启动
#前提是已经rz flanneld 的二进制执行文件到/opt/kubernetes/bin/目录下
[[email protected] ~]# ls /opt/kubernetes/bin/
etcd etcdctl flanneld mk-docker-opts.sh
#写入分配的子网段到etcd，供flanneld使用
cd /opt/kubernetes/ssl
/opt/kubernetes/bin/etcdctl --ca-file=ca.pem --cert-file=server.pem --key-file=server-key.pem --endpoints="https://192.168.0.195:2379,https://192.168.0.78:2379,https://192.168.0.101:2379" set /coreos.com/network/config ‘{ "Network": "172.17.0.0/16", "Backend": {"Type": "vxlan"}}‘
#配置Flannel cfg
cat <<EOF >/opt/kubernetes/cfg/flanneld
FLANNEL_OPTIONS="--etcd-endpoints=https://192.168.0.195:2379,https://192.168.0.78:2379,https://192.168.0.101:2379 -etcd-cafile=/opt/kubernetes/ssl/ca.pem -etcd-certfile=/opt/kubernetes/ssl/server.pem -etcd-keyfile=/opt/kubernetes/ssl/server-key.pem"
EOF
#systemd管理Flannel
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
#问题1：我这里如果\$FLANNEL_OPTIONS 就可以启动 $FLANNEL_OPTIONS 反而报错 可能和配置文件没有写正确有关系把！ 第二次安装还是需要注释掉才能正常启动 2018年2月5日 16:16:34 经过阿良哥指导是因为$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启动指定子网段
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
#查看etcd存储的信息
[[email protected] ssl]# /opt/kubernetes/bin/etcdctl --ca-file=ca.pem --cert-file=server.pem --key-file=server-key.pem --endpoints="https://192.168.0.195:2379,https://192.168.0.78:2379,https://192.168.0.101:2379" ls /coreos.com/network/subnets
/coreos.com/network/subnets/172.17.47.0-24
/coreos.com/network/subnets/172.17.92.0-24
[[email protected] ssl]# /opt/kubernetes/bin/etcdctl --ca-file=ca.pem --cert-file=server.pem --key-file=server-key.pem --endpoints="https://192.168.0.195:2379,https://192.168.0.78:2379,https://192.168.0.101:2379" get /coreos.com/network/subnets/172.17.47.0-24
{"PublicIP":"192.168.0.101","BackendType":"vxlan","BackendData":{"VtepMAC":"fe:f4:f3:14:cd:6a"}}
[[email protected] ssl]# /opt/kubernetes/bin/etcdctl --ca-file=ca.pem --cert-file=server.pem --key-file=server-key.pem --endpoints="https://192.168.0.195:2379,https://192.168.0.78:2379,https://192.168.0.101:2379" get /coreos.com/network/subnets/172.17.92.0-24
{"PublicIP":"192.168.0.78","BackendType":"vxlan","BackendData":{"VtepMAC":"0a:75:1e:ab:a7:e0"}}
6、创建Node节点所需的kubeconfig文件
#前提是已经rz flanneld 的二进制执行文件到/opt/kubernetes/bin/目录下
[[email protected] bin]# ls /opt/kubernetes/bin/
etcd etcdctl flanneld kubectl mk-docker-opts.sh
[[email protected] bin]# chmod +x kubectl
# 创建 TLS Bootstrapping Token
export BOOTSTRAP_TOKEN=$(head -c 16 /dev/urandom | od -An -t x | tr -d ‘ ‘)
cat > token.csv <<EOF
${BOOTSTRAP_TOKEN},kubelet-bootstrap,10001,"system:kubelet-bootstrap"
EOF
#----------------------
# 创建kubelet bootstrapping kubeconfig
export KUBE_APISERVER="https://192.168.0.195:6443"
# 设置集群参数
/opt/kubernetes/bin/kubectl config set-cluster kubernetes --certificate-authority=./ca.pem --embed-certs=true --server=${KUBE_APISERVER} --kubeconfig=bootstrap.kubeconfig
# 设置客户端认证参数
/opt/kubernetes/bin/kubectl config set-credentials kubelet-bootstrap --token=${BOOTSTRAP_TOKEN} --kubeconfig=bootstrap.kubeconfig
# 设置上下文参数
/opt/kubernetes/bin/kubectl config set-context default --cluster=kubernetes --user=kubelet-bootstrap --kubeconfig=bootstrap.kubeconfig
# 设置默认上下文
/opt/kubernetes/bin/kubectl config use-context default --kubeconfig=bootstrap.kubeconfig
#----------------------
# 创建kube-proxy kubeconfig文件
/opt/kubernetes/bin/kubectl config set-cluster kubernetes --certificate-authority=./ca.pem --embed-certs=true --server=${KUBE_APISERVER} --kubeconfig=kube-proxy.kubeconfig
/opt/kubernetes/bin/kubectl config set-credentials kube-proxy --client-certificate=./kube-proxy.pem --client-key=./kube-proxy-key.pem --embed-certs=true --kubeconfig=kube-proxy.kubeconfig
/opt/kubernetes/bin/kubectl config set-context default --cluster=kubernetes --user=kube-proxy --kubeconfig=kube-proxy.kubeconfig
/opt/kubernetes/bin/kubectl config use-context default --kubeconfig=kube-proxy.kubeconfig
7、获取K8S二进制包
[[email protected] bin]# ls /opt/kubernetes/bin
etcd etcdctl flanneld kubectl master.zip mk-docker-opts.sh
[[email protected] ssl]# ls /opt/kubernetes/bin
etcd etcdctl flanneld kubectl mk-docker-opts.sh node.zip
[[email protected] ssl]# ls /opt/kubernetes/bin
etcd etcdctl flanneld kubectl mk-docker-opts.sh node.zip
8、运行Master组件
#解压master.zip 运行apiserver.sh如下 并执行kube-apiserver的启动
export MASTER_ADDRESS=${1:-"192.168.0.195"}
export ETCD_SERVERS=${2:-"https://192.168.0.195:2379,https://192.168.0.78:2379,https://192.168.0.101:2379"}
cat <<EOF >/opt/kubernetes/cfg/kube-apiserver
KUBE_APISERVER_OPTS="--logtostderr=true --v=4 --etcd-servers=${ETCD_SERVERS} --insecure-bind-address=127.0.0.1 --bind-address=${MASTER_ADDRESS} --insecure-port=8080 --secure-port=6443 --advertise-address=${MASTER_ADDRESS} --allow-privileged=true --service-cluster-ip-range=10.10.10.0/24 --admission-control=NamespaceLifecycle,LimitRanger,SecurityContextDeny,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/kubernetes/ssl/ca.pem --etcd-certfile=/opt/kubernetes/ssl/server.pem --etcd-keyfile=/opt/kubernetes/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
#保证把token.csv文件放到/opt/kubernetes/cfg/目录下！！！
[[email protected] cfg]# cp /opt/kubernetes/ssl/token.csv /opt/kubernetes/cfg/
[[email protected] cfg]# ls /opt/kubernetes/cfg/
etcd flanneld kube-apiserver token.csv
systemctl daemon-reload
systemctl enable kube-apiserver
systemctl restart kube-apiserver
#运行controller-manager.sh如下 并执行kube-controller-manager 的启动
export MASTER_ADDRESS=${1:-"127.0.0.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.10.10.0/24 --cluster-name=kubernetes --cluster-signing-cert-file=/opt/kubernetes/ssl/ca.pem --cluster-signing-key-file=/opt/kubernetes/ssl/ca-key.pem --service-account-private-key-file=/opt/kubernetes/ssl/ca-key.pem --root-ca-file=/opt/kubernetes/ssl/ca.pem"
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
#运行controller-manager.sh如下 并执行kube-controller-manager 的启动
export MASTER_ADDRESS=${1:-"127.0.0.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
echo ‘export PATH=$PATH:/opt/kubernetes/bin/‘ >>/etc/profile
. /etc/profile
#很重要的一步：执行绑定node角色用户
[[email protected] ssl]# kubectl create clusterrolebinding kubelet-bootstrap --clusterrole=system:node-bootstrapper --user=kubelet-bootstrap
clusterrolebinding "kubelet-bootstrap" created
#验证下：
[[email protected] bin]# kubectl get cs
NAME STATUS MESSAGE ERROR
controller-manager Healthy ok
scheduler Healthy ok
etcd-2 Healthy {"health": "true"}
etcd-0 Healthy {"health": "true"}
etcd-1 Healthy {"health": "true"}
9、运行Node组件
#拷贝第六步 产生 的 node节点所需的kubeconfig文件到各node节点的/opt/kubernetes/cfg/目录下
[[email protected] ssl]# cd /opt/kubernetes/ssl/
[[email protected] ssl]# scp kube-proxy.kubeconfig bootstrap.kubeconfig 192.168.0.78:/opt/kubernetes/cfg/
[email protected]‘s password:
kube-proxy.kubeconfig 100% 6295 5.8MB/s 00:00
bootstrap.kubeconfig 100% 2189 2.3MB/s 00:00
[[email protected] ssl]# scp kube-proxy.kubeconfig bootstrap.kubeconfig 192.168.0.101:/opt/kubernetes/cfg/
[email protected]‘s password:
kube-proxy.kubeconfig 100% 6295 933.6KB/s 00:00
bootstrap.kubeconfig 100% 2189 206.9KB/s 00:00
#解压node.zip
[[email protected] bin]# unzip node.zip
[[email protected] bin]# chmod +x kubelet kube-proxy
[[email protected] bin]# ls
etcd etcdctl flanneld kubectl kubelet kubelet.sh kube-proxy mk-docker-opts.sh node.zip proxy.sh
#node1节点运行kubelet组件
export NODE_ADDRESS=${1:-"192.168.0.101"}
export DNS_SERVER_IP=${2:-"10.10.10.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 --cert-dir=/opt/kubernetes/ssl --allow-privileged=true --cluster-dns=${DNS_SERVER_IP} --cluster-domain=cluster.local --fail-swap-on=false --pod-infra-container-image=registry.cn-hangzhou.aliyuncs.com/google-containers/pause-amd64:3.0"
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
#node1节点运行kube-proxy组件
export NODE_ADDRESS=${1:-"192.168.0.101"}
cat <<EOF >/opt/kubernetes/cfg/kube-proxy
KUBE_PROXY_OPTS="--logtostderr=true --v=4 --hostname-override=${NODE_ADDRESS} --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
10、查询集群状态
[[email protected] ~]# kubectl get node
NAME STATUS ROLES AGE VERSION
192.168.0.101 Ready <none> 1d v1.9.0
192.168.0.78 Ready <none> 1d v1.9.0
[[email protected] ~]# kubectl get cs
NAME STATUS MESSAGE ERROR
controller-manager Healthy ok
scheduler Healthy ok
etcd-0 Healthy {"health": "true"}
etcd-1 Healthy {"health": "true"}
etcd-2 Healthy {"health": "true"}
11、启动一个测试示例
kubectl run nginx --image=nginx --replicas=3
kubectl get pod
kubectl expose deployment nginx --port=88 --target-port=80 --type=NodePort
kubectl get svc nginx
问题1的解决：
linux企业运维——k8s高可用集群架构搭建详解(代码片段)
K8s高可用集群文章目录K8s高可用集群一、K8s高可用集群架构原理二、实验环境三、K8s高可用集群架构搭建3.1、负载均衡Loadbalancer部署—haproxy3.2、Docker部署3.3、K8s集群部署3.4、K8s集群添加worker节点四、集群高可用性能测试一、K8s... 查看详情
linux企业运维——k8s高可用集群架构搭建详解(代码片段)
K8s高可用集群文章目录K8s高可用集群一、K8s高可用集群架构原理二、实验环境三、K8s高可用集群架构搭建1、负载均衡Loadbalancer部署—haproxy2、Docker部署3、K8s集群部署4、K8s集群添加worker节点四、集群高可用性能测试一、K8s高可用... 查看详情
k8s落地实践之旅——pod（豌豆荚）(代码片段)
文章目录✨前言1.认识k8s🍑容器调度管理平台🍑架构图🍑核心组件🍑理解集群资源🍑kubectl的使用2.工作流程🍑架构设计的几点思考🍑实践集群安装3.Pod定义🍑使用yaml格式定义Pod🍑创建和访... 查看详情
[k8s]elk架构设计-k8s集群里搭建
elk设计架构参考Elasticsearch最佳实践建议将这些节点分成三个角色：Master节点-仅用于集群管理，没有数据，没有HTTPAPIClient节点-用于客户端使用，无数据，使用HTTPAPIData节点-旨在存储和索引数据，没有HTTPAPI分为管理区存储区读写... 查看详情
我的“技术架构”之旅
导言：很久没写过涉及技术的文章了，因为进行职业转型后对技术有种很纠结的心态。热爱——每每看到五颜六色的代码窗口就会心里发酸，想起曾经那是生活中的一份灿烂心情；不自信——这么久离开技术会不会已经落后生疏... 查看详情
linux企业运维——k8s高可用集群架构搭建详解(代码片段)
K8s高可用集群文章目录K8s高可用集群一、K8s高可用集群架构原理二、实验环境三、K8s高可用集群架构搭建3.1、负载均衡Loadbalancer部署—haproxy3.2、Docker部署3.3、K8s集群部署3.4、K8s集群添加worker节点四、集群高可用性能测试一、K8s... 查看详情
k8s之001:概述集群搭建(代码片段)
...es概述:1.kubernetes基本介绍1.1前置知识:2.K28特性:3.k8s的集群架构:4.k8s核心概念:4.1pod:4.2controller:4.3service:二、集群搭建:1.搭建k8s环境平台规划:1.1单master节点:1.2多master节点:1.3硬件要求:2.k8s集群搭建方法--kubeadm:2.1系统配置及初始化:2.2... 查看详情
kubernetes（k8s）单matser集群架构的搭建（v1.20）(代码片段)
文章目录Kubernetes单Matser集群架构的搭建架构图环境准备操作系统初始化配置部署etcd集群准备签发证书环境在master01节点上操作在node01节点上操作在node02节点上操作部署docker引擎部署Master组件在master01节点上操作部署WorkerNode组件... 查看详情
从零到壹搭建一个商城架构--k8s集群安装(代码片段)
如果想了解其他内容，请点击这里查看目录1、kubeadmkubeadm是官方推出的一个用于快速部署kubernetes集群的工具这个工具能通过两条指令完成一个kubernetes集群的部署：#创建一个Mster节点kubeadminit#将一个Node节点加入到当前集群中kubead... 查看详情
使用树莓派搭建k8s集群（arm64架构，附安装脚本）(代码片段)
为了能够更好的学习K8S，王道还是得自己动手在虚拟机上玩K8S，没啥感觉。决定挑战自己，然后买了6个树莓派，在真实的硬件上从零开始搭建部署K8S。以下内容在自己的树莓派集群上经过充分验证，没毛病。... 查看详情
手把手从零开始搭建k8s集群超详细教程(代码片段)
本教程根据B站课程云原生Java架构师的第一课K8s+Docker+KubeSphere+DevOps同步所做笔记教程k8s集群搭建超详细教程1.基本环境搭建1.创建私有网络2.创建服务器资源3.远程连接到服务器4.docker容器化环境安装5.kubeadm、kubectl、kubelet... 查看详情
手把手从零开始搭建k8s集群超详细教程(代码片段)
本教程根据B站课程云原生Java架构师的第一课K8s+Docker+KubeSphere+DevOps同步所做笔记教程k8s集群搭建超详细教程1.基本环境搭建1.创建私有网络2.创建服务器资源3.远程连接到服务器4.docker容器化环境安装5.kubeadm、kubectl、kubelet... 查看详情
前后端分离架构+k8s+ingress(代码片段)
一、概述在前面几篇文章中，已经讲到了前后端分离架构和ingress，链接如下：https://www.cnblogs.com/xiao987334176/p/12195722.htmlhttps://www.cnblogs.com/xiao987334176/p/12195797.html接下来使用k8s进行发布应用 二、演示3.0环境说明k8s集群系统dockeri... 查看详情
kubernetes概述和kubeadm方式集群搭建(代码片段)
...etes概述和kubeadm方式集群搭建kubernetes概述k8s的功能K8S集群架构组件K8S核心概念集群搭建kubeadm部署方式1.系统初始化2.master和node1,2安装Docker/kubeadm/kubelet3.部署KubernetesMaster4.加入KubernetesNode5.安装Pod网络插件（CNI）6.测试kubernet... 查看详情
我的gradle安装探索之旅
...://gradle.org/docs官方给出了这么贴心的文档我绝对尝试搭建我的环境。 1第一步安装 这是教我们安装给出的内容 以下为翻译内容 预备知识 Gradle运行在所有的主流操作系统需要安装JDK或者JRE 7或以上版本&... 查看详情
linux12k8s--＞10搭建wordpess+discuz(代码片段)
...或宕机数据随之丢失一、搭建wordpress1、构建镜像2、构思架构，同时编写配置清单 查看详情
我的opengl学习进阶之旅收集的3d渲染技术之uvmap和mesh相关资料(代码片段)
一、为什么要了解UVMap在我的博客【我的Android进阶之旅】在Android中使用MediaPipe库在实时视频源上实现人脸网格FaceMesh的绘制里面有简单介绍：最终要实现增强人脸AugmentedFaces的话，里面有个重要步骤是使用UV贴图来绘制面... 查看详情
openstack成长之旅-5swift介绍安装及作者的反思
...错，一些基本的东西，频频出错，对此很是无奈啊，看来我的能力还是有待提升了，虽说虚拟机搭建openstack会有一些问题，但是也没有我的这么夸张吧，所以我决定，最近一段时间内要闭关修炼了，一定要能在任何环境中熟练操... 查看详情