详情

首页手游攻略 K8s 1.15.0 安装记录

K8s 1.15.0 安装记录

佚名 2026-09-02 09:46:56

K8s 1.15 集群部署

环境

hostnameipsystem
master192.168.33.10CentOS7
node1192.168.33.11CentOS7
node2192.168.33.12CentOS7
node3192.168.33.13CentOS7
node4192.168.33.14CentOS7
node5192.168.33.15CentOS7

所有节点上操作

[root@master install]# cat preENV.sh#!/bin/bash# 关闭防火墙systemctl stop firewalld && systemctl disable firewalld# 关闭SELINUXsetenforce 0 && sed -i "s/SELINUX=enforcing/SELINUX=disabled/g" /etc/selinux/config# 关闭Swapswapoff -a && sed -i "s//dev/mapper/centos-swap/#/dev/mapper/centos-swap/g" /etc/fstab[root@master ~]# vim /etc/sysctl.d/k8s.conf[root@master ~]# cat /etc/sysctl.d/k8s.confnet.bridge.bridge-nf-call-ip6tables = 1net.bridge.bridge-nf-call-iptables = 1net.ipv4.ip_forward = 1[root@master ~]# modprobe br_netfilter && sysctl -p /etc/sysctl.d/k8s.confnet.bridge.bridge-nf-call-ip6tables = 1net.bridge.bridge-nf-call-iptables = 1net.ipv4.ip_forward = 1[root@master ~]# wget -O /etc/yum.repos.d/CentOS7-Aliyun.repo http://mirrors.aliyun.com/repo/Centos-7.repo--2019-06-30 04:26:32--http://mirrors.aliyun.com/repo/Centos-7.repoResolving mirrors.aliyun.com (mirrors.aliyun.com)... 116.177.250.229, 116.177.250.233, 60.28.226.4, ...Connecting to mirrors.aliyun.com (mirrors.aliyun.com)|116.177.250.229|:80... connected.HTTP request sent, awaiting response... 200 OKLength: 2523 (2.5K) [application/octet-stream]Saving to: ‘/etc/yum.repos.d/CentOS7-Aliyun.repo’100%[============================================================================>] 2,523 --.-K/s in 0s2019-06-30 04:26:32 (296 MB/s) - ‘/etc/yum.repos.d/CentOS7-Aliyun.repo’ saved [2523/2523]root@master ~]# sudo yum install -y yum-utils device-mapper-persistent-data lvm2[root@master ~]# sudo yum-config-manager --add-repo https://download.docker.com/linux/centos/docker-ce.repo[root@master ~]# yum install docker-ce -y[root@master ~]# systemctl enable docker && systemctl start dockerCreated symlink from /etc/systemd/system/multi-user.target.wants/docker.service to /usr/lib/systemd/system/docker.service.[root@master ~]# mkdir -p /etc/docker[root@master ~]# sudo tee /etc/docker/daemon.json <<-'EOF'{"registry-mirrors": ["https://gmjjwogo.mirror.aliyuncs.com"],"exec-opts": ["native.cgroupdriver=systemd"]}EOF{"registry-mirrors": ["https://gmjjwogo.mirror.aliyuncs.com"],"exec-opts": ["native.cgroupdriver=systemd"]}[root@master ~]# sudo systemctl daemon-reload && sudo systemctl restart docker[root@master ~]# docker info |grep CgroupCgroup Driver: systemd[root@master ~]# # kube-proxy开启ipvs的前置条件[root@master ~]# cat > /etc/sysconfig/modules/ipvs.modules <<EOF#!/bin/bashmodprobe -- ip_vsmodprobe -- ip_vs_rrmodprobe -- ip_vs_wrrmodprobe -- ip_vs_shmodprobe -- nf_conntrack_ipv4EOF[root@master ~]# chmod 755 /etc/sysconfig/modules/ipvs.modules && bash /etc/sysconfig/modules/ipvs.modules && lsmod | grep -e ip_vs -e nf_conntrack_ipv4ip_vs_sh 126880ip_vs_wrr126970ip_vs_rr 126000ip_vs 1454976 ip_vs_rr,ip_vs_sh,ip_vs_wrrnf_conntrack_ipv4150532nf_defrag_ipv4 127291 nf_conntrack_ipv4nf_conntrack1330957 ip_vs,nf_nat,nf_nat_ipv4,xt_conntrack,nf_nat_masquerade_ipv4,nf_conntrack_netlink,nf_conntrack_ipv4libcrc32c126444 xfs,ip_vs,nf_nat,nf_conntrack[root@master ~]# # 安装kubernetes初始化工具[root@master ~]# # 使用阿里云的kubernetes源[root@master ~]# cat <<EOF > /etc/yum.repos.d/kubernetes.repo[kubernetes]name=Kubernetesbaseurl=https://mirrors.aliyun.com/kubernetes/yum/repos/kubernetes-el7-x86_64/enabled=1gpgcheck=1repo_gpgcheck=1gpgkey=https://mirrors.aliyun.com/kubernetes/yum/doc/yum-key.gpg https://mirrors.aliyun.com/kubernetes/yum/doc/rpm-package-key.gpgEOF[root@master ~]# # 安装k8s 工具 1.15版本[root@master ~]# yum install -y kubelet kubeadm kubectlInstalled:kubeadm.x86_64 0:1.15.0-0kubectl.x86_64 0:1.15.0-0kubelet.x86_64 0:1.15.0-0Dependency Installed:conntrack-tools.x86_64 0:1.4.4-4.el7 cri-tools.x86_64 0:1.12.0-0kubernetes-cni.x86_64 0:0.7.5-0libnetfilter_cthelper.x86_64 0:1.0.0-9.el7libnetfilter_cttimeout.x86_64 0:1.0.0-6.el7libnetfilter_queue.x86_64 0:1.0.2-2.el7_2socat.x86_64 0:1.7.3.2-2.el7Complete![root@master ~]# # 启动 kubelet[root@master ~]# systemctl enable kubelet && systemctl start kubeletCreated symlink from /etc/systemd/system/multi-user.target.wants/kubelet.service to /usr/lib/systemd/system/kubelet.service.[root@master ~]#

