首页 / K8S / centos7 使用kubeadm部署k8s

centos7 使用kubeadm部署k8s

内容导读

互联网集市收集整理的这篇技术教程文章主要介绍了centos7 使用kubeadm部署k8s，小编现在分享给大家，供广大互联网技能从业者学习和参考。文章包含14234字，纯文字阅读大概需要21分钟。

内容图文

配置环境

本次配置共准备master、node1、node2三台服务器，环境配置三台机器保持同步

1.安装docker

参考文章centos安装docker

2.关闭防火墙

关闭防火墙并禁用开机启动

systemctl stop firewalld & systemctl disable firewalld

3.关闭Swap

目的在于防止内存交换影响性能以及稳定性

swapoff -a可临时关闭，系统重启后恢复
编辑/etc/fstab注释包含swap一行重启之后可永久关闭
快速命令：

swapoff -a
sed -i '/swap/s/^/#/' /etc/fstab

4.关闭SeLinux

目的在于允许容器访问宿主机的文件系统

setenforce 0
sed -i "s/SELINUX=enforcing/SELINUX=disabled/g" /etc/selinux/config

5.配置k8s国内yum源

由于墙的存在，需要配置国内的下载源，使用如下命令添加

cat <<EOF > /etc/yum.repos.d/kubernetes.repo

[kubernetes]

name=Kubernetes

baseurl=http://mirrors.aliyun.com/kubernetes/yum/repos/kubernetes-el7-x86_64

enabled=1

gpgcheck=0

repo_gpgcheck=0

gpgkey=http://mirrors.aliyun.com/kubernetes/yum/doc/yum-key.gpg

        http://mirrors.aliyun.com/kubernetes/yum/doc/rpm-package-key.gpg

EOF

6.修改docker引擎

修改docker cgroup驱动，与k8s一致，防止因为引擎不一致而导致的启动错误

vi /etc/docker/daemon.json

{
  "exec-opts": ["native.cgroupdriver=systemd"],
  "log-driver": "json-file",
  "log-opts": {
    "max-size": "100m"
  },
  "storage-driver": "overlay2",
  "storage-opts": [
    "overlay2.override_kernel_check=true"
  ],
  "registry-mirrors": ["https://registry.docker-cn.com","http://hub-mirror.c.163.com"]
}

执行如下命令重启docker

systemctl daemon-reload
systemctl restart docker

7.安装k8s组件

执行命令(所有节点机都需要安装)

# 下载相关组件
yum install -y kubelet-1.15.1 kubeadm-1.15.1 kubectl-1.15.1
# 设置开机启动 kubelet
systemctl enable --now kubelet

8.设置路由

centos7需要设置路由

yum install -y bridge-utils.x86_64

# 加载br_netfilter模块，使用lsmod查看开启的模块
modprobe  br_netfilter

# 修改配置文件
cat <<EOF >  /etc/sysctl.d/k8s.conf
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1
EOF

# 重新加载配置文件
sysctl --system

创建集群

集群创建master机器与node机器有所区别，文中会做出区分

1.拉取集群所需镜像

把所需的镜像下载好，init的时候就不会再拉镜像，由于无法连接google镜像库导致出错

首先拉取国内对应镜像资源

master服务器：

docker pull mirrorgooglecontainers/kube-apiserver:v1.15.1
docker pull mirrorgooglecontainers/kube-controller-manager:v1.15.1
docker pull mirrorgooglecontainers/kube-scheduler:v1.15.1
docker pull mirrorgooglecontainers/kube-proxy:v1.15.1
docker pull mirrorgooglecontainers/pause:3.1
docker pull mirrorgooglecontainers/etcd:3.3.10
docker pull coredns/coredns:1.3.1

node服务器：

docker pull mirrorgooglecontainers/kube-proxy:v1.15.1
docker pull mirrorgooglecontainers/pause:3.1

将镜像tag名称修改为k8s官方一致

master服务器：

