CentOS7配置Kubernetes（K8S）集群

最新推荐文章于 2023-08-16 09:33:18 发布
最新推荐文章于 2023-08-16 09:33:18 发布
阅读量208 收藏
点赞数
文章标签： 运维 python 开发工具
原文链接：https://my.oschina.net/daidetian/blog/1863506
版权

2019独角兽企业重金招聘Python工程师标准>>> hot3.png

1.物理环境

两台CentOS7机器，地址为192.168.0.51和192.168.0.61

1.1 机器信息

  1. 192.168.0.51 Master/etcd
  2. 192.168.0.61 Node

2. 部署主机

2.1 部署etcd

yum -y install etcd

yum安装的etcd默认配置文件在/etc/etcd/etcd.conf。编辑配置文件，更改为：

# [member]
ETCD_NAME=master
ETCD_DATA_DIR="/var/lib/etcd/default.etcd"
#ETCD_WAL_DIR=""
#ETCD_SNAPSHOT_COUNT="10000"
#ETCD_HEARTBEAT_INTERVAL="100"
#ETCD_ELECTION_TIMEOUT="1000"
#ETCD_LISTEN_PEER_URLS="http://0.0.0.0:2380"
ETCD_LISTEN_CLIENT_URLS="http://0.0.0.0:2379,http://0.0.0.0:4001"
#ETCD_MAX_SNAPSHOTS="5"
#ETCD_MAX_WALS="5"
#ETCD_CORS=""
#
#[cluster]
#ETCD_INITIAL_ADVERTISE_PEER_URLS="http://localhost:2380"
# if you use different ETCD_NAME (e.g. test), set ETCD_INITIAL_CLUSTER value for this name, i.e. "test=http://..."
#ETCD_INITIAL_CLUSTER="default=http://localhost:2380"
#ETCD_INITIAL_CLUSTER_STATE="new"
#ETCD_INITIAL_CLUSTER_TOKEN="etcd-cluster"
ETCD_ADVERTISE_CLIENT_URLS="http://192.168.0.51:2379,http://192.168.0.51:4001"
#ETCD_DISCOVERY=""
#ETCD_DISCOVERY_SRV=""
#ETCD_DISCOVERY_FALLBACK="proxy"
#ETCD_DISCOVERY_PROXY=""

启动并验证状态

[root@localhost ~]# vim /etc/etcd/etcd.conf
[root@localhost ~]# systemctl start etcd
[root@localhost ~]# etcdctl set testdir/testkey0 0
0
[root@localhost ~]# etcdctl get testdir/testkey0
0
[root@localhost ~]# etcdctl set testdir/testkey0 1
1
[root@localhost ~]# etcdctl get testdir/testkey0
1
[root@localhost ~]# etcdctl -C http://192.168.0.51:4001 cluster-health
member 8e9e05c52164694d is healthy: got healthy result from http://192.168.0.51:2379
cluster is healthy
[root@localhost ~]# etcdctl -C http://192.168.0.51:2379 cluster-health
member 8e9e05c52164694d is healthy: got healthy result from http://192.168.0.51:2379
cluster is healthy

2.2 部署master

安装kubernetes:

yum -y install kubernetes

安装kubernetes会安装docker，所以不单独再安装docker（如果安装docker版本过高会冲突，建议卸载原有docker） 启动Docker并开机启动

systemctl enable docker && systemctl start docker

在kubernetes master上需要运行以下组件：

　　　　Kubernets API Server

　　　　Kubernets Controller Manager

　　　　Kubernets Scheduler

修改配置：

2.2.1 /etc/kubernetes/apiserver

###
# kubernetes system config
#
# The following values are used to configure the kube-apiserver
#

# The address on the local server to listen to.
KUBE_API_ADDRESS="--insecure-bind-address=0.0.0.0"

# The port on the local server to listen on.
KUBE_API_PORT="--port=8080"

# Port minions listen on
# KUBELET_PORT="--kubelet-port=10250"

# Comma separated list of nodes in the etcd cluster
KUBE_ETCD_SERVERS="--etcd-servers=http://192.168.0.51:2379"

# Address range to use for services
KUBE_SERVICE_ADDRESSES="--service-cluster-ip-range=10.254.0.0/16"

