安科网

CentOS系列教程（八）

lizhengfa

lizhengfa

2020-04-15

关注 关注
本文是 kubernets集群实验部署前的准备操作。

以下是操作过程：

设置主机名及配置hosts

[ master]# hostnamectl set-hostname kubernetes-master
[ master]# hostnamectl status
Static hostname: kubernetes-master
Icon name: computer-vm
Chassis: vm
Machine ID: 6191eb7683f84b63a36c1c4d8a68fcfb
Boot ID: 92e6aa3941f048f8a5ef99d86b30e990
Virtualization: vmware
Operating System: CentOS Linux 7 (Core)
CPE OS Name: cpe:/o:centos:centos:7
Kernel: Linux 3.10.0-862.el7.x86_64
Architecture: x86-64
[ master]# cat >> /etc/hosts << EOF

192.168.20.195 kubernetes-master
192.168.20.196 kubernetes-node00
192.168.20.197 kubernetes-node01
EOF
[ master]# cat -n /etc/hosts
1 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
2 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
3 192.168.20.195 kubernetes-master
4 192.168.20.196 kubernetes-node00
5 192.168.20.197 kubernetes-node01
[ master]#

[ work0]# hostnamectl set-hostname kubernetes-node00
[ work0]# hostnamectl status
Static hostname: kubernetes-node00
Icon name: computer-vm
Chassis: vm
Machine ID: 6bfc0a20ffc345c0b9a6e8f183b41ab5
Boot ID: 6312a3bd740e4718b6e102120957769f
Virtualization: vmware
Operating System: CentOS Linux 7 (Core)
CPE OS Name: cpe:/o:centos:centos:7
Kernel: Linux 3.10.0-862.el7.x86_64
Architecture: x86-64
[ work0]# cat >> /etc/hosts << EOF
192.168.20.195 kubernetes-master
192.168.20.196 kubernetes-node00
192.168.20.197 kubernetes-node01
EOF
[ work0]# cat -n /etc/hosts
1 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
2 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
3 192.168.20.195 kubernetes-master
4 192.168.20.196 kubernetes-node00
5 192.168.20.197 kubernetes-node01
[ work0]#

[ work1]# hostnamectl set-hostname kubernetes-node01
[ work1]# hostnamectl status
Static hostname: kubernetes-node01
Icon name: computer-vm
Chassis: vm
Machine ID: 8a968f63778d447587873c082ee483d1
Boot ID: b33f693a1d8149238a5e8fabd263b383
Virtualization: vmware
Operating System: CentOS Linux 7 (Core)
CPE OS Name: cpe:/o:centos:centos:7
Kernel: Linux 3.10.0-862.el7.x86_64
Architecture: x86-64
[ work1]# cat >> /etc/hosts << EOF
192.168.20.195 kubernetes-master
192.168.20.196 kubernetes-node00
192.168.20.197 kubernetes-node01
EOF
[ work1]# cat -n /etc/hosts
1 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
2 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
3 192.168.20.195 kubernetes-master
4 192.168.20.196 kubernetes-node00
5 192.168.20.197 kubernetes-node01
[ work1]#
###########################################################

master与nodes间的免密登录

