K8S linux安装

最新推荐文章于 2024-04-20 16:55:58 发布
最新推荐文章于 2024-04-20 16:55:58 发布
阅读量188 收藏
点赞数
分类专栏： 开源技术学习 文章标签： 开源软件
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/eassen_licd/article/details/132583224
版权

K8S linux安装

一、虚拟机配置

1、准备三台centos虚拟机

192.168.189.128  2G内存 2个CPU共4核  40G硬盘 master最低最好3G内存
192.168.189.129  2G内存 2个CPU共4核  40G硬盘
192.168.189.130  2G内存 2个CPU共4核  40G硬盘

2、关闭防火墙和selinux

# 每台都需执行
systemctl stop firewalld
systemctl disable firewalld
sed -i 's/enforcing/disabled/' /etc/selinux/config
setenforce 0

3、关闭swap分区

# 每台都需执行
# 临时关闭
swapoff -a
 # 注释到swap那一行  永久关闭
vim /etc/fstab
/dev/mapper/centos-root /                       xfs     defaults        0 0
UUID=5ce36a60-278b-4612-869e-1b04220c5379 /boot                   xfs     defaults        0 0
# /dev/mapper/centos-swap swap                    swap    defaults        0 0   #此行注释
4、添加主机名与IP对应关系
echo '''
192.168.189.128 k8s-master
192.168.189.129 k8s-node-01
192.168.189.130 k8s-node-02
''' >> /etc/hosts

5、设置主机名

# 192.168.189.128
hostnamectl set-hostname k8s-master
# 192.168.189.129
hostnamectl set-hostname k8s-node-01
# 192.168.189.130
hostnamectl set-hostname k8s-node-02

6、将桥接的IPv4流量传递到iptables的链

# 以下net.ipv4.ip_forward如存在=0，修改为1即可
cat > /etc/sysctl.d/k8s.conf << EOF
net.ipv4.ip_forward = 1
net.ipv4.tcp_tw_recycle = 0
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1
EOF

sysctl --system

二、升级centos最新内核

3台全部升级

1、查看当前内核版本

[root@k8s02 ~]# uname -a
Linux k8s-node-01 3.10.0-1160.el7.x86_64 #1 SMP Mon Oct 19 16:18:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

2、安装epel源

[root@k8s01 ~]# rpm --import https://www.elrepo.org/RPM-GPG-KEY-elrepo.org
[root@k8s01 ~]# yum install -y https://www.elrepo.org/elrepo-release-7.el7.elrepo.noarch.rpm
Loaded plugins: fastestmirror, langpacks
elrepo-release-7.el7.elrepo.noarch.rpm                                                 | 8.7 kB  00:00:00
Examining /var/tmp/yum-root-7n6VwO/elrepo-release-7.el7.elrepo.noarch.rpm: elrepo-release-7.0-6.el7.elrepo.noarch
Marking /var/tmp/yum-root-7n6VwO/elrepo-release-7.el7.elrepo.noarch.rpm to be installed
Resolving Dependencies
--> Running transaction check
---> Package elrepo-release.noarch 0:7.0-6.el7.elrepo will be installed
--> Finished Dependency Resolution

Dependencies Resolved

==============================================================================================================================================================
 Package                           Arch                      Version                             Repository                                              Size
==============================================================================================================================================================
Installing:
 elrepo-release                    noarch                    7.0-6.el7.elrepo                    /elrepo-release-7.el7.elrepo.noarch                    5.0 k

Transaction Summary
==============================================================================================================================================================
Install  1 Package

Total size: 5.0 k
Installed size: 5.0 k
Downloading packages:
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
  Installing : elrepo-release-7.0-6.el7.elrepo.noarch                                                  1/1
  Verifying  : elrepo-release-7.0-6.el7.elrepo.noarch                                                  1/1

Installed:
  elrepo-release.noarch 0:7.0-6.el7.elrepo

Complete!

3、查看最新内核

[root@k8s01 ~]# yum --disablerepo="*" --enablerepo="elrepo-kernel" list available
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile
 * elrepo-kernel: mirrors.tuna.tsinghua.edu.cn
