沙舟狼客的博客

目标
1. 搭建一个master和两个node
2. ip地址
```
 master: 192.168.1.4
 node1: 192.168.1.7
 node2: 192.168.1.8
```
3. 创建一个service 30080可以对外访问

基础软件安装

master

 yum install -y etcd kubernetes-master ntp flannel

node

 yum install -y etcd kubernetes-node ntp flannel docker

软件版本

 [root@master ~]# kubectl --version
 Kubernetes v1.5.2
        
 [root@master ~]# etcd --version
 etcd Version: 3.2.22
 Git SHA: 1674e68
 Go Version: go1.9.4
 Go OS/Arch: linux/amd64
        
 [root@master ~]# flanneld --version
 0.7.1
        
 [root@node1 ~]# docker --version
 Docker version 1.13.1, build 8633870/1.13.1

做成系统服务

master

 systemctl enable etcd kube-apiserver     kube-controller-manager kube-scheduler

node

 systemctl enable etcd flanneld kube-proxy kubelet docker

开始前准备

在master和node安装工具软件(最好yum update -y)

 yum install -y wget elinks ntp gcc net-tools telnet
 systemctl enable ntpd
 # 启动服务
 systemctl start ntpd
 # 设置亚洲时区
 timedatectl set-timezone Asia/Shanghai
 # 启用NTP同步
 timedatectl set-ntp yes
 # 重启ntp服务
 systemctl restart ntpd
 systemctl stop firewalld.service
 systemctl disable firewalld.service
 init 6

在每个node上执行

     docker pull registry.access.redhat.com/rhel7/pod-infrastructure:latest
        
     #如果提示下面错误:
        
     details: (open /etc/docker/certs.d/registry.access.redhat.com/redhat-ca.crt: no such file or directory)
        
     #执行下面命令
     cd
        
     wget http://mirror.centos.org/centos/7/os/x86_64/Packages/python-rhsm-certificates-1.19.10-1.el7_4.x86_64.rpm
        
     rpm2cpio python-rhsm-certificates-1.19.10-1.el7_4.x86_64.rpm | cpio -iv --to-stdout ./etc/rhsm/ca/redhat-uep.pem | tee /etc/rhsm/ca/redhat-uep.pem

在master和node上设置ip转发规则

增加转发规则

     iptables -L FORWARD ACCEPT

编辑vi /etc/sysctl.d/k8s.conf

     net.bridge.bridge-nf-call-ip6tables = 1
     net.bridge.bridge-nf-call-iptables = 1
     net.ipv4.ip_forward = 1

配置文件

master

etcd服务启动文件: /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/
     EnvironmentFile=-/etc/etcd/etcd.conf
     User=etcd
     # set GOMAXPROCS to number of processors
     ExecStart=/bin/bash -c "GOMAXPROCS=$(nproc) /usr/bin/etcd\
             --name=\"${ETCD_NAME}\"\
             --data-dir=\"${ETCD_DATA_DIR}\"\
             --listen-client-urls=\"${ETCD_LISTEN_CLIENT_URLS}\"\
             --listen-peer-urls=\"${ETCD_LISTEN_PEER_URLS}\"\
             --advertise-client-urls=\"${ETCD_ADVERTISE_CLIENT_URLS}\"\
             --initial-cluster-token=\"${ETCD_INITIAL_CLUSTER_TOKEN}\"\
             --initial-cluster=\"${ETCD_INITIAL_CLUSTER}\"\
             --initial-cluster-state=\"${ETCD_INITIAL_CLUSTER_STATE}\""
     Restart=on-failure
     LimitNOFILE=65536