【注意：此操作只需要在master机器上执行，两个work机器不需要做任何操作】
[ 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:XpMV6NEsm+8MCpqpxgMWkf6/UuAH9zmB8E10uzirkf8
The key‘s randomart image is:
+---[RSA 2048]----+
| . .. . +. |
| o . .. = o. |
|. . o + o =. |
| o o + o. =o |
| + + .oS.+. |
|.. o oo=o.... |
|.o +* oo. + |
| +.+.+ . o |
| ..o.o...E |
+----[SHA256]-----+
[ master]# ssh-copy-id -i /root/.ssh/id_rsa.pub
/usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/root/.ssh/id_rsa.pub"
The authenticity of host ‘192.168.20.196 (192.168.20.196)‘ can‘t be established.
ECDSA key fingerprint is SHA256:aDoeqgH+fD1Ur/WdpYlNjuIY0t5iH5PuT0ewPkQ64PQ.
ECDSA key fingerprint is MD5:8f:3a:d5:e2:ee:d5:60:3c:9c:f7:28:1e:70:0d:64:5f.
Are you sure you want to continue connecting (yes/no)? 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
‘s password:

Number of key(s) added: 1

Now try logging into the machine, with: "ssh ‘‘"
and check to make sure that only the key(s) you wanted were added.

[ master]# ssh-copy-id -i /root/.ssh/id_rsa.pub
/usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/root/.ssh/id_rsa.pub"
The authenticity of host ‘192.168.20.197 (192.168.20.197)‘ can‘t be established.
ECDSA key fingerprint is SHA256:a6PG3JgmZaDRZXGwMq5C1MamuiAbXah+/72QDqp02lA.
ECDSA key fingerprint is MD5:52:f9:b9:17:83:75:d0:26:15:48:88:09:89:dc:73:ce.
Are you sure you want to continue connecting (yes/no)? 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
‘s password:

Number of key(s) added: 1

Now try logging into the machine, with: "ssh ‘‘"
and check to make sure that only the key(s) you wanted were added.

[ master]# ssh
Last login: Tue Apr 14 19:45:04 2020
[ ~]# ls
anaconda-ks.cfg initial-setup-ks.cfg
[ ~]# exit
logout
Connection to 192.168.20.196 closed.
[ master]# ssh
Last login: Tue Apr 14 19:47:14 2020
[ ~]# ls
anaconda-ks.cfg initial-setup-ks.cfg
[ ~]# exit
logout
Connection to 192.168.20.197 closed.
[ master]#
##########################################################

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

[ master]# modprobe br_netfilter
[ master]# sysctl -p
[ master]# sysctl --system

  • Applying /usr/lib/sysctl.d/00-system.conf ...
    net.bridge.bridge-nf-call-ip6tables = 0
    net.bridge.bridge-nf-call-iptables = 0
    net.bridge.bridge-nf-call-arptables = 0
  • Applying /usr/lib/sysctl.d/10-default-yama-scope.conf ...
    kernel.yama.ptrace_scope = 0
  • Applying /usr/lib/sysctl.d/50-default.conf ...
    kernel.sysrq = 16
    kernel.core_uses_pid = 1
    net.ipv4.conf.default.rp_filter = 1
    net.ipv4.conf.all.rp_filter = 1
    net.ipv4.conf.default.accept_source_route = 0
    net.ipv4.conf.all.accept_source_route = 0
    net.ipv4.conf.default.promote_secondaries = 1
    net.ipv4.conf.all.promote_secondaries = 1
    fs.protected_hardlinks = 1
    fs.protected_symlinks = 1
  • Applying /usr/lib/sysctl.d/60-libvirtd.conf ...
    fs.aio-max-nr = 1048576
  • Applying /etc/sysctl.d/99-sysctl.conf ...
  • Applying /etc/sysctl.d/k8s.conf ...
    net.bridge.bridge-nf-call-ip6tables = 1
    net.bridge.bridge-nf-call-iptables = 1
  • Applying /etc/sysctl.conf ...
    [ master]#

    [ work0]# cat > /etc/sysctl.d/k8s.conf << EOF

    net.bridge.bridge-nf-call-ip6tables = 1
    net.bridge.bridge-nf-call-iptables = 1
    EOF
    [ work0]# modprobe br_netfilter
    [ work0]# sysctl -p
    [ work0]# sysctl --system

  • Applying /usr/lib/sysctl.d/00-system.conf ...
    net.bridge.bridge-nf-call-ip6tables = 0
    net.bridge.bridge-nf-call-iptables = 0
    net.bridge.bridge-nf-call-arptables = 0
  • Applying /usr/lib/sysctl.d/10-default-yama-scope.conf ...
    kernel.yama.ptrace_scope = 0
  • Applying /usr/lib/sysctl.d/50-default.conf ...
    kernel.sysrq = 16
    kernel.core_uses_pid = 1
    net.ipv4.conf.default.rp_filter = 1
    net.ipv4.conf.all.rp_filter = 1
    net.ipv4.conf.default.accept_source_route = 0
    net.ipv4.conf.all.accept_source_route = 0
    net.ipv4.conf.default.promote_secondaries = 1
    net.ipv4.conf.all.promote_secondaries = 1
    fs.protected_hardlinks = 1
    fs.protected_symlinks = 1
  • Applying /usr/lib/sysctl.d/60-libvirtd.conf ...
    fs.aio-max-nr = 1048576
  • Applying /etc/sysctl.d/99-sysctl.conf ...
  • Applying /etc/sysctl.d/k8s.conf ...
    net.bridge.bridge-nf-call-ip6tables = 1
    net.bridge.bridge-nf-call-iptables = 1
  • Applying /etc/sysctl.conf ...
    [ work0]#

    [ work1]# cat > /etc/sysctl.d/k8s.conf << EOF

    net.bridge.bridge-nf-call-ip6tables = 1
    net.bridge.bridge-nf-call-iptables = 1
    EOF
    [ work1]# modprobe br_netfilter
    [ work1]# sysctl -p
    [ work1]# sysctl --system

  • Applying /usr/lib/sysctl.d/00-system.conf ...
    net.bridge.bridge-nf-call-ip6tables = 0
    net.bridge.bridge-nf-call-iptables = 0
    net.bridge.bridge-nf-call-arptables = 0
  • Applying /usr/lib/sysctl.d/10-default-yama-scope.conf ...
    kernel.yama.ptrace_scope = 0
  • Applying /usr/lib/sysctl.d/50-default.conf ...
    kernel.sysrq = 16
    kernel.core_uses_pid = 1
    net.ipv4.conf.default.rp_filter = 1
    net.ipv4.conf.all.rp_filter = 1
    net.ipv4.conf.default.accept_source_route = 0
    net.ipv4.conf.all.accept_source_route = 0
    net.ipv4.conf.default.promote_secondaries = 1
    net.ipv4.conf.all.promote_secondaries = 1
    fs.protected_hardlinks = 1
    fs.protected_symlinks = 1
  • Applying /usr/lib/sysctl.d/60-libvirtd.conf ...
    fs.aio-max-nr = 1048576
  • Applying /etc/sysctl.d/99-sysctl.conf ...
  • Applying /etc/sysctl.d/k8s.conf ...
    net.bridge.bridge-nf-call-ip6tables = 1
    net.bridge.bridge-nf-call-iptables = 1
  • Applying /etc/sysctl.conf ...
    [ work1]#
    ########################################################

    配置docker和kubernetes YUM软件源

    [ master]# wget -O /etc/yum.repos.d/docker-ce.repo https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo
    --2020-04-14 21:59:42-- https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo
    Resolving mirrors.aliyun.com (mirrors.aliyun.com)... 111.6.206.244, 111.6.206.243, 111.6.206.242, ...
    Connecting to mirrors.aliyun.com (mirrors.aliyun.com)|111.6.206.244|:443... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 2640 (2.6K) [application/octet-stream]
    Saving to: ‘/etc/yum.repos.d/docker-ce.repo’

100%[=============================================>] 2,640 --.-K/s in 0s

2020-04-14 21:59:42 (846 MB/s) - ‘/etc/yum.repos.d/docker-ce.repo’ saved [2640/2640]

[ 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
[ master]# ls -F /etc/yum.repos.d/
CentOS-Base.repo CentOS-fasttrack.repo docker-ce.repo
CentOS-Base.repo.original0 CentOS-Media.repo kubernetes.repo
CentOS-CR.repo CentOS-Sources.repo
CentOS-Debuginfo.repo CentOS-Vault.repo
[ master]#

[ work0]# wget -O /etc/yum.repos.d/docker-ce.repo https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo
--2020-04-14 22:01:53-- https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo
Resolving mirrors.aliyun.com (mirrors.aliyun.com)... 111.6.206.245, 111.6.206.246, 111.6.206.244, ...
Connecting to mirrors.aliyun.com (mirrors.aliyun.com)|111.6.206.245|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2640 (2.6K) [application/octet-stream]
Saving to: ‘/etc/yum.repos.d/docker-ce.repo’

100%[=============================================>] 2,640 --.-K/s in 0s

2020-04-14 22:01:53 (970 MB/s) - ‘/etc/yum.repos.d/docker-ce.repo’ saved [2640/2640]

[ work0]# 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
[ work0]# ls -F /etc/yum.repos.d/
CentOS-Base.repo CentOS-fasttrack.repo docker-ce.repo
CentOS-Base.repo.original0 CentOS-Media.repo kubernetes.repo
CentOS-CR.repo CentOS-Sources.repo
CentOS-Debuginfo.repo CentOS-Vault.repo
[ work0]#

[ work1]# wget -O /etc/yum.repos.d/docker-ce.repo https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo
--2020-04-14 22:02:06-- https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo
Resolving mirrors.aliyun.com (mirrors.aliyun.com)... 111.6.206.245, 111.6.206.246, 111.6.206.244, ...
Connecting to mirrors.aliyun.com (mirrors.aliyun.com)|111.6.206.245|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2640 (2.6K) [application/octet-stream]
Saving to: ‘/etc/yum.repos.d/docker-ce.repo’

100%[=========================================================================================================>] 2,640 --.-K/s in 0s

2020-04-14 22:02:06 (1.33 GB/s) - ‘/etc/yum.repos.d/docker-ce.repo’ saved [2640/2640]

[ work1]# 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
[ work1]# ls -F /etc/yum.repos.d/
CentOS-Base.repo CentOS-CR.repo CentOS-fasttrack.repo CentOS-Sources.repo docker-ce.repo
CentOS-Base.repo.original0 CentOS-Debuginfo.repo CentOS-Media.repo CentOS-Vault.repo kubernetes.repo
[ work1]#

孟伯，20200411

交流联系：微信 1807479153 ，QQ 1807479153

master centos localhost kubernetes hosts

lizhengfa

lizhengfa

0 关注 0 粉丝 0 动态

关注 关注

相关推荐

Redis面试8连问，你能顶住几道？

出现实例宕机自动进行主备切换，配置读写分离缓解Master读写压力。使用官方推荐的哨兵机制就能实现，当主节点出现故障时，由Sentinel自动完成故障发现和转移，并通知应用方，实现高可用性。集群监控，负责监控redis master和slave进程是否正常

聚合室 2020-09-30

Redis服务之高可用组件sentinel详解

有没有这样的一组件帮我们对master做实时的监控，一旦发现master宕机就提升一个slave当选新的master，如果原master还有其他slave，将其他slave都从属于新的master；除此之外它还应该让系统在发生切换master时触发报警通知

wera00 2020-08-17

Redis集群详解

主从模式是三种模式中最简单的，在主从复制中，数据库分为两类：主数据库和从数据库。* master挂了以后，不影响slave的读，但redis不再提供写服务，master重启后redis将重新对外提供写服务。当slave启动后，主动向master发送SYNC

DiamondTao 2020-08-17

Centos7部署redis主从复制及哨兵架构

redis是一个key-value存储系统。在此基础上，redis支持各种不同方式的排序，与memcached一样，为了保证效率，数据都是缓存在内存中，区别的是redis会周期性的把更新的数据写入磁盘或者把修改操作写入追加的记录文件，并且在此基础上实现了m

rongxionga 2020-07-26

MySQL高可用之MHA

MHA Node运行在每台 MySQL服务器上，MHA Manager会定时探测集群中的master节点，当master出现故障时，它可以自动将最新 数据的slave提升为新的master，然后将所有其他的slave重新指向新的master。整个故障转移过

herohope 2020-07-19

SpringBoot集成Redis集群

只需要修改为如下集群模式的配置。　　这里的集群架构为redis 3主3从

王道革 2020-07-05

git学习(2)-分支管理

其中 git 为我们创建了一个默认的 master 分支，也叫主分支。运行命令，会发现没有任何的提示内容，但我们的分支其实已经创建成功了。可以看到原本多了一个我们新创建的 dev 分支。上边我们也说到了，分支前边有 * 号才代表当前处于哪一条分支上，那怎么

nebulali 2020-07-05

Redis 哨兵机制和实现

如果Redis主挂了，两个redis从不能进行写操作，将导致redis不可用。Redis从也不会自动转为Redis主。这时候哨兵机制就很好的解决了这个问题。新的redis主和redis从重新组成redis主从模式。往往一个哨兵是不够的，通常是一个哨兵集群。

kaixinfelix 2020-07-04

Redis 主从集群，从机配置内容

# 可以通过将这个值设为 1 来保证每次只有一个slave 处于不能处理命令请求的状态。#如果5秒后,mysater仍没启动过来，则启动failoversentinel failover-timeout mymaster 5000. # 设置连接maste

bruce 2020-06-28

Elasticsearch 是如何实现 Master 选举的？

些节点需要 ping 通）这两部分；节点，暂且认为它是 master 节点。否则重新选举一直到满足上。别的管理；data 节点可以关闭 http 功能*。

YEEHOLIC 2020-06-26

git 把分支代码合并给master主分支

3. 一般多人开发需要pull，建议都pull一下，比如：单独开发有时后台会“帮”你改东改西。。。

guying 2020-06-16

Mysql通过MHA实现高可用

MHA是一款开源的 MySQL 的高可用程序，它为 MySQL 主从复制架构提供了 automating master failover 功能。MHA 在监控到 master 节点故障时，会提升其中拥有最新数据的 slave 节点成为新的master 节点

KFLING 2020-06-13

【华为云技术分享】数据库开发：MySQL Seconds_Behind_Master简要分析

Definition：The number of seconds that the slave SQL thread is behind processing the master binary log.主库binlog中事件的时间。以一个包含两条inse

贤冰 2020-06-12

redis主从复制

　　redis的高并发有一种实现方式就是主从架构，一个master节点，多个slave节点，可以很好的实现slave节点的水平扩容；主从架构再加上读写分离，master节点负责写操作，slave节点负责读操作，使得redis可以很好的做一个高并发的处理。有

qingmuluoyang 2020-06-10

master烧饼(哨兵)模式

将宕机的master下线找一个salve作为master通知所有的slave连接新的master启动新的Master与slave全量复制N+部分复制N谁来确认master宕机了找一个？怎么找法修改配置后，原始的主恢复了怎么办？哨兵简介哨兵是一个分布式系统，

Smileyou 2020-06-09

一条命令实现centos安装最新nodejs

此外，由于政策原因，github上的资源可能会墙掉，安装失败时请重复执行此命令直到成功安装

xinlugang 2020-06-08

redis-cluster集群

redis哨兵模式:redis集群会有一个Master节点和多个Slave节点，通过Master节点写入数据到redis，然后Copy Master中的数据到Slaver节点的redis中，slave有多个，一个Master和多个Slave组成集群，从集群

afanti 2020-06-08

redis主从同步原理及优化

主从复制：主从复制将master中的数据即时、有效的复制到slave中，特征：一个master可以拥有多个salve,g，一个slave只对应一个master。

Smileyou 2020-06-05

本地项目上传到gitlab

git add .git branch master (删除本地分支：git branch -d master). git push -u origin master (删除远程分支：git push origin --delete maste

Earlyuan 2020-06-03

MySQL5.7配置GTID双主

grant replication slave on *.* to ‘ops‘@‘192.168.10.%‘ identified by ‘ops123‘;mysqldump -uroot -p --single-transaction --default

wanjichun 2020-06-02
lizhengfa

lizhengfa

W3CSchool教程
HTML 教程
CSS 教程
Bootstrap 教程
Javascript 教程
jQuery 教程
后端教程
C 教程
Java 教程
PHP 教程
Python 教程
Go 教程
移动开发
Android 教程
Swift 教程
Kotlin 教程
jQuery Mobile 教程
ionic 教程
关于我们
新闻动态
联系方式
招聘英才
安科实验室
帮助与反馈

安科网(Ancii)，中国第一极客网

Copyright © 2013 - 2019 Ancii.com

京ICP备18063983号 京公网安备11010802014868号