elrepo-kernel                                       | 3.0 kB  00:00:00
elrepo-kernel/primary_db                            | 2.1 MB  00:00:03
Available Packages
kernel-lt.x86_64                                    5.4.254-1.el7.elrepo    elrepo-kernel
kernel-lt-devel.x86_64                              5.4.254-1.el7.elrepo    elrepo-kernel
kernel-lt-doc.noarch                                5.4.254-1.el7.elrepo    elrepo-kernel
kernel-lt-headers.x86_64                            5.4.254-1.el7.elrepo    elrepo-kernel
kernel-lt-tools.x86_64                              5.4.254-1.el7.elrepo    elrepo-kernel
kernel-lt-tools-libs.x86_64                         5.4.254-1.el7.elrepo    elrepo-kernel
kernel-lt-tools-libs-devel.x86_64                   5.4.254-1.el7.elrepo    elrepo-kernel
kernel-ml.x86_64                                    6.4.12-1.el7.elrepo     elrepo-kernel
kernel-ml-devel.x86_64                              6.4.12-1.el7.elrepo     elrepo-kernel
kernel-ml-doc.noarch                                6.4.12-1.el7.elrepo     elrepo-kernel
kernel-ml-headers.x86_64                            6.4.12-1.el7.elrepo     elrepo-kernel
kernel-ml-tools.x86_64                              6.4.12-1.el7.elrepo     elrepo-kernel
kernel-ml-tools-libs.x86_64                         6.4.12-1.el7.elrepo     elrepo-kernel
kernel-ml-tools-libs-devel.x86_64                   6.4.12-1.el7.elrepo     elrepo-kernel
perf.x86_64                                         5.4.254-1.el7.elrepo    elrepo-kernel
python-perf.x86_64                                  5.4.254-1.el7.elrepo    elrepo-kernel

4、安装最新lt内核版本

[root@k8s01 ~]# yum --disablerepo='*' --enablerepo=elrepo-kernel install kernel-lt -y
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile
 * elrepo-kernel: mirrors.tuna.tsinghua.edu.cn
Resolving Dependencies
--> Running transaction check
---> Package kernel-lt.x86_64 0:5.4.254-1.el7.elrepo will be installed
--> Finished Dependency Resolution

Dependencies Resolved

==============================================================================================================================================================
 Package                           Arch                           Version                                         Repository                             Size
==============================================================================================================================================================
Installing:
 kernel-lt                         x86_64                         5.4.254-1.el7.elrepo                            elrepo-kernel                          50 M

Transaction Summary
==============================================================================================================================================================
Install  1 Package

Total download size: 50 M
Installed size: 230 M
Downloading packages:
kernel-lt-5.4.254-1.el7.elrepo.x86_64.rpm                                 |  50 MB  00:00:42
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
  Installing : kernel-lt-5.4.254-1.el7.elrepo.x86_64                                         1/1
  Verifying  : kernel-lt-5.4.254-1.el7.elrepo.x86_64                                         1/1

Installed:
  kernel-lt.x86_64 0:5.4.254-1.el7.elrepo
Complete!

5、查看系统grub内核的启动列表

awk -F\' '$1=="menuentry " {print i++ " : " $2}' /etc/grub2.cfg

0 : CentOS Linux (5.4.254-1.el7.elrepo.x86_64) 7 (Core)
1 : CentOS Linux (3.10.0-1160.el7.x86_64) 7 (Core)
2 : CentOS Linux (0-rescue-10a248b980bc45fb9a526f4511831830) 7 (Core)

6、指定以新安装的编号0的内核版本为默认启动内核

grub2-set-default 0

7、重启机器，以新内核版本加载启动

shutdown -r now

8、卸载旧内核版本

