我用3台机器搭建k8s集群

192.168.10.40 为master

192.168.10.42  192.168.10.43为node

前提是必须每台机器都装了docker.可参考以前的文章。

step 1: 3台机器上分别执行：

1. swapoff -a  只是临时关闭

2. systemctl stop firewalld  关闭防火墙

3. 关闭selinux：sed -i 's/enforcing/disabled/' /etc/selinux/config (永久关闭)

4. 关闭selinux（临时关闭）setenforce 0

5. cat > /etc/yum.repos.d/kubernetes.repo << EOF

   [kubernetes]

   name=Kubernetes

   baseurl=https://mirrors.aliyun.com/kubernetes/yum/repos/kubernetes-el7-x86_64

   enabled=1

   gpgcheck=0

   repo_gpgcheck=0

   gpgkey=https://mirrors.aliyun.com/kubernetes/yum/doc/yum-key.gpg https://mirrors.aliyun.com/kubernetes/yum/doc/rpm-package-key.gpg

   EOF

6. 

7. yum install -y kubelet-1.15.0 kubeadm-1.15.0 kubectl-1.15.0

step 2: 只在master节点执行初始化命令

[root@database-16 ~]#  kubeadm init \

>   --apiserver-advertise-address=192.168.10.40 \

>   --image-repository registry.aliyuncs.com/google_containers \

>   --kubernetes-version v1.15.0 \

>   --service-cidr=10.1.0.0/16 \

>   --pod-network-cidr=10.244.0.0/16

[init] Using Kubernetes version: v1.15.0

[preflight] Running pre-flight checks

[WARNING Service-Docker]: docker service is not enabled, please run 'systemctl enable docker.service'

[WARNING IsDockerSystemdCheck]: detected "cgroupfs" as the Docker cgroup driver. The recommended driver is "systemd". Please follow the guide at https://kubernetes.io/docs/setup/cri/

[preflight] Pulling images required for setting up a Kubernetes cluster

[preflight] This might take a minute or two, depending on the speed of your internet connection

