{"id":7798,"date":"2019-04-23T16:58:49","date_gmt":"2019-04-23T08:58:49","guid":{"rendered":"http:\/\/rmohan.com\/?p=7798"},"modified":"2019-04-23T17:03:09","modified_gmt":"2019-04-23T09:03:09","slug":"kubernetes-install-centos7","status":"publish","type":"post","link":"https:\/\/mohan.sg\/?p=7798","title":{"rendered":"Kubernetes install centos7"},"content":{"rendered":"\n

Kubeadm quickly builds a k8s cluster<\/p>\n\n\n\n

surroundings<\/p>\n\n\n\n

Master01: 192.168.1.110 (minimum 2 core CPU)<\/p>\n\n\n\n

node01: 192.168.1.100<\/p>\n\n\n\n

planning<\/p>\n\n\n\n

Services network: 10.96.0.0\/12<\/p>\n\n\n\n

Pod network: 10.244.0.0\/16<\/p>\n\n\n\n

  1. Configure hosts to resolve each host<\/li><\/ol>\n\n\n\n

    vim \/etc\/hosts<\/p>\n\n\n\n

    127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
    \n::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
    \n192.168.1.110 master01
    \n192.168.1.100 node01<\/p>\n\n\n\n

    1. Synchronize each host time<\/li><\/ol>\n\n\n\n

      yum install -y ntpdate
      \nntpdate time.windows.com<\/p>\n\n\n\n

      14 Mar 16:51:32 ntpdate[46363]: adjust time server 13.65.88.161 offset -0.001108 sec<\/p>\n\n\n\n

      1. Close SWAP and close selinux<\/li><\/ol>\n\n\n\n

        swapoff -a<\/p>\n\n\n\n

        vim \/etc\/selinux\/config<\/p>\n\n\n\n

        This file controls the state of SELinux on the system.<\/h4>\n\n\n\n

        SELINUX= can take one of these three values:<\/h4>\n\n\n\n

        enforcing – SELinux security policy is enforced.<\/h4>\n\n\n\n

        permissive – SELinux prints warnings instead of enforcing.<\/h4>\n\n\n\n

        disabled – No SELinux policy is loaded.<\/h4>\n\n\n\n

        SELINUX=disabled<\/p>\n\n\n\n

        1. Install docker-ce<\/li><\/ol>\n\n\n\n

          yum install -y yum-utils device-mapper-persistent-data lvm2
          \nyum-config-manager –add-repo http:\/\/mirrors.aliyun.com\/docker-ce\/linux\/CentOS\/docker-ce.repo
          \nyum makecache fast
          \nyum -y install docker-ce<\/p>\n\n\n\n

          Appears after Docker installation: WARNING: bridge-nf-call-iptables is disabled<\/p>\n\n\n\n

          vim \/etc\/sysctl.conf<\/p>\n\n\n\n

          sysctl settings are defined through files in<\/h4>\n\n\n\n

          \/usr\/lib\/sysctl.d\/, \/run\/sysctl.d\/, and \/etc\/sysctl.d\/.<\/h4>\n\n\n\n

          <\/p>\n\n\n\n

          Vendors settings live in \/usr\/lib\/sysctl.d\/.<\/h4>\n\n\n\n

          To override a whole file, create a new file with the same in<\/h4>\n\n\n\n

          \/etc\/sysctl.d\/ and put new settings there. To override<\/h4>\n\n\n\n

          only specific settings, add a file with a lexically later<\/h4>\n\n\n\n

          name in \/etc\/sysctl.d\/ and put new settings there.<\/h4>\n\n\n\n

          #<\/p>\n\n\n\n

          For more information, see sysctl.conf(5) and sysctl.d(5).<\/h4>\n\n\n\n

          net.bridge.bridge-nf-call-ip6tables=1
          \nnet.bridge.bridge-nf-call-iptables=1
          \nnet.bridge.bridge-nf-call-arptables=1<\/p>\n\n\n\n

          systemctl enable docker && systemctl start docker<\/p>\n\n\n\n

          1. Install kubernetes<\/li><\/ol>\n\n\n\n

            cat < \/etc\/yum.repos.d\/kubernetes.repo
            \n<\/p>\n\n\n

            [kubernetes]<\/p>\n\n\n\n

            \nname=Kubernetes
            \nbaseurl=https:\/\/mirrors.aliyun.com\/kubernetes\/yum\/repos\/kubernetes-el7-x86_64\/
            \nenabled=1
            \ngpgcheck=1
            \nrepo_gpgcheck=1
            \ngpgkey=https:\/\/mirrors.aliyun.com\/kubernetes\/yum\/doc\/yum-key.gpg https:\/\/mirrors.aliyun.com\/kubernetes\/yum\/doc\/rpm-package-key.gpg
            \nEOF
            \nsetenforce 0
            \nyum install -y kubelet kubeadm kubectl
            \nsystemctl enable kubelet && systemctl start kubelet\n<\/p>\n\n\n\n

            1. Initialize the cluster<\/li><\/ol>\n\n\n\n

              kubeadm init –image-repository registry.aliyuncs.com\/google_containers –cubernetes-version v1.13.1 –pod-network-cidr = 10.244.0.0 \/ 16<\/p>\n\n\n\n

              Your Kubernetes master has initialized successfully!<\/p>\n\n\n\n

              To start using your cluster, you need to run the following as a regular user:<\/p>\n\n\n\n

              mkdir -p $HOME\/.kube
              \n sudo cp -i \/etc\/kubernetes\/admin.conf $HOME\/.kube\/config
              \n sudo chown $(id -u):$(id -g) $HOME\/.kube\/config<\/p>\n\n\n\n

              You should now deploy a pod network to the cluster.
              \nRun “kubectl apply -f [podnetwork].yaml” with one of the options listed at:
              \n https:\/\/kubernetes.io\/docs\/concepts\/cluster-administration\/addons\/<\/p>\n\n\n\n

              You can now join any number of machines by running the following on each node
              \nas root:<\/p>\n\n\n\n

              kubeadm join 192.168.1.110:6443 –token wgrs62.vy0trlpuwtm5jd75 –discovery-token-ca-cert-hash sha256:6e947e63b176acf976899483d41148609a6e109067ed6970b9fbca8d9261c8d0<\/p>\n\n\n\n

              1. Manually deploy flannel<\/li><\/ol>\n\n\n\n

                Flannel URL: https:\/\/github.com\/coreos\/flannel<\/p>\n\n\n\n

                for Kubernetes v1.7 +<\/p>\n\n\n\n

                kubectl apply -f https:\/\/raw.githubusercontent.com\/coreos\/flannel\/master\/Documentation\/kube-flannel.yml<\/p>\n\n\n\n

                podsecuritypolicy.extensions\/psp.flannel.unprivileged created
                \nclusterrole.rbac.authorization.k8s.io\/flannel created
                \nclusterrolebinding.rbac.authorization.k8s.io\/flannel created
                \nserviceaccount\/flannel created
                \nconfigmap\/kube-flannel-cfg created
                \ndaemonset.extensions\/kube-flannel-ds-amd64 created
                \ndaemonset.extensions\/kube-flannel-ds-arm64 created
                \ndaemonset.extensions\/kube-flannel-ds-arm created
                \ndaemonset.extensions\/kube-flannel-ds-ppc64le created
                \ndaemonset.extensions\/kube-flannel-ds-s390x created<\/p>\n\n\n\n

                8.node placement<\/p>\n\n\n\n

                Install docker kubelet kubeadm<\/p>\n\n\n\n

                Docker installation is the same as step 4, kubelet kubeadm installation is the same as step 5<\/p>\n\n\n\n

                9.node joins the master<\/p>\n\n\n\n

                kubeadm join 192.168.1.110:6443 –token wgrs62.vy0trlpuwtm5jd75 –discovery-token-ca-cert-hash sha256:6e947e63b176acf976899483d41148609a6e109067ed6970b9fbca8d9261c8d0<\/p>\n\n\n\n

                Kubectl get nodes #View node status<\/p>\n\n\n\n

                NAME STATUS ROLES AGE VERSION
                \nlocalhost.localdomain NotReady 130m v1.13.4
                \nmaster01 Ready master 4h47m v1.13.4
                \nnode01 Ready 94m v1.13.4<\/p>\n\n\n\n

                Kubectl get cs #View component status<\/p>\n\n\n\n

                NAME STATUS MESSAGE ERROR
                \nscheduler Healthy ok
                \ncontroller-manager Healthy ok
                \netcd-0 Healthy {“health”: “true”} <\/p>\n\n\n\n

                Kubectl get ns #View namespace<\/p>\n\n\n\n

                NAME STATUS AGE
                \ndefault Active 4h41m
                \nkube-public Active 4h41m
                \nkube-system Active 4h41m<\/p>\n\n\n\n

                Kubectl get pods -n kube-system #View pod status<\/p>\n\n\n\n

                NAME READY STATUS RESTARTS AGE
                coredns-78d4cf999f-bszbk 1\/1 Running 0 4h44m
                coredns-78d4cf999f-j68hb 1\/1 Running 0 4h44m
                etcd-master01 1\/1 Running 0 4h43m
                kube-apiserver-master01 1\/1 Running 1 4h43m
                kube-controller-manager-master01 1\/1 Running 2 4h43m
                kube-flannel-ds-amd64-27×59 1\/1 Running 1 126m
                kube-flannel-ds-amd64-5sxgk 1\/1 Running 0 140m
                kube-flannel-ds-amd64-xvrbw 1\/1 Running 0 91m
                kube-proxy-4pbdf 1\/1 Running 0 91m
                kube-proxy-9fmrl 1\/1 Running 0 4h44m
                kube-proxy-nwkl9 1\/1 Running 0 126m
                kube-scheduler-master01 1\/1 Running 2 4h43m<\/p>\n\n\n\n

                <\/p>\n\n\n\n

                Environment preparation master01 node01 node02, connect to the network, modify the hosts file, and confirm that the three hosts resolve each other.<\/p>\n\n\n\n

                Vim \/etc\/hosts<\/p>\n\n\n\n

                127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
                \n::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
                \n192.168.1.201 master01
                \n192.168.1.202 node01
                \n192.168.1.203 node02<\/p>\n\n\n\n

                Host configuration Ali YUM source<\/p>\n\n\n\n

                mv \/etc\/yum.repos.d\/ CentOS -Base.repo \/etc\/yum.repos.d\/CentOS-Base.repo.backup && curl -o \/etc\/yum.repos.d\/CentOS-Base.repo http :\/\/mirrors.aliyun.com\/repo\/Centos-7.repo<\/p>\n\n\n\n

                Start deploying kubernetes<\/p>\n\n\n\n

                1. Install etcd on master01<\/li><\/ol>\n\n\n\n

                  Yum install etcd -y<\/p>\n\n\n\n

                  After the installation is complete, modify the etcd configuration file \/etc\/etcd\/etcd.conf<\/p>\n\n\n\n

                  Vim \/etc\/etcd\/etcd.conf<\/p>\n\n\n\n

                  ETCD_LISTEN_CLIENT_URLS=”http:\/\/0.0.0.0:2379″ <\/p>\n\n\n\n

                  Modify the listening address ETCD_LISTEN_CLIENT_URLS=”http:\/\/192.168.1.201:2379″ #Modify the etcd address as the local address<\/h4>\n\n\n\n

                  Set service startup<\/p>\n\n\n\n

                  Systemctl start etcd && systemctl enable etcd<\/p>\n\n\n\n

                  1. Install kubernetes on all hosts<\/li><\/ol>\n\n\n\n

                    Yum install kubernetes -y<\/p>\n\n\n\n

                    1. Configure the master<\/li><\/ol>\n\n\n\n

                      Vim \/etc\/kubernetes\/config<\/p>\n\n\n\n

                      KUBE_MASTER=”–master=http:\/\/192.168.1.201:8080″ #Modify kube_master address<\/p>\n\n\n\n

                      Vim \/etc\/kubernetes\/apiserver<\/p>\n\n\n\n

                      KUBE_API_ADDRESS=”–insecure-bind-address=0.0.0.0″ <\/p>\n\n\n\n

                      Modify the listening address KUBE_ETCD_SERVERS=”–etcd-servers=http:\/\/192.168.1.201:2379″ #Modify the etcd address<\/h3>\n\n\n\n

                      KUBE_ADMISSION_CONTROL=”–admission-control =NamespaceLifecycle,NamespaceExists,LimitRanger,SecurityContextDeny,ResourceQuota” #Delete authentication parameter ServiceAccount<\/p>\n\n\n\n

                      Set the service startup, start sequence apiserver>scheduler=controller-manager<\/p>\n\n\n\n

                      Systemctl start docker && systemctl enable docker
                      \nsystemctl start kube-apiserver && systemctl enable kube-apiserver
                      \nsystemctl start kube-scheduler && systemctl enable kube-scheduler
                      \nsystemctl start kube-controller-manager && systemctl enable kube-controller-manager<\/p>\n\n\n\n

                      1. Configure node<\/li><\/ol>\n\n\n\n

                        Vim \/etc\/kubernetes\/config<\/p>\n\n\n\n

                        KUBE_MASTER=”–master=http:\/\/192.168.1.201:8080″ #Modify the master address<\/p>\n\n\n\n

                        Vim \/etc\/kubernetes\/kubelet<\/p>\n\n\n\n

                        KUBELET_ADDRESS=”–address=192.168.1.202″ #Modify kubelet address
                        \nKUBELET_HOSTNAME=”–hostname-override=192.168.1.202″ #Modify kubelet hostname
                        \nKUBELET_API_SERVER=”–api-servers=http:\/\/192.168.1.201: 8080″ #Modify apiserver address<\/p>\n\n\n\n

                        Set service startup<\/p>\n\n\n\n

                        Systemctl start docker && systemctl enable docker
                        \nsystemctl start kubelet && systemctl enable kubelet
                        \nsystemctl start kube-proxy && systemctl enable kube-proxy<\/p>\n\n\n\n

                        1. Deployment is complete, check the cluster status<\/li><\/ol>\n\n\n\n

                          Kubectl get nodes<\/p>\n\n\n

                          [root@node02 kubernetes]<\/p>\n\n\n\n

                          # kubectl -s http:\/\/192.168.1.201:8080 get nodes -o wide
                          \nNAME STATUS AGE EXTERNAL-IP
                          \n192.168.1.202 Ready 29s
                          \n192.168.1.203 Ready 16m \n<\/p>\n\n\n\n

                          1. Install flannel on all hosts<\/li><\/ol>\n\n\n\n

                            Yum install flannel -y<\/p>\n\n\n\n

                            Vim \/etc\/sysconfig\/flanneld<\/p>\n\n\n\n

                            FLANNEL_ETCD_ENDPOINTS=”http:\/\/192.168.1.201:2379″ #Modify the etcd address<\/p>\n\n\n\n

                            Etcdctl mk \/atomic.io\/network\/config ‘{ “Network”: “172.16.0.0\/16” }’ #Set the container network in the etcd host<\/p>\n\n\n\n

                            Master host restart service<\/p>\n\n\n\n

                            Systemctl start flanneld && systemctl enable flanneld
                            \nsystemctl restart docker
                            \nsystemctl restart kube-apiserver
                            \nsystemctl restart kube-scheduler
                            \nsystemctl restart kube-controller-manager<\/p>\n\n\n\n

                            Node host restart service<\/p>\n\n\n\n

                            Systemctl start flanneld && systemctl enable flanneld
                            \nsystemctl restart docker
                            \nsystemctl restart kubelet
                            \nsystemctl restart kube-proxy<\/p>\n","protected":false},"excerpt":{"rendered":"\n

                            Kubeadm quickly builds a k8s cluster<\/p>\n

                            surroundings<\/p>\n

                            Master01: 192.168.1.110 (minimum 2 core CPU)<\/p>\n

                            node01: 192.168.1.100<\/p>\n

                            planning<\/p>\n

                            Services network: 10.96.0.0\/12<\/p>\n

                            Pod network: 10.244.0.0\/16<\/p>\n

                            Configure hosts to resolve each host <\/p>\n

                            vim \/etc\/hosts<\/p>\n

                            127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 192.168.1.110 master01 192.168.1.100 node01<\/p>\n

                            Synchronize each host time <\/p>\n

                            yum install -y ntpdate ntpdate time.windows.com<\/p>\n

                            […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[92],"tags":[],"_links":{"self":[{"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/posts\/7798"}],"collection":[{"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=7798"}],"version-history":[{"count":3,"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/posts\/7798\/revisions"}],"predecessor-version":[{"id":7802,"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/posts\/7798\/revisions\/7802"}],"wp:attachment":[{"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=7798"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=7798"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=7798"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}