# 重启之后才可以删除
[root@k8s-master ~]# yum remove kernel -y
Loaded plugins: fastestmirror, langpacks
Resolving Dependencies
--> Running transaction check
---> Package kernel.x86_64 0:3.10.0-1160.el7 will be erased
--> Processing Dependency: kernel(PDE_DATA) = 0x44f0d59d for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(___ratelimit) = 0x155f4108 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(__bitmap_weight) = 0x4cbbd171 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(__cond_resched_lock) = 0xe2cfb038 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(__init_waitqueue_head) = 0xf432dd3d for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(__kmalloc) = 0xd2b09ce5 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(__list_add) = 0x0343a1a8 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(__list_del_entry) = 0x65e75cb6 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(__mutex_init) = 0x9a025cd5 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(__stack_chk_fail) = 0xf0fdf6cb for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(__vmalloc) = 0xa9bd2676 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(__wake_up) = 0xcf21d241 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(_raw_qspin_lock) = 0x4b7dcf38 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(_raw_qspin_lock_irq) = 0x3588d8ba for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(_raw_read_lock) = 0x9b0c8220 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(_raw_spin_lock_bh) = 0x1637ff0f for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(_raw_spin_lock_irqsave) = 0x9327f5ce for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(_raw_spin_unlock_bh) = 0xba63339c for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(_raw_spin_unlock_irqrestore) = 0x08f64aa4 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(_raw_write_lock) = 0x13a1a61a for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(autoremove_wake_function) = 0xc8b57c27 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(bdevname) = 0x8f619a88 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(bio_add_page) = 0x4554b079 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(bio_alloc_bioset) = 0xeb862489 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(bio_endio) = 0xdd5fbc2b for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(bio_put) = 0x867c68af for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(bio_reset) = 0x060f6a84 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(bioset_create) = 0x1b57183e for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(bioset_free) = 0x8f49a246 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(blk_finish_plug) = 0x0ce900af for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(blk_limits_io_min) = 0x124af3bf for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(blk_limits_io_opt) = 0x7c922190 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(blk_start_plug) = 0x925520d2 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(blkdev_get_by_dev) = 0x8c1cc22d for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(blkdev_get_by_path) = 0x6f3b39e8 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(blkdev_put) = 0x1a86fdbf for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(complete) = 0x4b06d2e7 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(complete_and_exit) = 0x5aeb145f for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(cpu_online_mask) = 0x930484aa for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(crc32_le) = 0x802d0e93 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(current_task) = 0xb8c7ff88 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(del_timer_sync) = 0xd5f2172f for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(dm_get_device) = 0xa425b4a9 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(dm_put_device) = 0x412d503d for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(dm_register_target) = 0x979ddcc5 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(dm_table_get_mode) = 0x6d0f1f89 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(dm_unregister_target) = 0xeeeae71b for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(finish_wait) = 0xfa66f77c for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(fs_bio_set) = 0x30877173 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(generic_make_request) = 0xd42803ea for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(getnstimeofday64) = 0x211f68f1 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(init_timer_key) = 0x0593a99b for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(jiffies) = 0x7d11c268 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(kernel_stack) = 0x4c4fef19 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(kobject_add) = 0xd9c798eb for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(kobject_get) = 0x75b1f1fb for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(kobject_init) = 0x9d6dbebd for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(kobject_put) = 0x54554948 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(kstrtoll) = 0x1b17e06c for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(kstrtoull) = 0x060ea2d6 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(kthread_create_on_node) = 0xc35e4b4e for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(kthread_stop) = 0x42f90a31 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(list_del) = 0x0521445b for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(mod_timer) = 0x8834396c for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(module_layout) = 0x28950ef1 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(msecs_to_jiffies) = 0x3bd1b1f6 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(mutex_lock) = 0x9abdea30 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(mutex_unlock) = 0x4ed12f73 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(name_to_dev_t) = 0x08156773 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(nr_cpu_ids) = 0xfe7c4287 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(prandom_bytes) = 0x7a188791 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(prepare_to_wait) = 0x5c8b5ce8 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(prepare_to_wait_exclusive) = 0xf8983de7 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(printk) = 0x27e1a049 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(proc_create_data) = 0x8c34c149 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(proc_mkdir) = 0x73839c7a for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(pv_irq_ops) = 0x78764f4e for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(pv_lock_ops) = 0x784213a6 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(remove_proc_entry) = 0xa16aae11 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(remove_proc_subtree) = 0x5ae98fc6 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(schedule_hrtimeout) = 0xd705b4c7 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(schedule_timeout) = 0xd62c833f for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(scnprintf) = 0x4ca9669f for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(seq_lseek) = 0x1685c91c for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(seq_read) = 0x9c3df9b4 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(seq_write) = 0x97544bdc for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(single_open) = 0x16a5a12f for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(single_release) = 0x2296f507 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(sme_me_mask) = 0x17fbce60 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(snprintf) = 0x28318305 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(sprintf) = 0x91715312 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(sscanf) = 0x20c55ae0 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(submit_bio) = 0xc4076f47 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(usecs_to_jiffies) = 0xb54533f7 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(vmalloc_to_page) = 0x18e6b5cd for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(vprintk) = 0xbf8ba54a for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(vsnprintf) = 0x99195078 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(wait_for_completion) = 0x6d0aba34 for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(wait_for_completion_interruptible) = 0x015ddbdc for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Processing Dependency: kernel(wake_up_process) = 0xe65cdceb for package: kmod-kvdo-6.1.3.23-5.el7.x86_64
--> Running transaction check
---> Package kmod-kvdo.x86_64 0:6.1.3.23-5.el7 will be erased
--> Processing Dependency: kmod-kvdo >= 6.1 for package: vdo-6.1.3.23-5.el7.x86_64
--> Running transaction check
---> Package vdo.x86_64 0:6.1.3.23-5.el7 will be erased
--> Finished Dependency Resolution
elrepo                                                                   | 3.0 kB  00:00:00
elrepo/primary_db                                                        | 356 kB  00:00:00