# default admission control policies
#KUBE_ADMISSION_CONTROL="--admission-control=NamespaceLifecycle,NamespaceExists,LimitRanger,SecurityContextDeny,ServiceAccount,ResourceQuota"
KUBE_ADMISSION_CONTROL="--admission-control=NamespaceLifecycle,NamespaceExists,LimitRanger,SecurityContextDeny,ResourceQuota"

# Add your own!
KUBE_API_ARGS=""

这里去除ServiceAccount是为了跳过验证。

2.2.2 /etc/kubernetes/config

###
# kubernetes system config
#
# The following values are used to configure various aspects of all
# kubernetes services, including
#
#   kube-apiserver.service
#   kube-controller-manager.service
#   kube-scheduler.service
#   kubelet.service
#   kube-proxy.service
# logging to stderr means we get it in the systemd journal
KUBE_LOGTOSTDERR="--logtostderr=true"

# journal message level, 0 is debug
KUBE_LOG_LEVEL="--v=0"

# Should this cluster be allowed to run privileged docker containers
KUBE_ALLOW_PRIV="--allow-privileged=false"

# How the controller-manager, scheduler, and proxy find the apiserver
KUBE_MASTER="--master=http://192.168.0.51:8080"

设置开机启动并启动服务

[root@localhost kubernetes]# systemctl enable kube-apiserver.service
Created symlink from /etc/systemd/system/multi-user.target.wants/kube-apiserver.service to /usr/lib/systemd/system/kube-apiserver.service.
[root@localhost kubernetes]# systemctl start kube-apiserver.service
[root@localhost kubernetes]# systemctl enable kube-controller-manager.service
Created symlink from /etc/systemd/system/multi-user.target.wants/kube-controller-manager.service to /usr/lib/systemd/system/kube-controller-manager.service.
[root@localhost kubernetes]# systemctl start kube-controller-manager.service
[root@localhost kubernetes]# systemctl enable kube-scheduler.service
Created symlink from /etc/systemd/system/multi-user.target.wants/kube-scheduler.service to /usr/lib/systemd/system/kube-scheduler.service.
[root@localhost kubernetes]# systemctl start kube-scheduler.service

3. 部署节点

安装kubernetes

yum -y install kubernetes
systemctl enable docker && systemctl start docker

3.1 配置服务

在kubernetes node上需要运行以下组件：

　　　　Kubelet

　　　　Kubernets Proxy

修改配置：

3.1.1 /etc/kubernetes/config

###
# kubernetes system config
#
# The following values are used to configure various aspects of all
# kubernetes services, including
#
#   kube-apiserver.service
#   kube-controller-manager.service
#   kube-scheduler.service
#   kubelet.service
#   kube-proxy.service
# logging to stderr means we get it in the systemd journal
KUBE_LOGTOSTDERR="--logtostderr=true"

# journal message level, 0 is debug
KUBE_LOG_LEVEL="--v=0"

# Should this cluster be allowed to run privileged docker containers
KUBE_ALLOW_PRIV="--allow-privileged=false"

# How the controller-manager, scheduler, and proxy find the apiserver
KUBE_MASTER="--master=http://192.168.0.51:8080"

3.1.2 /etc/kubernetes/kubelet

###
# kubernetes kubelet (minion) config

# The address for the info server to serve on (set to 0.0.0.0 or "" for all interfaces)
KUBELET_ADDRESS="--address=0.0.0.0"

# The port for the info server to serve on
# KUBELET_PORT="--port=10250"

# You may leave this blank to use the actual hostname
KUBELET_HOSTNAME="--hostname-override=192.168.0.61"

# location of the api-server
KUBELET_API_SERVER="--api-servers=http://192.168.0.51:8080"

# pod infrastructure container
KUBELET_POD_INFRA_CONTAINER="--pod-infra-container-image=registry.access.redhat.com/rhel7/pod-infrastructure:latest"

# Add your own!
KUBELET_ARGS=""

设置开机启动并启动服务

[root@localhost kubernetes]# systemctl enable kubelet.service
Created symlink from /etc/systemd/system/multi-user.target.wants/kubelet.service to /usr/lib/systemd/system/kubelet.service.
[root@localhost kubernetes]# systemctl start kubelet.service
A dependency job for kubelet.service failed. See 'journalctl -xe' for details.
[root@localhost kubernetes]# systemctl enable kube-proxy.service
Created symlink from /etc/systemd/system/multi-user.target.wants/kube-proxy.service to /usr/lib/systemd/system/kube-proxy.service.
[root@localhost kubernetes]# systemctl start kube-proxy.service