docker tag mirrorgooglecontainers/kube-apiserver:v1.15.1 k8s.gcr.io/kube-apiserver:v1.15.1
docker tag mirrorgooglecontainers/kube-controller-manager:v1.15.1 k8s.gcr.io/kube-controller-manager:v1.15.1
docker tag mirrorgooglecontainers/kube-scheduler:v1.15.1 k8s.gcr.io/kube-scheduler:v1.15.1
docker tag mirrorgooglecontainers/kube-proxy:v1.15.1 k8s.gcr.io/kube-proxy:v1.15.1
docker tag mirrorgooglecontainers/pause:3.1 k8s.gcr.io/pause:3.1
docker tag mirrorgooglecontainers/etcd:3.3.10 k8s.gcr.io/etcd:3.3.10
docker tag coredns/coredns:1.3.1 k8s.gcr.io/coredns:1.3.1

node服务器：

docker tag mirrorgooglecontainers/kube-proxy:v1.15.1 k8s.gcr.io/kube-proxy:v1.15.1
docker tag mirrorgooglecontainers/pause:3.1 k8s.gcr.io/pause:3.1

删除原来的镜像

master服务器：

docker rmi mirrorgooglecontainers/kube-apiserver:v1.15.1
docker rmi mirrorgooglecontainers/kube-controller-manager:v1.15.1
docker rmi mirrorgooglecontainers/kube-scheduler:v1.15.1
docker rmi mirrorgooglecontainers/kube-proxy:v1.15.1
docker rmi mirrorgooglecontainers/pause:3.1
docker rmi mirrorgooglecontainers/etcd:3.3.10
docker rmi coredns/coredns:1.3.1

node服务器：

docker rmi mirrorgooglecontainers/kube-proxy:v1.15.1
docker rmi mirrorgooglecontainers/pause:3.1

2.master机器创建集群

修改master机器hostname为master

hostnamectl set-hostname master

创建集群

# --apiserver-advertise-address 本机ip
# --kubernetes-version 指定镜像版本
# --service-cidr 服务使用IP地址的替代范围
# --pod-network-cidr 指定Pod网络的IP地址范围。如果设置，控制平面将自动为每个节点分配CIDR
kubeadm init --apiserver-advertise-address 192.168.0.108 --kubernetes-version 1.15.1 --service-cidr 10.1.0.0/16 --pod-network-cidr 10.244.0.0/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

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/

Then you can join any number of worker nodes by running the following on each as root:

kubeadm join 192.168.0.108:6443 --token y9e8yj.a2olglq2lurpmow7 \
    --discovery-token-ca-cert-hash sha256:43e3035c08345a303afd696ed8a87d3b8a2ebd2c875d2fb30d2eeea47594447c

上述信息表示我们可以通过运行此行命令将node服务器加入集群，需要记录以免遗忘

kubeadm join 192.168.0.108:6443 --token y9e8yj.a2olglq2lurpmow7 \
    --discovery-token-ca-cert-hash sha256:43e3035c08345a303afd696ed8a87d3b8a2ebd2c875d2fb30d2eeea47594447c

根据kubeadm信息提示设置普通用户权限

.kube/config文件可以放在任意安装有kubectl的机器上，通过该文件可以使用kubectl远程控制集群

mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config

应用flannel网络

kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/a70459be0084506e4ec919aa1c114638878db11b/Documentation/kube-flannel.yml

若报错The connection to the server raw.githubusercontent.com was refused - did you specify the right host or port?则是网络导致的，改用手动添加解决

kubectl apply -f - <<EOF
---
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1beta1
metadata:
  name: flannel
rules:
  - apiGroups:
      - ""
    resources:
      - pods
    verbs:
      - get
  - apiGroups:
      - ""
    resources:
      - nodes
    verbs:
      - list
      - watch
  - apiGroups:
      - ""
    resources:
      - nodes/status
    verbs:
      - patch
---
kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1beta1
metadata:
  name: flannel
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: flannel
subjects:
- kind: ServiceAccount
  name: flannel
  namespace: kube-system
---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: flannel
  namespace: kube-system
---
kind: ConfigMap
apiVersion: v1
metadata:
  name: kube-flannel-cfg
  namespace: kube-system
  labels:
    tier: node
    app: flannel