主节点操作

[root@master install]# vim installK8sMasterImage.sh[root@master install]# cat installK8sMasterImage.sh#!/bin/bashset -eKUBE_VERSION=v1.15.0KUBE_PAUSE_VERSION=3.1ETCD_VERSION=3.3.10CORE_DNS_VERSION=1.3.1GCR_URL=k8s.gcr.ioALIYUN_URL=registry.cn-hangzhou.aliyuncs.com/google_containersimages=(kube-proxy:${KUBE_VERSION}kube-scheduler:${KUBE_VERSION}kube-controller-manager:${KUBE_VERSION}kube-apiserver:${KUBE_VERSION}pause:${KUBE_PAUSE_VERSION}etcd:${ETCD_VERSION}coredns:${CORE_DNS_VERSION})for imageName in ${images[@]} ; dodocker pull $ALIYUN_URL/$imageNamedocker tag$ALIYUN_URL/$imageName $GCR_URL/$imageNamedocker rmi $ALIYUN_URL/$imageNamedone[root@master install]# chmod  x installK8sMasterImage.sh && ./installK8sMasterImage.shroot@master install]# kubeadm init --kubernetes-version=v1.15.0 --apiserver-advertise-address=192.168.33.10 --pod-network-cidr=10.244.0.0/16[init] Using Kubernetes version: v1.15.0[preflight] Running pre-flight checks[WARNING Hostname]: hostname "master" could not be reached[WARNING Hostname]: hostname "master": lookup master on 10.0.2.3:53: no such host[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 "front-proxy-ca" certificate and key[certs] Generating "front-proxy-client" certificate and key[certs] Generating "ca" certificate and key[certs] Generating "apiserver" certificate and key[certs] apiserver serving cert is signed for DNS names [master kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 192.168.33.10][certs] Generating "apiserver-kubelet-client" certificate and key[certs] Generating "etcd/ca" certificate and key[certs] Generating "etcd/server" certificate and key[certs] etcd/server serving cert is signed for DNS names [master localhost] and IPs [192.168.33.10 127.0.0.1 ::1][certs] Generating "etcd/healthcheck-client" certificate and key[certs] Generating "apiserver-etcd-client" certificate and key[certs] Generating "etcd/peer" certificate and key[certs] etcd/peer serving cert is signed for DNS names [master localhost] and IPs [192.168.33.10 127.0.0.1 ::1][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 26.502984 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 master as control-plane by adding the label "node-role.kubernetes.io/master=''"[mark-control-plane] Marking the node master as control-plane by adding the taints [node-role.kubernetes.io/master:NoSchedule][bootstrap-token] Using token: z1uxfl.z8l2uo9v8x3dtdcu[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-proxyYour Kubernetes control-plane has initialized successfully!To start using your cluster, you need to run the following as a regular user:mkdir -p $HOME/.kubesudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/configsudo chown $(id -u):$(id -g) $HOME/.kube/configYou 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.33.10:6443 --token z1uxfl.z8l2uo9v8x3dtdcu --discovery-token-ca-cert-hash sha256:5c725b5b384221d25aed03a02a142fe2442d76f6362673b72f349abffb18b6f2[root@master ~]#[root@master ~]# mkdir -p $HOME/.kube[root@master ~]# sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config[root@master ~]# sudo chown $(id -u):$(id -g) $HOME/.kube/config[root@master ~]# kubectl get pod -n kube-system -owideNAME READY STATUSRESTARTS AGE IPNODE NOMINATED NODE READINESS GATEScoredns-5c98db65d4-9g7dj 0/1 Pending 039s <none><none> <none> <none>coredns-5c98db65d4-f6h7d 0/1 Pending 039s <none><none> <none> <none>etcd-master1/1 Running 057s 10.0.2.15 master <none> <none>kube-apiserver-master1/1 Running 057s 10.0.2.15 master <none> <none>kube-controller-manager-master 1/1 Running 057s 10.0.2.15 master <none> <none>kube-proxy-n9tql 1/1 Running 039s 10.0.2.15 master <none> <none>kube-scheduler-master1/1 Running 057s 10.0.2.15 master <none> <none>[root@master ~]# wget https://raw.githubusercontent.com/coreos/flannel/62e44c867a2846fefb68bd5f178daf4da3095ccb/Documentation/kube-flannel.yml--2019-06-30 06:47:53--https://raw.githubusercontent.com/coreos/flannel/62e44c867a2846fefb68bd5f178daf4da3095ccb/Documentation/kube-flannel.ymlResolving raw.githubusercontent.com (raw.githubusercontent.com)... 151.101.228.133Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|151.101.228.133|:443... connected.HTTP request sent, awaiting response... 200 OKLength: 12306 (12K) [text/plain]Saving to: ‘kube-flannel.yml’100%[==============================================================================================>] 12,30651.3KB/s in 0.2s2019-06-30 06:47:57 (51.3 KB/s) - ‘kube-flannel.yml’ saved [12306/12306][root@master install]# lltotal 24-rwxr-xr-x. 1 root root 580 Jun 30 05:21 installK8sMasterImage.sh-rw-r--r--. 1 root root 12306 Jun 30 05:26 kube-flannel.yml-rwxr-xr-x. 1 root root 294 Jun 30 04:20 preENV.sh[root@master install]# kubectl apply -f kube-flannel.ymlpodsecuritypolicy.extensions/psp.flannel.unprivileged createdclusterrole.rbac.authorization.k8s.io/flannel createdclusterrolebinding.rbac.authorization.k8s.io/flannel createdserviceaccount/flannel createdconfigmap/kube-flannel-cfg createddaemonset.extensions/kube-flannel-ds-amd64 createddaemonset.extensions/kube-flannel-ds-arm64 createddaemonset.extensions/kube-flannel-ds-arm createddaemonset.extensions/kube-flannel-ds-ppc64le createddaemonset.extensions/kube-fla[root@master ~]# kubectl get pod -n kube-system -owideNAME READY STATUSRESTARTS AGE IP NODE NOMINATED NODE READINESS GATEScoredns-5c98db65d4-9g7dj 1/1 Running 05m42s 10.244.0.3 master <none> <none>coredns-5c98db65d4-f6h7d 1/1 Running 05m42s 10.244.0.2 master <none> <none>etcd-master1/1 Running 06m10.0.2.15master <none> <none>kube-apiserver-master1/1 Running 06m10.0.2.15master <none> <none>kube-controller-manager-master 1/1 Running 06m10.0.2.15master <none> <none>kube-flannel-ds-amd64-lbprc1/1 Running 084s 10.0.2.15master <none> <none>kube-proxy-n9tql 1/1 Running 05m42s 10.0.2.15master <none> <none>kube-scheduler-master1/1 Running 06m10.0.2.15master <none> <none>[root@master install]# # 查看当前集群状态[root@master ~]# kubectl get node -ANAME STATUS ROLESAGE VERSIONmaster Readymaster 6m29s v1.15.0[root@master ~]#