Dependencies Resolved

==============================================================================================================================================================
 Package                              Arch                              Version                                    Repository                            Size
==============================================================================================================================================================
Removing:
 kernel                               x86_64                            3.10.0-1160.el7                            @anaconda                             64 M
Removing for dependencies:
 kmod-kvdo                            x86_64                            6.1.3.23-5.el7                             @anaconda                            1.2 M
 vdo                                  x86_64                            6.1.3.23-5.el7                             @anaconda                            3.3 M

Transaction Summary
==============================================================================================================================================================
Remove  1 Package (+2 Dependent packages)

Installed size: 69 M
Downloading packages:
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
  Erasing    : vdo-6.1.3.23-5.el7.x86_64                                    1/3
  Erasing    : kmod-kvdo-6.1.3.23-5.el7.x86_64                              2/3
  Erasing    : kernel-3.10.0-1160.el7.x86_64                                3/3
  Verifying  : kmod-kvdo-6.1.3.23-5.el7.x86_64                              1/3
  Verifying  : kernel-3.10.0-1160.el7.x86_64                                2/3
  Verifying  : vdo-6.1.3.23-5.el7.x86_64                                    3/3

Removed:
  kernel.x86_64 0:3.10.0-1160.el7

Dependency Removed:
  kmod-kvdo.x86_64 0:6.1.3.23-5.el7                                                vdo.x86_64 0:6.1.3.23-5.el7

Complete!

9、重新查看内核

[root@k8s-master ~]# uname -a
Linux k8s-master 5.4.254-1.el7.elrepo.x86_64 #1 SMP Wed Aug 16 17:27:41 EDT 2023 x86_64 x86_64 x86_64 GNU/Linux

三、安装Docker

1、安装阿里源

[root@k8s-master ~]# yum-config-manager --add-repo http://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo
Loaded plugins: fastestmirror, langpacks
adding repo from: http://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo
grabbing file http://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo to /etc/yum.repos.d/docker-ce.repo
repo saved to /etc/yum.repos.d/docker-ce.repo

2、安装docker依赖

yum install -y yum-utils device-mapper-persistent-data lvm2

3、docker安装

# 查看指定包的版本信息
yum --showduplicates list docker-ce
[root@k8s-master ~]# yum --showduplicates list docker-ce
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile
 * base: mirrors.huaweicloud.com
 * elrepo: mirrors.tuna.tsinghua.edu.cn
 * extras: mirrors.huaweicloud.com
 * updates: mirrors.huaweicloud.com