data:
  cni-conf.json: |
    {
      "name": "cbr0",
      "plugins": [
        {
          "type": "flannel",
          "delegate": {
            "hairpinMode": true,
            "isDefaultGateway": true
          }
        },
        {
          "type": "portmap",
          "capabilities": {
            "portMappings": true
          }
        }
      ]
    }
  net-conf.json: |
    {
      "Network": "10.244.0.0/16",
      "Backend": {
        "Type": "vxlan"
      }
    }
---
apiVersion: extensions/v1beta1
kind: DaemonSet
metadata:
  name: kube-flannel-ds-amd64
  namespace: kube-system
  labels:
    tier: node
    app: flannel
spec:
  template:
    metadata:
      labels:
        tier: node
        app: flannel
    spec:
      hostNetwork: true
      nodeSelector:
        beta.kubernetes.io/arch: amd64
      tolerations:
      - operator: Exists
        effect: NoSchedule
      serviceAccountName: flannel
      initContainers:
      - name: install-cni
        image: quay.io/coreos/flannel:v0.11.0-amd64
        command:
        - cp
        args:
        - -f
        - /etc/kube-flannel/cni-conf.json
        - /etc/cni/net.d/10-flannel.conflist
        volumeMounts:
        - name: cni
          mountPath: /etc/cni/net.d
        - name: flannel-cfg
          mountPath: /etc/kube-flannel/
      containers:
      - name: kube-flannel
        image: quay.io/coreos/flannel:v0.11.0-amd64
        command:
        - /opt/bin/flanneld
        args:
        - --ip-masq
        - --kube-subnet-mgr
        resources:
          requests:
            cpu: "100m"
            memory: "50Mi"
          limits:
            cpu: "100m"
            memory: "50Mi"
        securityContext:
          privileged: true
        env:
        - name: POD_NAME
          valueFrom:
            fieldRef:
              fieldPath: metadata.name
        - name: POD_NAMESPACE
          valueFrom:
            fieldRef:
              fieldPath: metadata.namespace
        volumeMounts:
        - name: run
          mountPath: /run
        - name: flannel-cfg
          mountPath: /etc/kube-flannel/
      volumes:
        - name: run
          hostPath:
            path: /run
        - name: cni
          hostPath:
            path: /etc/cni/net.d
        - name: flannel-cfg
          configMap:
            name: kube-flannel-cfg
---
apiVersion: extensions/v1beta1
kind: DaemonSet
metadata:
  name: kube-flannel-ds-arm64
  namespace: kube-system
  labels:
    tier: node
    app: flannel
spec:
  template:
    metadata:
      labels:
        tier: node
        app: flannel
    spec:
      hostNetwork: true
      nodeSelector:
        beta.kubernetes.io/arch: arm64
      tolerations:
      - operator: Exists
        effect: NoSchedule
      serviceAccountName: flannel
      initContainers:
      - name: install-cni
        image: quay.io/coreos/flannel:v0.11.0-arm64
        command:
        - cp
        args:
        - -f
        - /etc/kube-flannel/cni-conf.json
        - /etc/cni/net.d/10-flannel.conflist
        volumeMounts:
        - name: cni
          mountPath: /etc/cni/net.d
        - name: flannel-cfg
          mountPath: /etc/kube-flannel/
      containers:
      - name: kube-flannel
        image: quay.io/coreos/flannel:v0.11.0-arm64
        command:
        - /opt/bin/flanneld
        args:
        - --ip-masq
        - --kube-subnet-mgr
        resources:
          requests:
            cpu: "100m"
            memory: "50Mi"
          limits:
            cpu: "100m"
            memory: "50Mi"
        securityContext:
          privileged: true
        env:
        - name: POD_NAME
          valueFrom:
            fieldRef:
              fieldPath: metadata.name
        - name: POD_NAMESPACE
          valueFrom:
            fieldRef:
              fieldPath: metadata.namespace
        volumeMounts:
        - name: run
          mountPath: /run
        - name: flannel-cfg
          mountPath: /etc/kube-flannel/
      volumes:
        - name: run
          hostPath:
            path: /run
        - name: cni
          hostPath:
            path: /etc/cni/net.d
        - name: flannel-cfg
          configMap:
            name: kube-flannel-cfg