各 Node 节点上处理

[root@node2 install]# vim installK8sNodeImage.sh[root@node5 install]# cat installK8sNodeImage.sh#!/bin/bashset -eKUBE_VERSION=v1.15.0KUBE_PAUSE_VERSION=3.1CORE_DNS_VERSION=1.3.1GCR_URL=k8s.gcr.ioALIYUN_URL=registry.cn-hangzhou.aliyuncs.com/google_containersimages=(kube-proxy:${KUBE_VERSION}pause:${KUBE_PAUSE_VERSION}coredns:${CORE_DNS_VERSION})for imageName in ${images[@]} ; dodocker pull $ALIYUN_URL/$imageNamedocker tag$ALIYUN_URL/$imageName $GCR_URL/$imageNamedocker rmi $ALIYUN_URL/$imageNamedone[root@node1 ~]# chmod  x installK8sNodeImage.sh&& ./installK8sNodeImage.shv1.15.0: Pulling from google_containers/kube-proxy39fafc05754f: Pull completedb3f71d0eb90: Pull completeb593bfa65f6f: Pull completeDigest: sha256:7b94921f1c64876d3663698ade724fce79b417b32f0e1053976ca68a18fc0cbaStatus: Downloaded newer image for registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy:v1.15.0Untagged: registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy:v1.15.0Untagged: registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy@sha256:7b94921f1c64876d3663698ade724fce79b417b32f0e1053976ca68a18fc0cba3.1: Pulling from google_containers/pausecf9202429979: Pull completeDigest: sha256:759c3f0f6493093a9043cc813092290af69029699ade0e3dbe024e968fcb7ccaStatus: Downloaded newer image for registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.1Untagged: registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.1Untagged: registry.cn-hangzhou.aliyuncs.com/google_containers/pause@sha256:759c3f0f6493093a9043cc813092290af69029699ade0e3dbe024e968fcb7cca1.3.1: Pulling from google_containers/corednse0daa8927b68: Pull complete3928e47de029: Pull completeDigest: sha256:638adb0319813f2479ba3642bbe37136db8cf363b48fb3eb7dc8db634d8d5a5bStatus: Downloaded newer image for registry.cn-hangzhou.aliyuncs.com/google_containers/coredns:1.3.1Untagged: registry.cn-hangzhou.aliyuncs.com/google_containers/coredns:1.3.1Untagged: registry.cn-hangzhou.aliyuncs.com/google_containers/coredns@sha256:638adb0319813f2479ba3642bbe37136db8cf363b48fb3eb7dc8db634d8d5a5b[root@node1 ~]#[root@node5 install]# # Node 加入集群[root@node1 install]# kubeadm join 192.168.33.10:6443 --token sofcoc.j1it9gvn4uxpduo5 > --discovery-token-ca-cert-hash sha256:3a9b79bd92f66a6284322ade27732932888c0f99884596d5f2c9a03d272e475b[preflight] Running pre-flight checks[preflight] Reading configuration from the cluster...[preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -oyaml'[kubelet-start] Downloading configuration for the kubelet from the "kubelet-config-1.15" ConfigMap in the kube-system namespace[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"[kubelet-start] Activating the kubelet service[kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap...This node has joined the cluster:* Certificate signing request was sent to apiserver and a response was received.* The Kubelet was informed of the new secure connection details.Run 'kubectl get nodes' on the control-plane to see this node join the cluster.[root@node1 install]#