这里发现kubelet未启动成功 查看日志

[root@localhost kubernetes]# journalctl -xe
--
-- Unit docker-storage-setup.service has begun starting up.
Jul 26 14:40:00 localhost.localdomain kernel: SELinux: initialized (dev overlay, type overlay), uses xattr
Jul 26 14:40:00 localhost.localdomain systemd[1]: docker-storage-setup.service: main process exited, code=exited, status=1/FAILURE
Jul 26 14:40:00 localhost.localdomain systemd[1]: Failed to start Docker Storage Setup.
-- Subject: Unit docker-storage-setup.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker-storage-setup.service has failed.
--
-- The result is failed.
Jul 26 14:40:00 localhost.localdomain systemd[1]: Unit docker-storage-setup.service entered failed state.
Jul 26 14:40:00 localhost.localdomain systemd[1]: docker-storage-setup.service failed.
Jul 26 14:40:00 localhost.localdomain systemd[1]: Starting Docker Application Container Engine...
-- Subject: Unit docker.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has begun starting up.
Jul 26 14:40:00 localhost.localdomain container-storage-setup[22194]: ERROR: XFS filesystem at /var has ftype=0, cannot use overlay backend; consider different driver or separate vol
Jul 26 14:40:01 localhost.localdomain dockerd-current[22281]: time="2018-07-26T14:40:00.993907399+08:00" level=info msg="libcontainerd: new containerd process, pid: 22293"
Jul 26 14:40:01 localhost.localdomain systemd[1]: Started Session 170 of user root.
-- Subject: Unit session-170.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-170.scope has finished starting up.
--
-- The start-up result is done.
Jul 26 14:40:01 localhost.localdomain CROND[22302]: (root) CMD (/usr/lib64/sa/sa1 1 1)
Jul 26 14:40:02 localhost.localdomain systemd[1]: Starting Session 170 of user root.
-- Subject: Unit session-170.scope has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-170.scope has begun starting up.
Jul 26 14:40:02 localhost.localdomain dockerd-current[22281]: time="2018-07-26T14:40:02.044621941+08:00" level=warning msg="overlay2: the backing xfs filesystem is formatted without
Jul 26 14:40:02 localhost.localdomain dockerd-current[22281]: Error starting daemon: SELinux is not supported with the overlay2 graph driver on this kernel. Either boot into a newer
Jul 26 14:40:02 localhost.localdomain systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE
Jul 26 14:40:02 localhost.localdomain systemd[1]: Failed to start Docker Application Container Engine.

注意到Error starting daemon: SELinux is not supported with the overlay2 graph driver on this kernel. Either boot into a newer，根据报错信息找到是启动docker出错，原因则是当前kernel不支持overlay2，解决方案为关闭selinux或者使用新的kernel。这里我直接关闭selinux。

[root@localhost kubernetes]# vim /etc/sysconfig/docker

# /etc/sysconfig/docker

# Modify these options if you want to change the way the docker daemon runs
OPTIONS='--selinux-enabled=false --log-driver=journald --signature-verification=false'
if [ -z "${DOCKER_CERT_PATH}" ]; then
    DOCKER_CERT_PATH=/etc/docker
fi

然后重新启动kubelet

systemctl start kubelet.service

查看结果：

[root@localhost kubernetes]#  kubectl -s http://192.168.0.51:8080/ get node
NAME           STATUS    AGE
192.168.0.61   Ready     12m

在master上可以直接查看

[root@localhost kubernetes]# kubectl get node
NAME           STATUS    AGE
192.168.0.61   Ready     1m

注意到这里的AGE不同，目前还不清楚原因，做个记录。

4. 部署Flannel

在所有节点（包括master和node）上安装flannel

yum -y install flannel

4.1 修改配置

所有节点修改/etc/sysconfig/flanneld

[root@localhost kubernetes]# vim /etc/sysconfig/flanneld

# Flanneld configuration options

# etcd url location.  Point this to the server where etcd runs
FLANNEL_ETCD_ENDPOINTS="http://192.168.0.51:2379"

# etcd config key.  This is the configuration key that flannel queries
# For address range assignment
FLANNEL_ETCD_PREFIX="/atomic.io/network"