---
apiVersion: extensions/v1beta1
kind: DaemonSet
metadata:
  name: kube-flannel-ds-arm
  namespace: kube-system
  labels:
    tier: node
    app: flannel
spec:
  template:
    metadata:
      labels:
        tier: node
        app: flannel
    spec:
      hostNetwork: true
      nodeSelector:
        beta.kubernetes.io/arch: arm
      tolerations:
      - operator: Exists
        effect: NoSchedule
      serviceAccountName: flannel
      initContainers:
      - name: install-cni
        image: quay.io/coreos/flannel:v0.11.0-arm
        command:
        - cp
        args:
        - -f
        - /etc/kube-flannel/cni-conf.json
        - /etc/cni/net.d/10-flannel.conflist
        volumeMounts:
        - name: cni
          mountPath: /etc/cni/net.d
        - name: flannel-cfg
          mountPath: /etc/kube-flannel/
      containers:
      - name: kube-flannel
        image: quay.io/coreos/flannel:v0.11.0-arm
        command:
        - /opt/bin/flanneld
        args:
        - --ip-masq
        - --kube-subnet-mgr
        resources:
          requests:
            cpu: "100m"
            memory: "50Mi"
          limits:
            cpu: "100m"
            memory: "50Mi"
        securityContext:
          privileged: true
        env:
        - name: POD_NAME
          valueFrom:
            fieldRef:
              fieldPath: metadata.name
        - name: POD_NAMESPACE
          valueFrom:
            fieldRef:
              fieldPath: metadata.namespace
        volumeMounts:
        - name: run
          mountPath: /run
        - name: flannel-cfg
          mountPath: /etc/kube-flannel/
      volumes:
        - name: run
          hostPath:
            path: /run
        - name: cni
          hostPath:
            path: /etc/cni/net.d
        - name: flannel-cfg
          configMap:
            name: kube-flannel-cfg
---
apiVersion: extensions/v1beta1
kind: DaemonSet
metadata:
  name: kube-flannel-ds-ppc64le
  namespace: kube-system
  labels:
    tier: node
    app: flannel
spec:
  template:
    metadata:
      labels:
        tier: node
        app: flannel
    spec:
      hostNetwork: true
      nodeSelector:
        beta.kubernetes.io/arch: ppc64le
      tolerations:
      - operator: Exists
        effect: NoSchedule
      serviceAccountName: flannel
      initContainers:
      - name: install-cni
        image: quay.io/coreos/flannel:v0.11.0-ppc64le
        command:
        - cp
        args:
        - -f
        - /etc/kube-flannel/cni-conf.json
        - /etc/cni/net.d/10-flannel.conflist
        volumeMounts:
        - name: cni
          mountPath: /etc/cni/net.d
        - name: flannel-cfg
          mountPath: /etc/kube-flannel/
      containers:
      - name: kube-flannel
        image: quay.io/coreos/flannel:v0.11.0-ppc64le
        command:
        - /opt/bin/flanneld
        args:
        - --ip-masq
        - --kube-subnet-mgr
        resources:
          requests:
            cpu: "100m"
            memory: "50Mi"
          limits:
            cpu: "100m"
            memory: "50Mi"
        securityContext:
          privileged: true
        env:
        - name: POD_NAME
          valueFrom:
            fieldRef:
              fieldPath: metadata.name
        - name: POD_NAMESPACE
          valueFrom:
            fieldRef:
              fieldPath: metadata.namespace
        volumeMounts:
        - name: run
          mountPath: /run
        - name: flannel-cfg
          mountPath: /etc/kube-flannel/
      volumes:
        - name: run
          hostPath:
            path: /run
        - name: cni
          hostPath:
            path: /etc/cni/net.d
        - name: flannel-cfg
          configMap:
            name: kube-flannel-cfg
---
apiVersion: extensions/v1beta1
kind: DaemonSet
metadata:
  name: kube-flannel-ds-s390x
  namespace: kube-system
  labels:
    tier: node
    app: flannel