master 节点操作

[root@master ~]# #将master节点也作为工作节点进行pod部署[root@master ~]# kubectl taint nodes master node-role.kubernetes.io/master-node/master untainted

打label

[root@master temp]# kubectl label node master nodename=masternode/master labeled[root@master temp]# kubectl label node node1 nodename=node1node/node1 labeled[root@master temp]# kubectl label node node2 nodename=node2node/node2 labeled[root@master temp]# kubectl label node node3 nodename=node3node/node3 labeled[root@master temp]# kubectl label node node4 nodename=node4node/node4 labeled[root@master temp]# kubectl label node node5 nodename=node5node/node5 labeled

测试

vim nginx-deployment.yaml
apiVersion: apps/v1kind: Deploymentmetadata:name: nginx-deploymentlabels:app: nginxspec:replicas: 1selector:matchLabels:app: nginxtemplate:metadata:labels:app: nginxspec:containers:- name: nginximage: nginx:1.7.9imagePullPolicy: IfNotPresentports:- containerPort: 80name: webprotocol: TCPnodeSelector:nodename: master---apiVersion: v1kind: Servicemetadata:name: nginx-servicelabels:app: nginxspec:ports:- port: 80targetPort: 8080name: webselector:app-name: nginx---apiVersion: extensions/v1beta1kind: Ingressmetadata:name: nginxnamespace: defaultspec:rules:- host: c4.k8s.comhttp:paths:- path: /nginxbackend:serviceName: nginx-serviceservicePort: 8080
[root@master temp]# kubectl apply -f nginx-deployment.yamldeployment.apps/nginx-deployment createdservice/nginx-service createdingress.extensions/nginx created[root@master temp]# kubectl get service/nginx-serviceNAMETYPECLUSTER-IPEXTERNAL-IP PORT(S) AGEnginx-service ClusterIP 10.100.2.78 <none>80/TCP38s[root@master temp]# kubectl get ingNAMEHOSTSADDRESS PORTS AGEnginx c4.k8s.com 804m5s[root@master temp]# wget c4.k8s.com--2019-06-30 07:12:18--http://c4.k8s.com/Resolving c4.k8s.com (c4.k8s.com)... 208.73.211.177, 208.73.210.202, 208.73.211.165, ...Connecting to c4.k8s.com (c4.k8s.com)|208.73.211.177|:80... connected.HTTP request sent, awaiting response... 302 Found : Moved TemporarilyLocation: http://1223.dragonparking.com/?site=c4.k8s.com [following]--2019-06-30 07:12:19--http://1223.dragonparking.com/?site=c4.k8s.comResolving 1223.dragonparking.com (1223.dragonparking.com)... 46.51.238.1Connecting to 1223.dragonparking.com (1223.dragonparking.com)|46.51.238.1|:80... connected.HTTP request sent, awaiting response... 302 Moved TemporarilyLocation: http://park.zunmi.cn/?acct=1223&site=c4.k8s.com [following]--2019-06-30 07:12:21--http://park.zunmi.cn/?acct=1223&site=c4.k8s.comResolving park.zunmi.cn (park.zunmi.cn)... 52.197.205.2Connecting to park.zunmi.cn (park.zunmi.cn)|52.197.205.2|:80... connected.HTTP request sent, awaiting response... 200 OKLength: 1020 [text/html]Saving to: ‘index.html’100%[======================================================================================================================================>] 1,020 --.-K/s in 0s2019-06-30 07:12:22 (93.5 MB/s) - ‘index.html’ saved [1020/1020][root@master temp]# lltotal 8-rw-r--r--. 1 root root 1020 May6 23:28 index.html-rw-r--r--. 1 root root908 Jun 30 07:07 nginx-deployment.yaml[root@master temp]# kubectl delete -f nginx-deployment.yamldeployment.apps "nginx-deployment" deletedservice "nginx-service" deletedingress.extensions "nginx" deleted
相关资讯
点击查看更多
游戏推荐
推荐专题
热门阅读
推荐下载