# Any additional options that you want to pass
#FLANNEL_OPTIONS=""

4.2 修改etc配置

Flannel使用Etcd进行配置，来保证多个Flannel实例之间的配置一致性，所以需要在etcd上进行如下配置：（‘/atomic.io/network/config’这个key与上文/etc/sysconfig/flannel中的配置项FLANNEL_ETCD_PREFIX是相对应的，错误的话启动就会出错）

etcdctl mk /atomic.io/network/config '{ "Network": "10.0.0.0/16" }'

4.3 启动

启动Flannel之后，需要依次重启docker、kubernete。 master:

systemctl enable flanneld.service
systemctl start flanneld.service
systemctl restart docker
systemctl restart kube-apiserver.service
systemctl restart kube-controller-manager.service
systemctl restart kube-scheduler.service

node:

systemctl enable flanneld.service
systemctl start flanneld.service
systemctl restart docker
systemctl restart kubelet.service
systemctl restart kube-proxy.service

转载于:https://my.oschina.net/daidetian/blog/1863506

weixin_34413065
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
CentOS7 部署K8S集群
carooo的博客
01-26 838
虚拟机： Oracle VM Virtualbox 操作系统：CentOS Linux release 7.6.1810 (Core) 查看操作版本命令：cat /etc/redhat-release 部署规划 192.168.1.164 k8s-master 192.168.1.189 k8s-node1 192.168.1.203 k8s-node2 备注：第1步~第8步，所有的节点都要操作，第9、10步Master节点操作，第11步Node节点操作。 如果第9、10、11步
CentOS7环境下Spark集群的配置
学习笔记
07-02 1119
1. 解压缩到/home/hadoop/ spark-2.2.0 scala-2.11.7 2. 配置环境变量/etc/profile 为避免与hadoop默认启动命令同名,spark/sbin中的start-all.sh和stop-all.sh分别改为start-spark-all.sh和stop-spark-all.sh scala写入bin spark写入bin和sbin 3...
Centos7安装K8S集群环境
菜鸟六十八@驿站
05-08 1万+
文章目录一、系统设置环境1、关闭swap2、 关闭SELinux3、关闭防火墙3、配置sysctl4、配置安装源为阿里4.1 配置yum安装源4.2 配置k8s源4.3 重建yum缓存二、安装docker1、安装docker2、docker配置3、重启docker三、集群安装1、安装kubeadm, kubelet和kubectl2、使用kubeadm创建集群3、用户设置权限(root用户也需要执行)4、应用flannel网络5、节点加入四、安装网页界面 (Dashboard)参考资料 一、系统设置 环境
记一次kubernetes+docker部署一个pod的全过程
majixiang1996的博客
05-12 4830
1、首先从vSphere中创建一个基本的CentOS7.2的虚拟机 2、创建完成后安装kubernetes和docker 2.1关闭防火墙 [root@kubernetes-m ~]# systemctl disable firewalld Removed symlink /etc/systemd/system/dbus-org.fedoraproject.Firewal...
ERROR: XFS filesystem at /var has ftype=0, cannot use overlay backend；
weixin_45014813的博客
08-16 136
ERROR: XFS filesystem at /var has ftype=0, cannot use overlay backend;
kubernetes1.16 错误排查
运维Carl的博客
12-08 1万+
目录一.环境说明1.使用kubectl get node命令，查看集群的状态。2.到node节点查看组件的状态3.于是我查看master节点的apiserver日志4.查看etcd集群的健康状态，并检查192.168.1.123节点上的etcd服务是否正常；5.问题猜测，并尝试解决6.再次查看K8S节点，已恢复正常，并查看etcd集群健康状态，已正常； 一.环境说明 一.环境说明 操作系统：cen...
部署Kubernetes集群 - v1.18.1
majixiang1996的博客
04-13 3352
链接：https://pan.baidu.com/s/1d9QuB8sm9qme73Rrm551Pw 提取码：rozu
在centos 7中安装配置k8s集群的步骤详解
09-15
在CentOS 7中搭建Kubernetes (k8s) 集群是一项复杂但至关重要的任务，特别是对于希望实现高效容器化应用管理的企业而言。Kubernetes是由Google开发的开源容器编排系统，它提供了强大的应用部署、管理和扩展功能，...
CentOS 7.9 最小化安装 kubernetes（k8s）1.25.3（免费下载）
11-23
在本教程中，我们将深入探讨如何在CentOS 7.9最小化安装环境中部署Kubernetes（简称k8s）版本1.25.3。Kubernetes是一个开源的容器编排系统，用于自动化容器化应用程序的部署、扩展和管理。CentOS作为一款稳定的Linux...
CentOS7+Kubeadm+K8S集群安装手册
最新发布
02-17
在Centos中利用kubeadm工具安装和部署一个原生的kubernetes集群
CentOS7使用Kubeadm安装K8S集群
05-31
在Centos中利用kubeadm工具安装和部署一个原生的kubernetes集群
部署k8s监控(1.1)：Prometheus-operator监控k8s集群的各个组件及pod（二进制环境）
向上的信念
05-19 1535
环境是使用二进制安装的，使用kubeadm则很难遇到这种情况 一、下载安装文件 [root@k8s-master1 prometheus]# git clone https://github.com/coreos/kube-prometheus.git [root@k8s-master1 prometheus]# cd ./kube-prometheus/manifests/ 二、修改yaml文件（开启nodeport,方便外网用户访问） [root@k8s-master1 manifests]#
yum安装k8s集群(kubernetes)
weixin_30530939的博客
03-13 538
此案例是以一个主，三个node来部署的，当然node可以根据自己情况部署 192.168.1.130 master 192.168.1.131 node1 192.168.1.132 node2 192.168.1.133 node3合法的 Enable NTP on master and all nodes : [root@k-master ~]# yum -y insta...
安装Docker启动失败，A dependency job for docker.service failed.
热门推荐
菜鸟六十八@驿站
04-21 2万+
安装Docker后，启动失败，报错如下： [root@st01015vm192 ~]# sudo service docker start Redirecting to /bin/systemctl start docker.service A dependency job for docker.service failed. See 'journalctl -xe' for details. [...
logstash启动失败解决
dinangjia2168的博客
09-25 5975
安装的是最新7.X系列首先要写repo文件 /etc/yum.repos.d/elasticsearch.repo [elasticsearch-7.x] name=Elasticsearch repository for 7.x packages baseurl=https://artifacts.elastic.co/packages/7.x/yum gpgcheck=...
centos7 sftp设置后 ssh 启动失败 原因分析
anshuye8780的博客
02-07 4619
大多数人 在 设置SFTP 使用时，会在 ../sshd_config中添加如下内容： ------------------------------- Subsystem sftp internal-sftpMatch Group sftpChrootDirectory /dataForceCommand internal-sftpAllowTcpForwarding noX1...
kubernetes-二进制部署的时候，遇到kubelet启动失败，服务报错Unit kubelet.service entered failed state.
做人如果没有梦想，那跟咸鱼有什么区别--周星驰
02-25 5223
博主最近在学习二进制部署k8s，在node上部署kubelet组件时遇到错误。 作为一个新手，遇见这个问题慌得一批，完全不知道如何下手，百度也看不懂。 这个分享一下解决得思路： 一、检查node节点，kubelet得bin命令是否拷贝 用cp 命令把二进制包里面得命令复制到你kubernetes的工作目录 二、检查node节点，ssl证书是否拷贝，跟主节点是否一致 在master节点生成了证书后，记得复制过去 三、对比跟node和master的bootstr
实战：kubeadm方式搭建k8s集群(containerd)-20211102
weixin_39246554的博客
11-02 887
目录 文章目录目录文档版本实验环境实验软件1、集群环境配置(all节点均要配置)1.1配置主机名1.2关闭防火墙，selinux1.3关闭swap分区1.4配置dns解析1.5将桥接的IPv4流量传递到iptables的链1.6安装 ipvs1.7同步服务器时间1.8配置免密(方便后期从master节点传文件到node节点)2、安装 Containerd(all节点均要配置)2.1安装containerd2.2将 containerd 的 cgroup driver 配置为 systemd2.3配置镜像加.
CentOS7使用kubeadm搭建Kubernetes集群指南
本手册详细介绍了如何在CentOS7操作系统中使用kubeadm工具安装和部署一个原生的Kubernetes（K8S）集群。Kubernetes是一种流行的容器编排系统，它能够自动化容器化应用的部署、扩展和管理。Kubeadm是Kubernetes官方...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值