Available Packages
docker-ce.x86_64            17.03.0.ce-1.el7.centos    docker-ce-stable
docker-ce.x86_64            17.03.1.ce-1.el7.centos    docker-ce-stable
docker-ce.x86_64            17.03.2.ce-1.el7.centos    docker-ce-stable
docker-ce.x86_64            17.03.3.ce-1.el7           docker-ce-stable
docker-ce.x86_64            17.06.0.ce-1.el7.centos    docker-ce-stable
docker-ce.x86_64            17.06.1.ce-1.el7.centos    docker-ce-stable
docker-ce.x86_64            17.06.2.ce-1.el7.centos    docker-ce-stable
docker-ce.x86_64            17.09.0.ce-1.el7.centos    docker-ce-stable
docker-ce.x86_64            17.09.1.ce-1.el7.centos    docker-ce-stable
docker-ce.x86_64            17.12.0.ce-1.el7.centos    docker-ce-stable
docker-ce.x86_64            17.12.1.ce-1.el7.centos    docker-ce-stable
docker-ce.x86_64            18.03.0.ce-1.el7.centos    docker-ce-stable
docker-ce.x86_64            18.03.1.ce-1.el7.centos    docker-ce-stable
docker-ce.x86_64            18.06.0.ce-3.el7           docker-ce-stable
docker-ce.x86_64            18.06.1.ce-3.el7           docker-ce-stable
docker-ce.x86_64            18.06.2.ce-3.el7           docker-ce-stable
docker-ce.x86_64            18.06.3.ce-3.el7           docker-ce-stable
docker-ce.x86_64            3:18.09.0-3.el7            docker-ce-stable
docker-ce.x86_64         3:23.0.1-1.el7     docker-ce-stable
docker-ce.x86_64         3:23.0.2-1.el7     docker-ce-stable
docker-ce.x86_64         3:23.0.3-1.el7     docker-ce-stable
docker-ce.x86_64         3:23.0.4-1.el7     docker-ce-stable
docker-ce.x86_64         3:23.0.5-1.el7     docker-ce-stable
docker-ce.x86_64         3:23.0.6-1.el7     docker-ce-stable
docker-ce.x86_64         3:24.0.0-1.el7     docker-ce-stable
docker-ce.x86_64         3:24.0.1-1.el7     docker-ce-stable
docker-ce.x86_64         3:24.0.2-1.el7     docker-ce-stable
docker-ce.x86_64         3:24.0.3-1.el7     docker-ce-stable
docker-ce.x86_64         3:24.0.4-1.el7     docker-ce-stable
docker-ce.x86_64         3:24.0.5-1.el7     docker-ce-stable

# 安装指定版本，去掉3：之后安装
yum -y install docker-ce-20.10.24-3.el7

4、启动并加入开机自启

systemctl start docker
systemctl enable docker

5、修改docker数据存放目录位置

//## vim /etc/docker/daemon.json
{
  "graph": "/app/dockerData",
  "registry-mirrors": ["https://registry.cn-hangzhou.aliyuncs.com"],
  "exec-opts": ["native.cgroupdriver=systemd"],
  "log-driver": "json-file",
  "log-opts": {
    "max-size": "100m"
  },
  "storage-driver": "overlay2"
}

6、重启docker载入新配置

systemctl daemon-reload
systemctl restart docker

四、安装kubeadm，kubelet和kubectl

1、添加k8s阿里云YUM软件源

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

2、安装kubeadm，kubelet和kubectl

# 查看kubelet版本列表 1.23版本之后可能会出现连接不到主节点的错误，因此使用1.23版本进行安装
yum --showduplicates list kubelet
yum install -y kubelet-1.23.0 kubeadm-1.23.0 kubectl-1.23.0
systemctl start kubelet
systemctl enable kubelet

五、部署k8s的master和node节点

1、部署master节点（128上）

kubeadm init   --apiserver-advertise-address=192.168.189.128 --image-repository registry.aliyuncs.com/google_containers   --kubernetes-version v1.23.0   --service-cidr=10.96.0.0/12 --pod-network-cidr=10.244.0.0/16