etcd配置文件(cat /etc/etcd/etcd.conf grep -v ‘^#’):

     ETCD_DATA_DIR="/var/lib/etcd/etcd1.etcd"
     ETCD_LISTEN_PEER_URLS="http://192.168.1.4:2380"
     ETCD_LISTEN_CLIENT_URLS="http://192.168.1.4:2379,http://127.0.0.1:2379"
     ETCD_NAME="etcd1"
     ETCD_INITIAL_ADVERTISE_PEER_URLS="http://192.168.1.4:2380"
     ETCD_ADVERTISE_CLIENT_URLS="http://192.168.1.4:2379"
     ETCD_INITIAL_CLUSTER="etcd1=http://192.168.1.4:2380,etcd2=http://192.168.1.7:2380,etcd3=http://192.168.1.8:2380"
     ETCD_INITIAL_CLUSTER_TOKEN="etcd-cluster"
     ETCD_INITIAL_CLUSTER_STATE="new"

k8s主配置文件( cat /etc/kubernetes/config grep -v ‘^#’):

     KUBE_LOGTOSTDERR="--logtostderr=true"
     KUBE_LOG_LEVEL="--v=0"
     KUBE_ALLOW_PRIV="--allow-privileged=false"
     KUBE_MASTER="--master=http://192.168.1.4:8080"

k8s apiserver(cat /etc/kubernetes/apiserver grep -v ‘^#’)

            
     KUBE_API_ADDRESS="--insecure-bind-address=0.0.0.0"
        
     KUBE_ETCD_SERVERS="--etcd-servers=http://192.168.1.4:2379"
            
     KUBE_SERVICE_ADDRESSES="--service-cluster-ip-range=10.168.0.0/16"
            
     KUBE_ADMISSION_CONTROL="--admission-control=AlwaysAdmit"
            
     KUBE_API_ARGS=""

k8s 控制器文件(cat /etc/kubernetes/controller-manager grep -v ‘^#’)

 KUBE_CONTROLLER_MANAGER_ARGS=""

scheduler(cat /etc/kubernetes/scheduler grep -v ‘^#’)

 KUBE_SCHEDULER_ARGS=""

node 配置文件

etcd服务启动文件: /usr/lib/systemd/system/etcd.service

同master配置文件，master、node1 、node2 都一样

etcd配置文件(cat /etc/etcd/etcd.conf |grep -v ‘^#’):

     #node1配置文件
     ETCD_DATA_DIR="/var/lib/etcd/etcd2.etcd"
     ETCD_LISTEN_PEER_URLS="http://192.168.1.7:2380"
     ETCD_LISTEN_CLIENT_URLS="http://192.168.1.7:2379,http://127.0.0.1:2379"
     ETCD_NAME="etcd2"
     ETCD_INITIAL_ADVERTISE_PEER_URLS="http://192.168.1.7:2380"
     ETCD_ADVERTISE_CLIENT_URLS="http://192.168.1.7:2379,http://127.0.0.1:2379"
     ETCD_INITIAL_CLUSTER="etcd1=http://192.168.1.4:2380,etcd2=http://192.168.1.7:2380,etcd3=http://192.168.1.8:2380"
     ETCD_INITIAL_CLUSTER_TOKEN="etcd-cluster"
     ETCD_INITIAL_CLUSTER_STATE="new"
                
     #node2配置文件
     ETCD_DATA_DIR="/var/lib/etcd/etcd3.etcd"
     ETCD_LISTEN_PEER_URLS="http://192.168.1.8:2380"
     ETCD_LISTEN_CLIENT_URLS="http://192.168.1.8:2379,http://127.0.0.1:2379"
     ETCD_NAME="etcd3"
     ETCD_INITIAL_ADVERTISE_PEER_URLS="http://192.168.1.8:2380"
     ETCD_ADVERTISE_CLIENT_URLS="http://192.168.1.8:2379,http://127.0.0.1:2379"
     ETCD_INITIAL_CLUSTER="etcd1=http://192.168.1.4:2380,etcd2=http://192.168.1.7:2380,etcd3=http://192.168.1.8:2380"
     ETCD_INITIAL_CLUSTER_TOKEN="etcd-cluster"
     ETCD_INITIAL_CLUSTER_STATE="new"

区别：

ETCD_DATA_DIR和ETCD_NAME名字不一样
ETCD_INITIAL_CLUSTER完全一样，所有etcd节点的ip地址
ip不一样

k8s主配置文件( cat /etc/kubernetes/config grep -v ‘^#’):

     KUBE_LOGTOSTDERR="--logtostderr=true"
    
     KUBE_LOG_LEVEL="--v=0"
            
     KUBE_ALLOW_PRIV="--allow-privileged=false"
            
     KUBE_MASTER="--master=http://192.168.1.4:8080"

node1和node2完全一致

kublet(cat /etc/kubernetes/kubelet |grep -v ‘^#’)

 KUBELET_ADDRESS="--address=192.168.1.7"
 KUBELET_HOSTNAME="--hostname-override=192.168.1.7"
 KUBELET_API_SERVER="--api-servers=http://192.168.1.4:8080"
 KUBELET_POD_INFRA_CONTAINER="--pod-infra-container-image=registry.access.redhat.com/rhel7/pod-infrastructure:latest"
 KUBELET_ARGS=""

node1和node2的ip不同

proxy文件(cat /etc/kubernetes/proxy |grep -v ‘^#’)
```
 KUBE_PROXY_ARGS="--bind-address=0.0.0.0"
```
node1和node2完全一致

etcd设置

在master和node上分别启动etcd服务
```
 systemctl start etcd
```

检查是否正常启动

 etcdctl cluster-health
        
 etcdctl member list

正常的话会看到如下输出:

 #etcdctl cluster-health输出
 member 6b23ec425a4bbc is healthy: got healthy result from http://127.0.0.1:2379
 member 1667b822635af5d is healthy: got healthy result from http://192.168.1.4:2379
 member 9af728b0ff83aa27 is healthy: got healthy result from http://127.0.0.1:2379
 cluster is healthy
        
 #etcdctl member list输出
 6b23ec425a4bbc: name=etcd2 peerURLs=http://192.168.1.7:2380 clientURLs=http://127.0.0.1:2379,http://192.168.1.7:2379 isLeader=false
 1667b822635af5d: name=etcd1 peerURLs=http://192.168.1.4:2380 clientURLs=http://192.168.1.4:2379 isLeader=true
 9af728b0ff83aa27: name=etcd3 peerURLs=http://192.168.1.8:2380 clientURLs=http://127.0.0.1:2379,http://192.168.1.8:2379 isLeader=false

设置网络

     etcdctl mk /atomic.io/network/config '{ "Network": "10.168.0.0/16" }'

启动服务

master

 systemctl restart flanneld kube-apiserver kube-controller-manager kube-scheduler

node

 systemctl restart flanneld kube-proxy kubelet docker

验证服务

子网验证

     [root@master ~]# etcdctl ls /atomic.io/network
     /atomic.io/network/config
     /atomic.io/network/subnets
     [root@master ~]# etcdctl get /atomic.io/network/config
     {"Network": "172.168.0.0/16"}
     [root@master ~]# etcdctl ls /atomic.io/network/subnets
     /atomic.io/network/subnets/172.168.62.0-24
     /atomic.io/network/subnets/172.168.53.0-24
     /atomic.io/network/subnets/172.168.51.0-24
     [root@master ~]# etcdctl ls /atomic.io/network/subnets/172.168.62.0-24
     /atomic.io/network/subnets/172.168.62.0-24
     [root@master ~]# etcdctl get /atomic.io/network/subnets/172.168.62.0-24
     {"PublicIP":"192.168.1.7"}
     [root@master ~]# etcdctl get /atomic.io/network/subnets/172.168.53.0-24
     {"PublicIP":"192.168.1.8"}
     [root@master ~]# etcdctl get /atomic.io/network/subnets/172.168.51.0-24
     {"PublicIP":"192.168.1.4"}
     [root@master ~]#

master验证一下命令

 kubectl get node
 正常输出
 NAME          STATUS    AGE
 192.168.1.7   Ready     21h
 192.168.1.8   Ready     21h

创建一个deployment(master上执行一下命令)

建立一个nginx-deploy.yml文件:

     apiVersion: extensions/v1beta1
     kind: Deployment
     metadata:
       name: nginx
     spec:
       replicas: 2
       selector:
             matchLabels:
                     app: nginx
       template:
         metadata:
           labels:
             app: nginx
         spec:
             containers:
             - name: nginx
               image: nginx
               imagePullPolicy: IfNotPresent
               ports:
               - name: http
                 containerPort: 80
                 protocol: TCP

执行命令: kutectl create -f nginx-deploy.yml
验证：

     [root@master ~]# kubectl get deployments
     NAME      DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
     nginx     2         2         2            2           1h
     [root@master ~]# kubectl get pods -o wide
     NAME                     READY     STATUS    RESTARTS   AGE       IP             NODE
     nginx-1838792130-dcnbq   1/1       Running   1          1h        172.168.53.2   192.168.1.8
     nginx-1838792130-s9plp   1/1       Running   1          1h        172.168.62.2   192.168.1.7

创建一个service(master上执行一下命令)

service创建文件nginx-svc.yml

    apiVersion: v1
    kind: Service
    metadata:
      name: nginx
    spec:
      type: NodePort
      #sessionAffinity: ClientIP
      selector:
        app: nginx
      ports:
      - port: 80
        targetPort: 80
        nodePort: 30080
        protocol: TCP

执行创建命令kubectl create -f nginx-svc.yml
验证

    [root@master ~]# kubectl get services
    NAME         CLUSTER-IP     EXTERNAL-IP   PORT(S)        AGE
    kubernetes   10.168.1.1     <none>        443/TCP        21h
    nginx        10.168.16.34   <nodes>       80:30080/TCP   1h

验证

在node1上执行:elinks http://127.0.0.1:30080

    [root@node1 ~]# elinks --dump http://127.0.0.1:30080
                               Welcome to nginx!
    
       If you see this page, the nginx web server is successfully installed and
       working. Further configuration is required.
        
       For online documentation and support please refer to [1]nginx.org.
       Commercial support is available at [2]nginx.com.
        
       Thank you for using nginx.
        
    References
        
       Visible links
       1. http://nginx.org/
       2. http://nginx.com/

在master上执行:elinks –dump http://192.168.1.7:30080结果同上

过程中问题

node1和node2各自访问elinks –dump http://127.0.0.1:30080 时好时坏,使用ip 不能相互访问
```
 解决办法:
 检查4.iii步骤是否设置
```

使用命令无法进入容器

现象

        
 [root@master ~]# kubectl exec -it nginx-1838792130-qtgdp -- /bin/bash
        
 rpc error: code = 2 desc = oci runtime error: exec failed: container_linux.go:247: starting container process caused "process_linux.go:110: decoding init error from pipe caused \"read parent: connection reset by peer\""
        
 或者在node上执行命令:
 docker exec -it nginx /bin/bash

解决办法: docker版本问题

 yum downgrade docker-1.13.1-75.git8633870.el7.centos.x86_64 docker-client-1.13.1-75.git8633870.el7.centos.x86_64 docker-common-1.13.1-75.git8633870.el7.centos.x86_64

运维 (3)

置顶文章

最新发表

联系我：

centos7安装部署k8s并进行service外部映射