-
kubernetes快速部署
1.2 kubernetes简介
kubernetes，是一个全新的基于容器技术的分布式架构领先方案，是谷歌严格保密十几年的秘密武器----Borg系统的一个开源版本，于2014年9月发布第一个版本，2015年7月发布第一个正式版本。
kubernetes的本质是一组服务器集群，它可以在集群的每个节点上运行特定的程序，来对节点中的容器进行管理。目的是实现资源管理的自动化，主要提供了如下的主要功能：
- 自我修复：一旦某一个容器崩溃，能够在1秒中左右迅速启动新的容器
- 弹性伸缩：可以根据需要，自动对集群中正在运行的容器数量进行调整
- 服务发现：服务可以通过自动发现的形式找到它所依赖的服务
- 负载均衡：如果一个服务起动了多个容器，能够自动实现请求的负载均衡
- 版本回退：如果发现新发布的程序版本有问题，可以立即回退到原来的版本
- 存储编排：可以根据容器自身的需求自动创建存储卷
1.3 kubernetes组件
一个kubernetes集群主要是由**控制节点(master)、工作节点(node)**构成，每个节点上都会安装不同的组件。
master：集群的控制平面，负责集群的决策 ( 管理 )
ApiServer : 资源操作的唯一入口，接收用户输入的命令，提供认证、授权、API注册和发现等机制
Scheduler : 负责集群资源调度，按照预定的调度策略将Pod调度到相应的node节点上
ControllerManager : 负责维护集群的状态，比如程序部署安排、故障检测、自动扩展、滚动更新等
Etcd ：负责存储集群中各种资源对象的信息
node：集群的数据平面，负责为容器提供运行环境 ( 干活 )
Kubelet : 负责维护容器的生命周期，即通过控制docker，来创建、更新、销毁容器
KubeProxy : 负责提供集群内部的服务发现和负载均衡
Docker : 负责节点上容器的各种操作
下面，以部署一个nginx服务来说明kubernetes系统各个组件调用关系：- 首先要明确，一旦kubernetes环境启动之后，master和node都会将自身的信息存储到etcd数据库中
- 一个nginx服务的安装请求会首先被发送到master节点的apiServer组件
- apiServer组件会调用scheduler组件来决定到底应该把这个服务安装到哪个node节点上
- 在此时，它会从etcd中读取各个node节点的信息，然后按照一定的算法进行选择，并将结果告知apiServer
- apiServer调用controller-manager去调度Node节点安装nginx服务
- kubelet接收到指令后，会通知docker，然后由docker来启动一个nginx的pod
- pod是kubernetes的最小操作单元，容器必须跑在pod中至此，
- 一个nginx服务就运行了，如果需要访问nginx，就需要通过kube-proxy来对pod产生访问的代理
1.4 kubernetes概念
Master：集群控制节点，每个集群需要至少一个master节点负责集群的管控
Node：工作负载节点，由master分配容器到这些node工作节点上，然后node节点上的docker负责容器的运行
Pod：kubernetes的最小控制单元，容器都是运行在pod中的，一个pod中可以有1个或者多个容器
Controller：控制器，通过它来实现对pod的管理，比如启动pod、停止pod、伸缩pod的数量等等
Service：pod对外服务的统一入口，下面可以维护者同一类的多个pod
Label：标签，用于对pod进行分类，同一类pod会拥有相同的标签
NameSpace：命名空间，用来隔离pod的运行环境
2.安装要求
在开始之前，部署Kubernetes集群机器需要满足以下几个条件：
-至少3台机器，操作系统 CentOS7+
- 硬件配置：2GB或更多RAM，2个CPU或更多CPU，硬盘20GB或更多
- 集群中所有机器之间网络互通
- 可以访问外网，需要拉取镜像
- 禁止swap分区
环境
名称 IP 系统 k8s-master 192.168.106.16 centos8 k8s-node1 192.168.106.20 centos8 k8s-node2 192.168.106.21 centos8 //以下的操作所有主机都要做 //关闭所有主机的防火墙，selinux [root@k8s-master ~]# systemctl disable --now firewalld Removed /etc/systemd/system/multi-user.target.wants/firewalld.service. Removed /etc/systemd/system/dbus-org.fedoraproject.FirewallD1.service. [root@k8s-master ~]# setenforce 0 [root@k8s-master ~]# vim /etc/selinux/config [root@k8s-node1 ~]# systemctl disable --now firewalld Removed /etc/systemd/system/multi-user.target.wants/firewalld.service. Removed /etc/systemd/system/dbus-org.fedoraproject.FirewallD1.service. [root@k8s-node1 ~]# setenforce 0 [root@k8s-node1 ~]# vim /etc/selinux/config [root@k8s-node2 ~]# systemctl disable --now firewalld Removed /etc/systemd/system/multi-user.target.wants/firewalld.service. Removed /etc/systemd/system/dbus-org.fedoraproject.FirewallD1.service. [root@k8s-node2 ~]# setenforce 0 [root@k8s-node2 ~]# vim /etc/selinux/config //关闭所有主机的swap分区： # vim /etc/fstab //注释掉swap分区 [root@k8s-master ~]# free -m total used free shared buff/cache available Mem: 3752 556 2656 10 539 2956 Swap: 4051 0 4051 [root@k8s-master ~]# vim /etc/fstab [root@k8s-node1 ~]# free -m total used free shared buff/cache available Mem: 1800 550 728 10 521 1084 Swap: 2047 0 2047 [root@k8s-node1 ~]# vim /etc/fstab [root@k8s-node2 ~]# free -m total used free shared buff/cache available Mem: 1800 559 711 10 529 1072 Swap: 2047 0 2047 [root@k8s-node2 ~]# vim /etc/fstab //在master添加hosts： [root@k8s-master ~]# cat >> /etc/hosts << EOF 192.168.106.16 k8s-master 192.168.106.20 k8s-node1 192.168.106.21 k8s-node2 EOF [root@k8s-node1 ~]# cat >> /etc/hosts << EOF > 192.168.106.16 k8s-master > 192.168.106.20 k8s-node1 > 192.168.106.21 k8s-node2 > EOF [root@k8s-node2 ~]# cat >> /etc/hosts << EOF > 192.168.106.16 k8s-master > 192.168.106.20 k8s-node1 > 192.168.106.21 k8s-node2 > EOF [root@k8s-master ~]# ping k8s-master //测试 PING k8s-master (192.168.106.16) 56(84) bytes of data. 64 bytes from k8s-master (192.168.106.16): icmp_seq=1 ttl=64 time=0.072 ms 64 bytes from k8s-master (192.168.106.16): icmp_seq=2 ttl=64 time=0.080 ms ^C --- k8s-master ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 41ms rtt min/avg/max/mdev = 0.072/0.076/0.080/0.004 ms [root@k8s-master ~]# ping k8s-node1 PING k8s-node1 (192.168.106.20) 56(84) bytes of data. 64 bytes from k8s-node1 (192.168.106.20): icmp_seq=1 ttl=64 time=0.512 ms 64 bytes from k8s-node1 (192.168.106.20): icmp_seq=2 ttl=64 time=0.285 ms ^C [root@k8s-master ~]# ping k8s-node2 PING k8s-node2 (192.168.106.21) 56(84) bytes of data. 64 bytes from k8s-node2 (192.168.106.21): icmp_seq=1 ttl=64 time=1.60 ms 64 bytes from k8s-node2 (192.168.106.21): icmp_seq=2 ttl=64 time=0.782 ms 64 bytes from k8s-node2 (192.168.106.21): icmp_seq=3 ttl=64 time=1.32 ms //将桥接的IPv4流量传递到iptables的链： [root@k8s-master ~]# cat > /etc/sysctl.d/k8s.conf << EOF > net.bridge.bridge-nf-call-ip6tables = 1 > net.bridge.bridge-nf-call-iptables = 1 > EOF [root@k8s-master ~]# sysctl --system //生效 #省略过程 * Applying /etc/sysctl.d/99-sysctl.conf ... * Applying /etc/sysctl.d/k8s.conf ... //看见这个说明应用了 * Applying /etc/sysctl.conf ... //时间同步，所有主机 [root@k8s-master ~]# vim /etc/chrony.conf # Use public servers from the pool.ntp.org project. # Please consider joining the pool (http://www.pool.ntp.org/join.html). pool time1.aliyun.com iburst //配置成阿里云的时间同步 [root@k8s-master ~]# systemctl enable chronyd [root@k8s-master ~]# systemctl restart chronyd [root@k8s-master ~]# systemctl status chronyd ● chronyd.service - NTP client/server Loaded: loaded (/usr/lib/systemd/system/chronyd.service; enabled; vendor preset: enab> Active: active (running) since Tue 2022-09-06 15:54:27 CST; 9s ago [root@k8s-node1 ~]# vim /etc/chrony.conf [root@k8s-node1 ~]# systemctl enable chronyd [root@k8s-node1 ~]# systemctl restart chronyd [root@k8s-node1 ~]# systemctl status chronyd ● chronyd.service - NTP client/server Loaded: loaded (/usr/lib/systemd/system/chronyd.service; enabled; vendor preset: enab> Active: active (running) since Tue 2022-09-06 15:57:52 CST; 8s ago [root@k8s-node2 ~]# vim /etc/chrony.conf [root@k8s-node2 ~]# systemctl enable chronyd [root@k8s-node2 ~]# systemctl restart chronyd [root@k8s-node2 ~]# systemctl status chronyd ● chronyd.service - NTP client/server Loaded: loaded (/usr/lib/systemd/system/chronyd.service; enabled; vendor preset: enab> Active: active (running) since Tue 2022-09-06 //配置免密登录 [root@k8s-master ~]# ssh-keygen -t rsa Generating public/private rsa key pair. Enter file in which to save the key (/root/.ssh/id_rsa): Created directory '/root/.ssh'. Enter passphrase (empty for no passphrase): Enter same passphrase again: Your identification has been saved in /root/.ssh/id_rsa. Your public key has been saved in /root/.ssh/id_rsa.pub. The key fingerprint is: SHA256:LZeVhmrafNhs4eAGG8dNQltVYcGX/sXbKj/dPzR/wNo root@k8s-master The key's randomart image is: +---[RSA 3072]----+ | . ...o=o.| | . o . o...| | o o + .o | | . * + .o| | o S * . =| | @ O . o+o| | o * * o.++| | . o o E.=| | o..=| +----[SHA256]-----+ [root@k8s-master ~]# ssh-copy-id k8s-master /usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/root/.ssh/id_rsa.pub" The authenticity of host 'k8s-master (192.168.106.16)' can't be established. ECDSA key fingerprint is SHA256:1x2Tw0BYQrGTk7wpwsIy+TtFN72hWbHYYiU6WtI/Ojk. Are you sure you want to continue connecting (yes/no/[fingerprint])? yes /usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed /usr/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are prompted now it is to install the new keys root@k8s-master's password: Number of key(s) added: 1 Now try logging into the machine, with: "ssh 'k8s-master'" and check to make sure that only the key(s) you wanted were added. [root@k8s-master ~]# ssh-copy-id k8s-node1 /usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/root/.ssh/id_rsa.pub" The authenticity of host 'k8s-node1 (192.168.106.20)' can't be established. ECDSA key fingerprint is SHA256:75svPGZTNSPdFX6K4lCDkoQfG10Y478mu0NzQD7HpnA. Are you sure you want to continue connecting (yes/no/[fingerprint])? yes /usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed /usr/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are prompted now it is to install the new keys root@k8s-node1's password: Number of key(s) added: 1 Now try logging into the machine, with: "ssh 'k8s-node1'" and check to make sure that only the key(s) you wanted were added. [root@k8s-master ~]# ssh-copy-id k8s-node2 /usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/root/.ssh/id_rsa.pub" The authenticity of host 'k8s-node2 (192.168.106.21)' can't be established. ECDSA key fingerprint is SHA256:75svPGZTNSPdFX6K4lCDkoQfG10Y478mu0NzQD7HpnA. Are you sure you want to continue connecting (yes/no/[fingerprint])? yes /usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed /usr/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are prompted now it is to install the new keys root@k8s-node2's password: Number of key(s) added: 1 Now try logging into the machine, with: "ssh 'k8s-node2'" and check to make sure that only the key(s) you wanted were added. [root@k8s-master ~]# ssh k8s-master Activate the web console with: systemctl enable --now cockpit.socket This system is not registered to Red Hat Insights. See https://cloud.redhat.com/ To register this system, run: insights-client --register Last login: Tue Sep 6 15:10:17 2022 from 192.168.106.1 [root@k8s-master ~]# ssh k8s-node1 Activate the web console with: systemctl enable --now cockpit.socket This system is not registered to Red Hat Insights. See https://cloud.redhat.com/ To register this system, run: insights-client --register Last login: Tue Sep 6 15:10:18 2022 from 192.168.106.1 [root@k8s-node1 ~]# exit 注销 Connection to k8s-node1 closed. [root@k8s-master ~]# ssh k8s-node2 Activate the web console with: systemctl enable --now cockpit.socket This system is not registered to Red Hat Insights. See https://cloud.redhat.com/ To register this system, run: insights-client --register Last login: Tue Sep 6 15:10:18 2022 from 192.168.106.1 [root@k8s-node2 ~]# exit 注销 Connection to k8s-node2 closed. [root@k8s-master ~]# reboot //前面设置了seliunx,swap分区，重启确保他永久生效 [root@k8s-node1 ~]# reboot [root@k8s-node2 ~]# reboot #//注意重启完了检查防火墙和seliunx，swap分区是是否关闭- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- 20
- 21
- 22
- 23
- 24
- 25
- 26
- 27
- 28
- 29
- 30
- 31
- 32
- 33
- 34
- 35
- 36
- 37
- 38
- 39
- 40
- 41
- 42
- 43
- 44
- 45
- 46
- 47
- 48
- 49
- 50
- 51
- 52
- 53
- 54
- 55
- 56
- 57
- 58
- 59
- 60
- 61
- 62
- 63
- 64
- 65
- 66
- 67
- 68
- 69
- 70
- 71
- 72
- 73
- 74
- 75
- 76
- 77
- 78
- 79
- 80
- 81
- 82
- 83
- 84
- 85
- 86
- 87
- 88
- 89
- 90
- 91
- 92
- 93
- 94
- 95
- 96
- 97
- 98
- 99
- 100
- 101
- 102
- 103
- 104
- 105
- 106
- 107
- 108
- 109
- 110
- 111
- 112
- 113
- 114
- 115
- 116
- 117
- 118
- 119
- 120
- 121
- 122
- 123
- 124
- 125
- 126
- 127
- 128
- 129
- 130
- 131
- 132
- 133
- 134
- 135
- 136
- 137
- 138
- 139
- 140
- 141
- 142
- 143
- 144
- 145
- 146
- 147
- 148
- 149
- 150
- 151
- 152
- 153
- 154
- 155
- 156
- 157
- 158
- 159
- 160
- 161
- 162
- 163
- 164
- 165
- 166
- 167
- 168
- 169
- 170
- 171
- 172
- 173
- 174
- 175
- 176
- 177
- 178
- 179
- 180
- 181
- 182
- 183
- 184
- 185
- 186
- 187
- 188
- 189
- 190
- 191
- 192
- 193
- 194
- 195
- 196
- 197
- 198
- 199
- 200
- 201
- 202
所有节点安装Docker/kubeadm/kubelet
Kubernetes默认CRI（容器运行时）为Docker，因此先安装Docker。
安装Docker
##注意所有docker的版本要一致，用dnf list all|grep docker 命令查看 docker-ce.x86_64 版本是否一致 //所有主机都做下面的操作 [root@k8s-master yum.repos.d]# wget https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo -O /etc/yum.repos.d/docker-ce.repo --2022-09-06 16:31:03-- https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo 正在解析主机 mirrors.aliyun.com (mirrors.aliyun.com)... 45.253.17.211, 45.253.17.216, 45.253.17.213, ... 正在连接 mirrors.aliyun.com (mirrors.aliyun.com)|45.253.17.211|:443... 已连接。 已发出 HTTP 请求，正在等待回应... 200 OK 长度：2081 (2.0K) [application/octet-stream] 正在保存至: “/etc/yum.repos.d/docker-ce.repo” /etc/yum.repos.d/docke 100%[=========================>] 2.03K --.-KB/s 用时 0.002s 2022-09-06 16:31:04 (1.05 MB/s) - 已保存 “/etc/yum.repos.d/docker-ce.repo” [2081/2081]) [root@k8s-master ~]# dnf list all|grep docker containerd.io.x86_64 1.6.8-3.1.el8 @docker-ce-stable docker-ce.x86_64 //这个 3:20.10.17-3.el8 @docker-ce-stable docker-ce-cli.x86_64 1:20.10.17-3.el8 @docker-ce-stable [root@k8s-master ~]# dnf -y install docker-ce --allowerasiong //正常情况不用加--allowerasiong来替换冲突的软件包 ，我的源有问题所有加这个 [root@k8s-master ~]# systemctl enable --now docker Created symlink /etc/systemd/system/multi-user.target.wants/docker.service → /usr/lib/systemd/system/docker.service. [root@k8s-master ~]# docker version Client: Docker Engine - Community Version: 20.10.17 //版本要统一 API version: 1.41 Go version: go1.17.11 Git commit: 100c701 Built: Mon Jun 6 23:03:11 2022 OS/Arch: linux/amd64 Context: default Experimental: true Server: Docker Engine - Community Engine: Version: 20.10.17 API version: 1.41 (minimum version 1.12) Go version: go1.17.11 Git commit: a89b842 Built: Mon Jun 6 23:01:29 2022 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.6.8 GitCommit: 9cd3357b7fd7218e4aec3eae239db1f68a5a6ec6 runc: Version: 1.1.4 GitCommit: v1.1.4-0-g5fd4c4d docker-init: Version: 0.19.0 GitCommit: de40ad0 [root@k8s-master ~]# //配置加速器 [root@k8s-master ~]# cat > /etc/docker/daemon.json << EOF > { > "registry-mirrors": ["https://b9pmyelo.mirror.aliyuncs.com"], > "exec-opts": ["native.cgroupdriver=systemd"], > "log-driver": "json-file", > "log-opts": { > "max-size": "100m" > }, > "storage-driver": "overlay2" > } > EOF [root@k8s-master ~]# cat /etc/docker/daemon.json { "registry-mirrors": ["https://b9pmyelo.mirror.aliyuncs.com"], //加速器 "exec-opts": ["native.cgroupdriver=systemd"], //驱动 "log-driver": "json-file", //格式 "log-opts": { "max-size": "100m" //100m开始运行 }, "storage-driver": "overlay2" //存储驱动 }- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- 20
- 21
- 22
- 23
- 24
- 25
- 26
- 27
- 28
- 29
- 30
- 31
- 32
- 33
- 34
- 35
- 36
- 37
- 38
- 39
- 40
- 41
- 42
- 43
- 44
- 45
- 46
- 47
- 48
- 49
- 50
- 51
- 52
- 53
- 54
- 55
- 56
- 57
- 58
- 59
- 60
- 61
- 62
- 63
- 64
- 65
- 66
- 67
- 68
- 69
- 70
- 71
- 72
- 73
- 74
添加kubernetes阿里云YUM软件源
#以下操作所有节点都要配置 [root@k8s-master ~]# 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- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
安装kubeadm，kubelet和kubectl
#以下操作所有节点都要配置 [root@k8s-master ~]# dnf list all|grep kubelet //查看，要统一 kubelet.x86_64 1.25.0-0 kubernetes [root@k8s-master ~]# dnf list all|grep kubeadm kubeadm.x86_64 1.25.0-0 kubernetes [root@k8s-master ~]# dnf list all|grep kubectl kubectl.x86_64 1.25.0-0 kubernetes [root@k8s-master ~]# dnf -y install kubelet kubeadm kubectl [root@k8s-master ~]# systemctl enable kubelet //不能启动 Created symlink /etc/systemd/system/multi-user.target.wants/kubelet.service → /usr/lib/systemd/system/kubelet.service. [root@k8s-master ~]# systemctl status kubelet ● kubelet.service - kubelet: The Kubernetes Node Agent Loaded: loaded (/usr/lib/systemd/system/kubelet.service; enabled; vendor> Drop-In: /usr/lib/systemd/system/kubelet.service.d- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
部署Kubernetes Master
在192.168.106.16（Master）执行[root@k8s-master ~]# kubeadm init -h //看帮助文档 [root@k8s-master ~]# cd /etc/containerd/ [root@k8s-master containerd]# containerd config default > config.toml //生成 [root@k8s-master containerd]# vim config.toml sandbox_image = "k8s.gcr.io/pause:3.6" //改为 sandbox_image = "registry.cn-beijing.aliyuncs.com/abcdocker/pause:3.6" [root@k8s-master manifests]# systemctl stop kubelet [root@k8s-master manifests]# systemctl restart containerd [root@k8s-master manifests]# kubeadm init --apiserver-advertise-address 192.168.70.134 --image-repository registry.aliyuncs.com/google_containers --kubernetes-version v1.25.0 --service-cidr 10.96.0.0/12 --pod-network-cidr 10.244.0.0/16 //省略过程 //除了192.168.106.16，其他基本都是固定写法 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 Alternatively, if you are the root user, you can run: export KUBECONFIG=/etc/kubernetes/admin.conf //root用户用这些命令 You should now deploy a pod network to the cluster. Run "kubectl apply -f [podnetwork].yaml" with one of the options listed at: //要配置这个网络插件，在github.com ，上搜索flannel 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.70.134:6443 --token h9utko.9esdw3ge9j0urwae \ --discovery-token-ca-cert-hash sha256:8c36d378e51b8d01f1fe904e51e1b5d7215fc76dcbaf105c798c4cda70e84ca1 //看到着说明初始化成功 //设置永久环境变量，用root方式 [root@k8s-master ~]# vim /etc/profile.d/k8s.sh [root@k8s-master ~]# cat /etc/profile.d/k8s.sh export KUBECONFIG=/etc/kubernetes/admin.conf [root@k8s-master ~]# source /etc/profile.d/k8s.sh [root@k8s-master ~]# echo $KUBECONFIG /etc/kubernetes/admin.conf- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- 20
- 21
- 22
- 23
- 24
- 25
- 26
- 27
- 28
- 29
- 30
- 31
- 32
- 33
- 34
- 35
- 36
- 37
- 38
- 39
- 40
- 41
由于默认拉取镜像地址k8s.gcr.io国内无法访问，这里指定阿里云镜像仓库地址。
使用kubectl工具：//这个普通用户要做的操作，root不用 mkdir -p $HOME/.kube sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config sudo chown $(id -u):$(id -g) $HOME/.kube/config kubectl get nodes- 1
- 2
- 3
- 4
- 5
[root@k8s-master ~]# kubectl get nodes NAME STATUS ROLES AGE VERSION k8s-master NotReady control-plane 14m v1.25.0- 1
- 2
- 3
安装Pod网络插件（CNI）
//看到说明成功 [root@k8s-master ~]# kubectl apply -f https://raw.githubusercontent.com/flannel-io/flannel/master/Documentation/kube-flannel.yml namespace/kube-flannel created clusterrole.rbac.authorization.k8s.io/flannel created clusterrolebinding.rbac.authorization.k8s.io/flannel created serviceaccount/flannel created configmap/kube-flannel-cfg created daemonset.apps/kube-flannel-ds created- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
确保能够访问到quay.io这个registery。
加入Kubernetes Node
在192.168.106.20、192.168.106.21上（Node）执行。向集群添加新节点，执行在kubeadm init输出的kubeadm join命令：
[root@k8s-master ~]# kubectl get nodes NAME STATUS ROLES AGE VERSION k8s-master Ready control-plane 15h v1.25.0 //网络通了，变成Ready //node节点这个文件都备份或者删除 [root@k8s-node2 containerd]# ls config.toml [root@k8s-node2 containerd]# mv config.toml{,.bak} //备份文件，里面都加# [root@k8s-node2 containerd]# ls config.toml.bak [root@k8s-master ~]# cd /etc/containerd/ [root@k8s-master containerd]# ls config.toml //将已经生成好不会报错的文件传过去 [root@k8s-master containerd]# scp /etc/containerd/config.toml k8s-node1:/etc/containerd/ config.toml 100% 6952 3.4MB/s 00:00 [root@k8s-master containerd]# scp /etc/containerd/config.toml k8s-node2:/etc/containerd/ config.toml 100% 6952 3.8MB/s 00:00 [root@k8s-node1 containerd]# ls config.toml [root@k8s-node1 containerd]# systemctl restart containerd //重启文件生效 [root@k8s-node1 containerd]# kubeadm join 192.168.70.134:6443 --token h9utko.9esdw3ge9j0urwae --discovery-token-ca-cert-hash sha256:8c36d378e51b8d01f1fe904e51e1b5d7215fc76dcbaf105c798c4cda70e84ca1 [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 -o yaml' [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] Starting the kubelet [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@k8s-node2 containerd]# ls config.toml config.toml.bak [root@k8s-node2 containerd]# systemctl restart containerd [root@k8s-node2 containerd]# kubeadm join 192.168.70.134:6443 --token h9utko.9esdw3ge9j0urwae --discovery-token-ca-cert-hash sha256:8c36d378e51b8d01f1fe904e51e1b5d7215fc76dcbaf105c798c4cda70e84ca1 [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 -o yaml' [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] Starting the kubelet [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@k8s-master containerd]# kubectl get nodes NAME STATUS ROLES AGE VERSION k8s-master Ready control-plane 15h v1.25.0 k8s-node1 Ready <none> 2m39s v1.25.0 k8s-node2 NotReady <none> 81s v1.25.0 //NotReady 不是因为网络不同，而是他在拉镜像，等会 [root@k8s-master containerd]# kubectl get nodes //已连通添加节点 NAME STATUS ROLES AGE VERSION k8s-master Ready control-plane 15h v1.25.0 k8s-node1 Ready <none> 4m35s v1.25.0 k8s-node2 Ready <none> 3m17s v1.25.0- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- 20
- 21
- 22
- 23
- 24
- 25
- 26
- 27
- 28
- 29
- 30
- 31
- 32
- 33
- 34
- 35
- 36
- 37
- 38
- 39
- 40
- 41
- 42
- 43
- 44
- 45
- 46
- 47
- 48
- 49
- 50
- 51
- 52
- 53
- 54
- 55
- 56
- 57
- 58
- 59
- 60
- 61
- 62
[root@k8s-node1 ~]# kubectl get nodes //访问不了因为没有添加环境变量和环境变量所指的文件 The connection to the server localhost:8080 was refused - did you specify the right host or port? //添加环境变量和环境变量所指的文件 [root@k8s-master ~]# scp /etc/kubernetes/admin.conf k8s-node1:/etc/kubernetes/admin.conf admin.conf 100% 5638 2.7MB/s 00:00 [root@k8s-master ~]# scp /etc/kubernetes/admin.conf k8s-node2:/etc/kubernetes/admin.conf admin.conf 100% 5638 2.9MB/s 00:00 [root@k8s-master ~]# scp /etc/profile.d/k8s.sh k8s-node2:/etc/profile.d/k8s.sh k8s.sh 100% 45 23.6KB/s 00:00 [root@k8s-master ~]# scp /etc/profile.d/k8s.sh k8s-node1:/etc/profile.d/k8s.sh k8s.sh 100% 45 3.8KB/s 00:00 //在node节点查看 [root@k8s-node1 ~]# bash //让变量生效 [root@k8s-node1 ~]# echo $KUBECONFIG /etc/kubernetes/admin.conf [root@k8s-node1 ~]# kubectl get nodes //成功，可以查看节点 NAME STATUS ROLES AGE VERSION k8s-master Ready control-plane 16h v1.25.0 k8s-node1 Ready <none> 21m v1.25.0 k8s-node2 Ready <none> 20m v1.25.0 [root@k8s-node2 ~]# bash [root@k8s-node2 ~]# echo $KUBECONFIG /etc/kubernetes/admin.conf [root@k8s-node2 ~]# kubectl get nodes NAME STATUS ROLES AGE VERSION k8s-master Ready control-plane 16h v1.25.0 k8s-node1 Ready <none> 21m v1.25.0 k8s-node2 Ready <none> 20m v1.25.0- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- 20
- 21
- 22
- 23
- 24
- 25
- 26
- 27
- 28
测试kubernetes集群
在Kubernetes集群中创建一个pod，验证是否正常运行：[root@k8s-master ~]# kubectl create deployment nginx --image=nginx deployment.apps/nginx created //deployment: 类型 //ngimx:pod名称 //nginx:镜像 [root@k8s-master ~]# kubectl expose deployment nginx --port=80 --type=NodePort //--part:暴露端口号 //type=NodePort:类型 service/nginx exposed [root@k8s-master ~]# kubectl get pod,svc //获取pod,service的信息 //READY是0/1 说明是在拉镜像，等以下在查看 //ContainerCreating 没起来 NAME READY STATUS RESTARTS AGE pod/nginx-76d6c9b8c-6vnnf 0/1 ContainerCreating 0 17s NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 16h service/nginx NodePort 10.98.79.60 <none> 80:30274/TCP 7s [root@k8s-master ~]# kubectl get pod,svc NAME READY STATUS RESTARTS AGE pod/nginx-76d6c9b8c-6vnnf 1/1 Running 0 5m28s NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 16h service/nginx NodePort 10.98.79.60 <none> 80:30274/TCP 5m18s- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19
访问端口，成功
集群IP只能内部访问，默认80端口[root@k8s-master ~]# curl 10.98.79.60 <!DOCTYPE html> <html> <head> <title>Welcome to nginx!</title> <style> html { color-scheme: light dark; } body { width: 35em; margin: 0 auto; font-family: Tahoma, Verdana, Arial, sans-serif; } </style> </head> <body> <h1>Welcome to nginx!</h1> <p>If you see this page, the nginx web server is successfully installed and working. Further configuration is required.</p> <p>For online documentation and support please refer to <a href="http://nginx.org/">nginx.org</a>.- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- 20
- 21
- 22
- 23
- 24
kubectl命令使用：
get命令：//查看pod详细信息 //查看名称空间来自那台主机，查看容器，KubeProxy提供负载均衡随机分配 [root@k8s-node1 ~]# kubectl get pods -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES nginx-76d6c9b8c-6vnnf 1/1 Running 1 (10m ago) 39m 10.244.2.3 k8s-node2 <none> <none>- 1
- 2
- 3
- 4
- 5
- 6
//查看控制器 [root@k8s-node1 ~]# kubectl get deployment NAME READY UP-TO-DATE AVAILABLE AGE nginx 1/1 1 1 44m // AVAILABLE 是否可用 // UP-TO-DATE 更新到最新状态- 1
- 2
- 3
- 4
- 5
- 6
create命令
[root@k8s-master ~]# kubectl create deployment test1 --image busybox deployment.apps/test1 created [root@k8s-master ~]# kubectl get pod NAME READY STATUS RESTARTS AGE nginx-76d6c9b8c-6vnnf 1/1 Running 2 (157m ago) 6h54m test1-5b6fc8994b-7fdf4 0/1 ContainerCreating 0 13s [root@k8s-master ~]#- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
run命令
[root@k8s-master ~]# kubectl run nginx --image nginx pod/nginx created //启动 nginx的pod [root@k8s-master ~]# kubectl delete pods nginx pod "nginx" deleted //删除 nginx的pod- 1
- 2
- 3
- 4
delete命令
[root@k8s-master ~]# kubectl delete deployment test1 // 删除test1，使用deployment类型 deployment.apps "test1" deleted [root@k8s-master ~]# kubectl get pod NAME READY STATUS RESTARTS AGE nginx-6799fc88d8-254qg 1/1 Running 0 24m- 1
- 2
- 3
- 4
- 5
expose命令
[root@k8s-master ~]# kubectl create deployment web --image busybox //列出所有的pod deployment.apps/web created [root@k8s-master ~]# kubectl expose deployment web --port 8080 --target-port 80 //显示所有pod的详细信息 service/web exposed [root@k8s-master ~]# kubectl get svc 列出所有服务 NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 23h nginx NodePort 10.98.79.60 <none> 80:30274/TCP 7h1m web ClusterIP 10.105.214.159 <none> 8080/TCP 48s- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
-
相关阅读:
vue create 创建项目的时候遇到使用nvm切换node后 提示‘vue‘ 不是内部或外部命令,也不是可运行的程序 或批处理文件
二叉树最大路径和问题
编译原理：上下文无关文法 CFG
uView 对象操作
Spring Boot入门(21)：使用Spring Boot和Log4j2进行高效日志管理：配置详解
基于Java的智能停车场管理系统设计与实现(源码+lw+部署文档+讲解等)
【数据结构】对称二叉树 && 另一颗树的子树（六）
京东手机销售数据：2023年9月京东手机行业TOP10品牌排行榜
蓝桥杯--挖地雷
C语言——转义字符
- 原文地址：https://blog.csdn.net/qq_52943068/article/details/126743678