spec:
  template:
    metadata:
      labels:
        tier: node
        app: flannel
    spec:
      hostNetwork: true
      nodeSelector:
        beta.kubernetes.io/arch: s390x
      tolerations:
      - operator: Exists
        effect: NoSchedule
      serviceAccountName: flannel
      initContainers:
      - name: install-cni
        image: quay.io/coreos/flannel:v0.11.0-s390x
        command:
        - cp
        args:
        - -f
        - /etc/kube-flannel/cni-conf.json
        - /etc/cni/net.d/10-flannel.conflist
        volumeMounts:
        - name: cni
          mountPath: /etc/cni/net.d
        - name: flannel-cfg
          mountPath: /etc/kube-flannel/
      containers:
      - name: kube-flannel
        image: quay.io/coreos/flannel:v0.11.0-s390x
        command:
        - /opt/bin/flanneld
        args:
        - --ip-masq
        - --kube-subnet-mgr
        resources:
          requests:
            cpu: "100m"
            memory: "50Mi"
          limits:
            cpu: "100m"
            memory: "50Mi"
        securityContext:
          privileged: true
        env:
        - name: POD_NAME
          valueFrom:
            fieldRef:
              fieldPath: metadata.name
        - name: POD_NAMESPACE
          valueFrom:
            fieldRef:
              fieldPath: metadata.namespace
        volumeMounts:
        - name: run
          mountPath: /run
        - name: flannel-cfg
          mountPath: /etc/kube-flannel/
      volumes:
        - name: run
          hostPath:
            path: /run
        - name: cni
          hostPath:
            path: /etc/cni/net.d
        - name: flannel-cfg
          configMap:
            name: kube-flannel-cfg
EOF

查看节点信息

kubectl get nodes

出现如下信息

NAME     STATUS     ROLES    AGE   VERSION
master   Ready      master   35ms   v1.15.1

若出现节点依旧是NotReady则参阅文章:工作节点NotReady处理

node节点加入集群

node服务器分别更改名称为node1、node2

# node1服务器
hostnamectl set-hostname node1

# node2服务器
hostnamectl set-hostname node2

运行kubeadm join命令加入集群

# node1服务器
kubeadm join 192.168.0.108:6443 --token y9e8yj.a2olglq2lurpmow7 \
    --discovery-token-ca-cert-hash sha256:43e3035c08345a303afd696ed8a87d3b8a2ebd2c875d2fb30d2eeea47594447c

# node2服务器
kubeadm join 192.168.0.108:6443 --token y9e8yj.a2olglq2lurpmow7 \
    --discovery-token-ca-cert-hash sha256:43e3035c08345a303afd696ed8a87d3b8a2ebd2c875d2fb30d2eeea47594447c

若出现如下报错

error execution phase preflight: unable to fetch the kubeadm-config ConfigMap: failed to get config map: Unauthorized

说明距离master生成的join命令已经超过24小时，token已经过期需要重新生成。

运行以下命令生成新的token

kubeadm token create

将生成的token值替换join命令中的token值再次运行join命令

然后回到master服务器，查看节点信息

kubectl get nodes

出现如下信息

NAME     STATUS     ROLES    AGE   VERSION
master   Ready      master   5m    v1.15.1
node1    Ready      <none>   42ms  v1.15.1
node2    Ready      <none>   22ms  v1.15.1

至此，k8s部署完毕

附加

由于构建集群的服务器时间可能存在一些误差，在一些验证token的服务里可能会出现因误差所导致的异常，建议构建集群的同时将集群内部所有服务器的时间同步。

服务器时间同步可以查看另一篇文章《centos服务器同步时间》

若需要针对gpu节点机进行配置，参考文章docker19.03以上版本k8s配置GPU支持

内容总结

以上是互联网集市为您收集整理的centos7 使用kubeadm部署k8s全部内容，希望文章能够帮你解决centos7 使用kubeadm部署k8s所遇到的程序开发问题。如果觉得互联网集市技术教程内容还不错，欢迎将互联网集市网站推荐给程序员好友。

内容备注

版权声明：本文内容由互联网用户自发贡献，该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容，请发送邮件至 gblab@vip.qq.com 举报，一经查实，本站将立刻删除。

内容手机端