[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'

 

------------------------------

[root@database-16 ~]# systemctl enable docker.service

Created symlink from /etc/systemd/system/multi-user.target.wants/docker.service to /usr/lib/systemd/system/docker.service.

[root@database-16 ~]#  kubeadm init   --apiserver-advertise-address=192.168.10.40   --image-repository registry.aliyuncs.com/google_containers   --kubernetes-version v1.15.0   --service-cidr=10.1.0.0/16   --pod-network-cidr=10.244.0.0/16

[init] Using Kubernetes version: v1.15.0

[preflight] Running pre-flight checks

[WARNING IsDockerSystemdCheck]: detected "cgroupfs" as the Docker cgroup driver. The recommended driver is "systemd". Please follow the guide at https://kubernetes.io/docs/setup/cri/

[preflight] Pulling images required for setting up a Kubernetes cluster

[preflight] This might take a minute or two, depending on the speed of your internet connection

[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'

[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"

[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"

[kubelet-start] Activating the kubelet service

[certs] Using certificateDir folder "/etc/kubernetes/pki"

[certs] Generating "ca" certificate and key

[certs] Generating "apiserver" certificate and key

[certs] apiserver serving cert is signed for DNS names [database-16 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.1.0.1 192.168.10.40]

[certs] Generating "apiserver-kubelet-client" certificate and key

[certs] Generating "front-proxy-ca" certificate and key

[certs] Generating "front-proxy-client" certificate and key

[certs] Generating "etcd/ca" certificate and key

[certs] Generating "etcd/healthcheck-client" certificate and key

[certs] Generating "etcd/server" certificate and key

[certs] etcd/server serving cert is signed for DNS names [database-16 localhost] and IPs [192.168.10.40 127.0.0.1 ::1]

[certs] Generating "etcd/peer" certificate and key

[certs] etcd/peer serving cert is signed for DNS names [database-16 localhost] and IPs [192.168.10.40 127.0.0.1 ::1]

[certs] Generating "apiserver-etcd-client" certificate and key

[certs] Generating "sa" key and public key

[kubeconfig] Using kubeconfig folder "/etc/kubernetes"

[kubeconfig] Writing "admin.conf" kubeconfig file

[kubeconfig] Writing "kubelet.conf" kubeconfig file

[kubeconfig] Writing "controller-manager.conf" kubeconfig file

[kubeconfig] Writing "scheduler.conf" kubeconfig file

[control-plane] Using manifest folder "/etc/kubernetes/manifests"

[control-plane] Creating static Pod manifest for "kube-apiserver"

[control-plane] Creating static Pod manifest for "kube-controller-manager"

[control-plane] Creating static Pod manifest for "kube-scheduler"

[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"

[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s

[apiclient] All control plane components are healthy after 37.504898 seconds

[upload-config] Storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace

[kubelet] Creating a ConfigMap "kubelet-config-1.15" in namespace kube-system with the configuration for the kubelets in the cluster

[upload-certs] Skipping phase. Please see --upload-certs

[mark-control-plane] Marking the node database-16 as control-plane by adding the label "node-role.kubernetes.io/master=''"

[mark-control-plane] Marking the node database-16 as control-plane by adding the taints [node-role.kubernetes.io/master:NoSchedule]

[bootstrap-token] Using token: y5khoj.hhpjag97mqz0b6gv

[bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles

[bootstrap-token] configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials

[bootstrap-token] configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token

[bootstrap-token] configured RBAC rules to allow certificate rotation for all node client certificates in the cluster

[bootstrap-token] Creating the "cluster-info" ConfigMap in the "kube-public" namespace

[addons] Applied essential addon: CoreDNS

[addons] Applied essential addon: kube-proxy

 

Your Kubernetes control-plane has initialized successfully!

 

To start using your cluster, you need to run the following as a regular user:

 

  mkdir -p $HOME/.kube

  sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config

  sudo chown $(id -u):$(id -g) $HOME/.kube/config

 

You should now deploy a pod network to the cluster.

Run "kubectl apply -f [podnetwork].yaml" with one of the options listed at:

  https://kubernetes.io/docs/concepts/cluster-administration/addons/

 

Then you can join any number of worker nodes by running the following on each as root:

 

kubeadm join 192.168.10.40:6443 --token y5khoj.hhpjag97mqz0b6gv \

    --discovery-token-ca-cert-hash

 

sha256:641c4bd07f44f6a2c852aea3634e4409d848d0e0013a9299119bc9417a5ec6ee

由于好多软件需要到国外raw.githubusercontent.com下载，配置了*IP.不然无法下载

红色打印命令需要另外2节点执行，然后把2节点加入集群。

step 3:  在3台机器上安装，Flannel 安装部署

a.先master执行。

[root@database-16 ~]# docker pull lizhenliang/flannel:v0.11.0-amd64

v0.11.0-amd64: Pulling from lizhenliang/flannel

Digest: sha256:bd76b84c74ad70368a2341c2402841b75950df881388e43fc2aca000c546653a

Status: Downloaded newer image for lizhenliang/flannel:v0.11.0-amd64

[root@database-16 ~]# kubectl apply -f kube-flannel.yml

clusterrole.rbac.authorization.k8s.io/flannel unchanged

clusterrolebinding.rbac.authorization.k8s.io/flannel unchanged

serviceaccount/flannel unchanged

configmap/kube-flannel-cfg unchanged

daemonset.extensions/kube-flannel-ds-amd64 configured

daemonset.extensions/kube-flannel-ds-arm64 unchanged

daemonset.extensions/kube-flannel-ds-arm unchanged

daemonset.extensions/kube-flannel-ds-ppc64le unchanged

daemonset.extensions/kube-flannel-ds-s390x unchanged

[root@database-16 ~]# kubectl  get pod -n kube-system

NAME                                  READY   STATUS    RESTARTS   AGE

coredns-bccdc95cf-hckvc               1/1     Running   0          64m

coredns-bccdc95cf-zlcnp               1/1     Running   0          64m

etcd-database-16                      1/1     Running   0          63m

kube-apiserver-database-16            1/1     Running   0          63m

kube-controller-manager-database-16   1/1     Running   0          63m

kube-flannel-ds-amd64-qm2t8           1/1     Running   0          31m

kube-proxy-6tk2h                      1/1     Running   0          64m

kube-scheduler-database-16            1/1     Running   0          63m

 

b. 拷贝admin.conf到另外2个节点

c. 另外2节点安装Flannel

 

step 4: 安装管理后台

   kubectl create  serviceaccount dashboard-admin -n kube-system

  kubectl create clusterrolebinding dashboard-admin --clusterrole=cluster-admin --serviceaccount=kube-system:dashboard-admin