# 执行日志
[root@k8s-master yum.repos.d]# kubeadm init   --apiserver-advertise-address=192.168.189.128 --image-repository registry.aliyuncs.com/google_containers   --kubernetes-version v1.16.0   --service-cidr=192.168.189.128 --pod-network-cidr=192.20.0.0/16
[init] Using Kubernetes version: v1.16.0
[preflight] Running pre-flight checks
[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 [k8s-master kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [192.10.0.1 192.168.189.128]
[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/server" certificate and key
[certs] etcd/server serving cert is signed for DNS names [k8s-master localhost] and IPs [192.168.189.128 127.0.0.1 ::1]
[certs] Generating "etcd/peer" certificate and key
[certs] etcd/peer serving cert is signed for DNS names [k8s-master localhost] and IPs [192.168.189.128 127.0.0.1 ::1]
[certs] Generating "etcd/healthcheck-client" certificate and key
[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 16.002945 seconds
[upload-config] Storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace
[kubelet] Creating a ConfigMap "kubelet-config-1.16" 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 k8s-master as control-plane by adding the label "node-role.kubernetes.io/master=''"
[mark-control-plane] Marking the node k8s-master as control-plane by adding the taints [node-role.kubernetes.io/master:NoSchedule]
[bootstrap-token] Using token: ndyb3v.iu7nolzawqaoxjm1
[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/

# 在129和130上执行此命令将node加入到master中
Then you can join any number of worker nodes by running the following on each as root:

kubeadm join 192.168.189.128:6443 --token ndyb3v.iu7nolzawqaoxjm1 \
    --discovery-token-ca-cert-hash sha256:0f9fb6873b263cbd14b085ecb2054cd0f78ae15d4468afb547fcdc10ad43ac05



[root@k8s-master yum.repos.d]# mkdir -p $HOME/.kube
[root@k8s-master yum.repos.d]# sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
[root@k8s-master yum.repos.d]# sudo chown $(id -u):$(id -g) $HOME/.kube/config

2、分别在两个节点中执行

kubeadm join 192.168.189.128:6443 --token ndyb3v.iu7nolzawqaoxjm1 \
    --discovery-token-ca-cert-hash sha256:0f9fb6873b263cbd14b085ecb2054cd0f78ae15d4468afb547fcdc10ad43ac05
    
    
[root@k8s-node-01 yum.repos.d]# kubeadm join 192.168.189.128:6443 --token ndyb3v.iu7nolzawqaoxjm1 \
>     --discovery-token-ca-cert-hash sha256:0f9fb6873b263cbd14b085ecb2054cd0f78ae15d4468afb547fcdc10ad43ac05
[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.16" 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.

3、安装网络插件（CNI）master上执行

# 下载yaml文件
wget wget https://raw.githubusercontent.com/flannel-io/flannel/master/Documentation/kube-flannel.yml
# 修改net-conf.json下面的网段为上面init pod-network-cidr的网段地址（必须正确否则会导致集群网络问题）
10.244.0.0/16
# 修改完安装插件，执行
kubectl apply -f kube-flannel.yml
kubectl get pods -n kube-system


[root@k8s-master app]# kubectl apply -f kube-flannel.yml
podsecuritypolicy.policy/psp.flannel.unprivileged 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
[root@k8s-master app]# kubectl get pods --all-namespaces
NAMESPACE      NAME                                 READY   STATUS    RESTARTS   AGE
kube-flannel   kube-flannel-ds-ps59n                1/1     Running   0          109s
kube-flannel   kube-flannel-ds-rmff2                1/1     Running   0          109s
kube-flannel   kube-flannel-ds-xhtkx                1/1     Running   0          109s
kube-system    coredns-6d8c4cb4d-kdw8k              1/1     Running   0          6m56s
kube-system    coredns-6d8c4cb4d-qn6px              1/1     Running   0          6m56s
kube-system    etcd-k8s-master                      1/1     Running   0          7m10s
kube-system    kube-apiserver-k8s-master            1/1     Running   0          7m11s
kube-system    kube-controller-manager-k8s-master   1/1     Running   0          7m11s
kube-system    kube-proxy-mnmxn                     1/1     Running   0          4m5s
kube-system    kube-proxy-mz5bf                     1/1     Running   0          6m57s
kube-system    kube-proxy-prlqr                     1/1     Running   0          4m15s
kube-system    kube-scheduler-k8s-master            1/1     Running   0          7m11s
[root@k8s-master app]# kubectl get nodes
NAME          STATUS   ROLES                  AGE     VERSION
k8s-master    Ready    control-plane,master   7m15s   v1.23.0
k8s-node-01   Ready    <none>                 4m16s   v1.23.0
k8s-node-02   Ready    <none>                 4m6s    v1.23.0

# 安装成功

4、安装图形话界面

kubectl apply -f https://addons.kuboard.cn/kuboard/kuboard-v3.yaml
# 您也可以使用下面的指令，唯一的区别是，该指令使用华为云的镜像仓库替代 docker hub 分发 Kuboard 所需要的镜像
# kubectl apply -f https://addons.kuboard.cn/kuboard/kuboard-v3-swr.yaml

# 等待安装
# 查看是否成功
watch kubectl get pods -n kuboard

Every 2.0s: kubectl get pods -n kuboard                                                                                                 Wed Aug 30 02:31:37 2023
NAME                          READY   STATUS              RESTARTS   AGE
kuboard-etcd-tdg4q            1/1     Running             0          95s
kuboard-v3-56b4b954c9-n98v6   0/1     ContainerCreating   0          95s

访问 Kuboard
在浏览器中打开链接: http://192.168.189.128:30080
输入初始用户名和密码，并登录
用户名： admin
密码： Kuboard123

需要手动导入k8s集群

按照向导导入
成功显示界面

九、错误信息

1、初始化时失败 container runtime is not running

[root@k8s-master ~]# kubeadm init   --apiserver-advertise-address=192.168.189.128 --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
[init] Using Kubernetes version: v1.25.0
[preflight] Running pre-flight checks
error execution phase preflight: [preflight] Some fatal errors occurred:
        [ERROR CRI]: container runtime is not running: output: time="2023-08-29T23:18:56-04:00" level=fatal msg="validate service connection: CRI v1 runtime API is not implemented for endpoint \"unix:///var/run/containerd/containerd.sock\": rpc error: code = Unimplemented desc = unknown service runtime.v1.RuntimeService"
, error: exit status 1
[preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`
To see the stack trace of this error execute with --v=5 or higher
[root@k8s-master ~]# rm -rf /etc/containerd/config.toml
[root@k8s-master ~]# systemctl restart containerd
eassen_licd
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
linux 安装k8s
csdn问鼎
06-18 353
版本信息 1.配置yum 源 2.禁用部分配置 3.安装kubelet 4.使用docker 作容器 5.kubeadm init 6.安装flannel插件 7.去掉master 节点不能运行pod限制 8.安装dashboard 9.最后测试应用 注意事项
shell脚本安装k8s
10-08
shell脚本安装k8s,通过编写脚本，来实现k8s的安装，减少了一步一步安装的麻烦。相当于一键安装！
docker安装教程及启动报错解决方法 Linux下 CentOs7
weixin_43980461的博客
08-09 495
步骤： 前提是： Linux联网操作： 参照 https://blog.csdn.net/weixin_43980461/article/details/89257269 1.检查内核版本，必须是3.10及以上 命令：uname -r 2.如果需要升级内核版本，命令如下 yum update 3.安装docker，命令如下： yum install docker 选择y，进行下载 comp...
CentOS常见问题解决方案
Jerry's Home
08-07 763
问题1： 解决： 可参考：http://jetyi.blog.51cto.com/1460128/893450
Linux安装Kubernetes（k8s）详细教程
Meta39的博客
04-20 1837
Linux安装Kubernetes（k8s）详细教程
linux安装k8s
ko_10086的博客
08-11 1170
​安装docker、kubeadm，kubelet（master，node均需配置）（如果安装其它版本，可根据Getting Started with Kubernetes | Rancher Quick Start，中对应的版本来选择，并且可以安装Rancher的k8s视图管理）
Linux安装K8S单机服务
m0_61418822的博客
04-21 1107
安装方式不限这里我们的操作系统可以使用yum命令直接进行docker安装安装结束后查看版本信息docker -v启动服务、设置开机自启动。
Linux 安装k8s 我自己的宝藏
m0_65372269的博客
01-09 1029
【代码】Linux 安装k8s 我自己的宝藏。
k8s安装Nacos集群
05-21
k8s搭建Nacos集群，制作Nacos镜像 Nacos版本是：2.0.2
使用sealos安装k8s时的工具
11-05
而SealOS是一款专为简化k8s安装流程而设计的工具，它使得部署和管理k8s集群变得更加便捷。在《快速搭建云原生开发环境（k8s+pv+prometheus+grafana）》这篇文章中，SealOS扮演了关键的角色。 首先，我们来看一下...
K8S安装包之kubernetes-clinet-linux-amd64
04-25
K8S安装包之kubernetes-clinet-linux-amd64，下载可用
linux-一键部署k8s集群就是这么任性
08-13
一键部署k8s集群，就是这么任性，almost one-click deploy k8s manually
skywalking K8S集群下安装
最新发布
06-14
在 Kubernetes（K8S）集群环境下安装 SkyWalking 可以帮助我们更好地监控和诊断服务的运行状态。以下是对 SkyWalking 在 K8S 集群下安装的详细步骤和相关知识点的讲解。 一、SkyWalking 简介 SkyWalking 是一个开源...
K8S Linux Centos 7安装1
08-08
K8S Linux Centos 7安装1
k8s-linux上安装
jll126的博客
06-26 6441
目录1、环境准备1.1、服务器准备1.2、服务器hostname设置1.3、添加hosts 网络主机配置，三台虚拟机都要设置1.4、关闭防火墙，三台虚拟机都要设置，生产环境跳过这一步2、安装docker，3台服务器都安装3、安装kubeadmin加载k8s镜像3.1、添加kubernetes yum源3.2、查看kubeadm版本3.3、下载3.4、下载后，进入kubernetes包，发现kubectl和kubelet存在1.24.1版本3.4.1 删除1.24.1版本3.4.2 下载kubelet-1.1
Linux环境基于kubeadm安装k8s
weixin_44515412的博客
07-04 181
#1、禁用防火墙 #systemctl stop firewalld #systemctl disable firewalld #2、禁用SELINUX #vim /etc/sysconfig/selinux SELINUX=disabled #3、关闭swap内存 #swapoff -a #4、安装并启动docker #yum install docker #systemctl enable docker;systemctl start docker #5、编辑生成kubernetes的yum源
linux 使用kubeadm安装k8s
weixin_42871919的博客
05-06 315
容器部署到专门的工作节点上，以避免占用主节点的计算资源和可用性，并确保集群的正常运行。请注意，虽然Kubernetes 1.22及更高版本不需要手动加载IPVS内核模块，但是您必须确保所有运行Kubernetes节点的主机都已安装所需的软件包和依赖项，例如IPVS-utils和IPSet。在CentOS上安装Kubernetes之前，请确保在系统上安装了以下软件包：vim、curl、wget、git。相反，建议将其部署到专门的工作节点上，并使用Kubernetes特性来控制其位置和资源使用。
Linux 7.6 系统 k8s安装
HuangXiaoChuan
05-13 408
1、k8s安装步骤：master，nodes 用的一台主机121.36.104.222 1、所有机器上执行以下命令，准备安装环境：(注意是所有机器，主机master，从机node都要安装) 1.1、安装epel-release源 yum -y install epel-release 1.2、所有机器关闭防火墙 systemctl stop firewalld systemctl disable firewalldsetenforce 0#查看防火墙状态 firewall-c...
k8s安装linux
10-12
要在 Linux 上安装 Kubernetes，需要先安装 Docker 和 kubeadm 工具。以下是安装步骤： 1. 安装 Docker：可以通过官方文档进行安装，也可以使用系统包管理器进行安装。 2. 安装 kubeadm、kubelet 和 kubectl：可以...

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值