扫描二维码推送至手机访问。

本文链接：https://qyyshop.com/info/931932.html

来源：【匿名】

【上一篇】如何快速在Ubuntu18.04.1上安装k8s1.20的简明教程【下一篇】关于k8s部署php镜像实例

更多 ►

【centos7 使用kubeadm部署k8s】教程文章相关的互联网学习教程文章

k8s v1.18.2 centos7 下环境搭建【代码】

准备服务器：3台机器——1台主、2台工作节点，可以使用virtualbox 搭建虚拟机主机名centos versionipdocker versionflannel version主机配置备注master017.7.1908192.168.56.10119.03.8v0.12.0-amd642P 2G 20Gnode017.7.1908192.168.56.10219.03.8v0.12.0-amd642P 2G 20Gnode027.7.1908192.168.56.10319.03.8v0.12.0-amd642P 2G 20Gk8s版本主机名kubelet versionkubeadm versionkubectl version备注master01v1.18.2v1.18.2v1.18.2n...

Centos7搭建k8s集群【代码】【图】

一、部署环境操作系统：CentOS Linux release 7.6.1810 (Core)安装软件：docker：18.06.3-cekubernetes：v1.15.4二、部署架构：部署开始前，先把主机名改成如上图所示。同时修改/etc/hosts，如下：三、部署过程1、安装docker（所有节点）1.1、卸载可能存在的依赖包sudoyum remove docker docker-common container-selinux docker-selinux docker-engine1.2、安装 yum-utils，它提供了 yum-config-manager，可用来管理yum源sudoy...

centos7 k8s集群部署

安装k8s集群前期准备：网络环境：节点主机名 ipMaster k8s_master 192.168.3.216Node1 k8s_node1 192.168.3.217Node2 k8s_node2 192.168.3.219 centos7版本：[root@k8s_master ~]# cat /etc/redhat-releaseCentOS Linux release 7.4.1708 (Core) 关闭firewalld:systemctl stop firewalldsystemctl disable firewalld三台主机基础服务安装：[root@k8s_...

K8S简介+CentOS7 部署K8S集群【代码】【图】

一、前言Kubernetes（简称K8S）是开源的容器集群管理系统，可以实现容器集群的自动化部署、自动扩缩容、维护等功能。它既是一款容器编排工具，也是全新的基于容器技术的分布式架构领先方案。在Docker技术的基础上，为容器化的应用提供部署运行、资源调度、服务发现和动态伸缩等功能，提高了大规模容器集群管理的便捷性。【Kubernetes是容器集群管理工具】二、Kubernetes的架构图三、重要概念 3.1、clustercluster是计算、存储和...

K8S安装部署在centos7下

所有节点操作K8S的安装部署可以参考文档:http://m.bubuko.com/infodetail-3144195.html 需要在每一台机器上执行的操作l 各节点禁用防火墙# systemctl stop firewalld# systemctl disable firewalldl 禁用SELINUX：# setenforce 0# sed -i ‘s/SELINUX=enforcing/SELINUX=disabled/g‘ /etc/selinux/config# SELINUX=disabledl 创建/etc/sysctl.d/k8s.conf文件，添加如下内容：net.bridge.bridge-nf-call-ip6tables = 1net.bridge.b...

从安装linux(centos7.6)系统到部署springboot java程序到k8s（大纲）

本文说明从安装linux系统开始，一直到在k8s运行springboot程序全过程本文假设在自己电脑操作，因此linux系统使用vmware虚拟机，linux发行版使用centos 7.6.1810（CentOS-7-x86_64-DVD-1810.iso） Linux安装：首先要先装一个centos的虚拟机（https://www.cnblogs.com/cannel/p/11104088.html），或者找有关人士获取 PS：由于k8s需要集群，集群主节点称为master，可一个或多个（一般一个够了），子节点称为node（一般多个），本...

在Centos7.6使用kubeadm部署k8s 1.14.3【图】

K8s不是一个软件，而是一堆软件的集合，由于这堆软件各自独立，因此可能k8s安装过程很容易出现问题 K8s部署有多种方式，本文使用kubeadm部署，从易操作性和可控性来说属于中等的方式环境：centos7.6，k8s 1.14.3 K8s安装前设置以下操作在所有节点操作（也就是master1和node1）关闭防火墙、selinux和swap，分别运行： systemctl stop firewalld systemctl disable firewalld setenforce 0 sed -i "s/^SELINUX=enforcing/S...

Centos7 Kubernetes(K8s) k8s 开发单服务器部署 rocketmq【代码】【图】

这几天对开发服务器中的 k8s和相关模块进行升级，做个记录环境，与系统系统：centos 7.6 内核： 5.1.9-1.el7.elrepo.x86_64 Kubernetes(K8s) 1.14.3 服务器IP：192.168.0.254 服务器IP 说明如果更改了服务器IP 为其他IP，那么请全局全部替换成你改的IP fox.风如何安装 k8s 请看最近写的一篇文章， https://blog.csdn.net/fenglailea/article/details/88745642 常用 k8s 命令 https://foxwho.blog.csdn.net/article/details/9...

CentOS7.5 Qihoo360/wayne部署（web管理K8S集群）【代码】

# 安装依赖包 yum install -y yum-utils device-mapper-persistent-data lvm2# 添加Docker软件包源 yum-config-manager --add-repo https://download.docker.com/linux/centos/docker-ce.repo# 更新yum包索引 yum makecache fast# 安装Docker CE yum install docker-ce # 启动systemctl start docker systemctl enable docker# 卸载 yum remove docker-ce rm -rf /var/lib/docker

centos7 安装k8s kubectl 客户端【代码】

1、配置k8s的kubelet 管理客户端1 cat <<EOF > /etc/yum.repos.d/kubernetes.repo 2 [kubernetes] 3 name=Kubernetes 4 baseurl=https://mirrors.aliyun.com/kubernetes/yum/repos/kubernetes-el7-x86_64 5 enabled=1 6 gpgcheck=1 7 repo_gpgcheck=1 8 gpgkey=https://mirrors.aliyun.com/kubernetes/yum/doc/yum-key.gpg https://mirrors.aliyun.com/kubernetes/yum/doc/rpm-package-key.gpg 9 EOF2、安装k8s kubectl 客户端[ro...

CentOS7使用KubeSpray搭建单节点K8S集群【代码】

主机预部署依据《CentOS7实验机模板搭建部署》克隆实验机kubespray 192.168.77.10# 主机名和hosts解析 HOSTNAME=kubespray hostnamectl set-hostname "$HOSTNAME" echo "$HOSTNAME">/etc/hostname echo "$(grep -E '127|::1' /etc/hosts)">/etc/hosts echo "$(ip a|grep "inet "|grep -v 127|awk -F'[ /]' '{print $6}') $HOSTNAME">>/etc/hosts# 关闭swap swapoff -a sed -i 's/^.*swap.*$/###&/g' /etc/fstab# 添加br_netfilter模...

项目环境搭建【Docker+k8s】二 || centos7服务器通用设置【代码】

1、设置静态ip和DNS ??该教程使用虚拟机进行安装，安装前设置虚拟机静态ip和DNS。教程：虚拟机安装centos7教程 2、关闭防火墙 systemctl stop firewalld && systemctl disable firewalld 3、设置主机名 #hostname主机名自定义 hostnamectl set-hostname <hostname> 4、关闭selinux查看selinux状态。enforceing代表开启，permissive代表警告，disabled代表关闭getenforce临时关闭selinuxsetenforce 0开启selinuxsetenforce 1永久关闭...

K8S简介+CentOS7 部署K8S集群【代码】【图】

centos7系统搭建k8s(minikube)【图】

1. 官网安装教程（选择RPM package）下载rpm安装包: curl -LO https://storage.googleapis.com/minikube/releases/latest/minikube-latest.aarch64.rpm 安装: sudo rpm -ivh minikube-latest.aarch64.rpm 新增启动账号(minikube不能通过root账号启动，minikube相关操作都用这个新增的用户): useradd -g docker -G wheel john -g:默认组(用户登录时就是这个组) -G: 其他群组 wheel:sudo组(加到这个组里才会有sudo权限) 为新用户...