京东云centos 7.6 安装单机k8s

最新推荐文章于 2025-11-05 16:49:32 发布

原创最新推荐文章于 2025-11-05 16:49:32 发布 · 908 阅读

15 ·

CC 4.0 BY-SA版权

文章标签：

#京东云 #centos #kubernetes

使用京东云轻量云主机安装cube

一先安装docker

建议先把原有的源都去掉，

curl -o /etc/yum.repos.d/CentOS-Base.repo http://mirrors.aliyun.com/repo/Centos-7.repo

安装常用工具

yum install wget net-tools ntp git -y

wget https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo -O /etc/yum.repos.d/docker-ce.repo

更新yum源

yum clean all
yum makecache

查看是否支持docker安装

yum list docker-ce
yum list docker-ce --showduplicates | sort -r

下载doker

yum install -y \
docker-ce-19.03.15 \
docker-ce-cli-19.03.15 \
containerd.io-1.2.13

二安装cube

配置时间同步

ntpdate 0.asia.pool.ntp.org

配置K8s的源

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=1
repo_gpgcheck=1
gpgkey=https://mirrors.aliyun.com/kubernetes/yum/doc/yum-key.gpg https://mirrors.aliyun.com/kubernetes/yum/doc/rpm-package-key.gpg
EOF

yum repolist 是管理 yum 仓库的基础命令

确保 br_netfilter 模块被加载。

通过运行 lsmod | grep br_netfilter 来确认br_netfilter已经加载。若要加载该模块，可执行 sudo

modprobe br_netfilter。

为了让你的 Linux 节点上的 iptables 能够正确地查看桥接流量，你需要确保在你的 sysctl 配置中将net.bridge.bridge-nf-call-iptables 设置为 1

# 创建或编辑sysctl配置文件（如/etc/sysctl.d/k8s.conf）
cat > /etc/sysctl.d/k8s.conf << EOF
net.bridge.bridge-nf-call-iptables = 1
net.bridge.bridge-nf-call-ip6tables = 1
net.ipv4.ip_forward = 1 # 开启IP转发（K8s网络必需）
EOF

# 生效配置
sysctl -p /etc/sysctl.d/k8s.conf

关闭防火墙

systemctl stop firewalld

systemctl disable firewalld

关闭 SeLinux

setenforce 0

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

关闭 swap

swapoff -a

yes | cp /etc/fstab /etc/fstab_bak

vi /etc/fstab #注释下面这一行

#/dev/mapper/centos-swap swap swap defaults 0 0

验证swap

[root@lavm-slcqlotfru yum.repos.d]# free -mg
total used free shared buff/cache available
Mem: 1 0 0 0 1 1
Swap: 0 0 0

修改docker的源

mkdir /etc/docker

cat > /etc/docker/daemon.json <<EOF
{
"exec-opts": ["native.cgroupdriver=systemd"],
"registry-mirrors": ["https://registry.cn-hangzhou.aliyuncs.com"]
}
EOF

# Restart Docker
systemctl daemon-reload
systemctl restart docker
systemctl enable docker

安装kubelet、kubeadm、kubectl

yum install -y kubelet-1.19.3 kubeadm-1.19.3 kubectl-1.19.3

systemctl enable kubelet

从次可以备份镜像

三初始化Master节点

设置主机名，管理节点设置主机名为master

hostnamectl set-hostname master

初始化主节点

kubeadm init --kubernetes-version=1.19.2 \
--apiserver-advertise-address=172.16.0.7 \
--image-repository registry.aliyuncs.com/google_containers \
--service-cidr=10.1.0.0/16 \
--pod-network-cidr=10.244.0.0/16

其中172.16.0.7 是本机ip

返回success就说明输出化成功

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 172.16.0.7:6443 --token n949k0.zirikbqcvsl3ttt4 \
--discovery-token-ca-cert-hash sha256:e2e5eb53ad1xxxxxe93097fa80021ed0d45ae8bd

执行返回的三条命了

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

配置KUBECONFIG 环境变量

echo "export KUBECONFIG=/etc/kubernetes/admin.conf" >> ~/.bash_profile

难点：安装网络插件 Flannel（只需要在 Master 安装 flannel）

方式一需要有外网权限，连接到docker hub

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

查看启动

kubectl get po -n kube-system

下载文件
wget https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml -O kube-flannel.yml

# 原配置（第 1 处：install-cni-plugin 镜像）
# image: ghcr.io/flannel-io/flannel-cni-plugin:v1.7.1-flannel1
# 修改为国内镜像（阿里云）
image: registry.cn-hangzhou.aliyuncs.com/flannel/flannel-cni-plugin:v1.7.1-flannel1

# 原配置（第 2 处：install-cni 镜像）
# image: ghcr.io/flannel-io/flannel:v0.27.2
# 修改为国内镜像（阿里云）
image: registry.cn-hangzhou.aliyuncs.com/flannel/flannel:v0.27.2

# 原配置（第 3 处：kube-flannel 主镜像）
# image: ghcr.io/flannel-io/flannel:v0.27.2
# 修改为国内镜像（阿里云）
image: registry.cn-hangzhou.aliyuncs.com/flannel/flannel:v0.27.2

# 先删除之前的 Flannel 部署（确保清理残留资源）
kubectl delete -f kube-flannel.yml

# 应用修改后的配置
kubectl apply -f kube-flannel.yml

方法二不需要外网权限，从网上找到的flannel.yaml文件

[root@master ~]# cat flannel.yaml
---
apiVersion: policy/v1beta1
kind: PodSecurityPolicy
metadata:
  name: psp.flannel.unprivileged
  annotations:
    seccomp.security.alpha.kubernetes.io/allowedProfileNames: docker/default
    seccomp.security.alpha.kubernetes.io/defaultProfileName: docker/default
    apparmor.security.beta.kubernetes.io/allowedProfileNames: runtime/default
    apparmor.security.beta.kubernetes.io/defaultProfileName: runtime/default
spec:
  privileged: false
  volumes:
  - configMap
  - secret
  - emptyDir
  - hostPath
  allowedHostPaths:
  - pathPrefix: "/etc/cni/net.d"
  - pathPrefix: "/etc/kube-flannel"
  - pathPrefix: "/run/flannel"
  readOnlyRootFilesystem: false
  # Users and groups
  runAsUser:
    rule: RunAsAny
  supplementalGroups:
    rule: RunAsAny
  fsGroup:
    rule: RunAsAny
  # Privilege Escalation
  allowPrivilegeEscalation: false
  defaultAllowPrivilegeEscalation: false
  # Capabilities
  allowedCapabilities: ['NET_ADMIN', 'NET_RAW']
  defaultAddCapabilities: []
  requiredDropCapabilities: []
  # Host namespaces
  hostPID: false
  hostIPC: false
  hostNetwork: true
  hostPorts:
  - min: 0
    max: 65535
  # SELinux
  seLinux:
    # SELinux is unused in CaaSP
    rule: 'RunAsAny'
---
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: flannel
rules:
- apiGroups: ['extensions']
  resources: ['podsecuritypolicies']
  verbs: ['use']
  resourceNames: ['psp.flannel.unprivileged']
- apiGroups:
  - ""
  resources:
  - pods
  verbs:
  - get
- apiGroups:
  - ""
  resources:
  - nodes
  verbs:
  - list
  - watch
- apiGroups:
  - ""
  resources:
  - nodes/status
  verbs:
  - patch
---
kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1
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",
      "cniVersion": "0.3.1",
      "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: apps/v1
kind: DaemonSet
metadata:
  name: kube-flannel-ds
  namespace: kube-system
  labels:
    tier: node
    app: flannel
spec:
  selector:
    matchLabels:
      app: flannel
  template:
    metadata:
      labels:
        tier: node
        app: flannel
    spec:
      affinity:
        nodeAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
            nodeSelectorTerms:
            - matchExpressions:
              - key: kubernetes.io/os
                operator: In
                values:
                - linux
      hostNetwork: true
      priorityClassName: system-node-critical
      tolerations:
      - operator: Exists
        effect: NoSchedule
      serviceAccountName: flannel
      initContainers:
      - name: install-cni
        image: registry.cn-beijing.aliyuncs.com/qingfeng666/flannel:v0.13.0
        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: registry.cn-beijing.aliyuncs.com/qingfeng666/flannel:v0.13.0
        command:
        - /opt/bin/flanneld
        args:
        - --ip-masq
        - --kube-subnet-mgr
        resources:
          requests:
            cpu: "100m"
            memory: "50Mi"
          limits:
            cpu: "100m"
            memory: "50Mi"
        securityContext:
          privileged: false
          capabilities:
            add: ["NET_ADMIN", "NET_RAW"]
        env:
        - name: POD_NAME
          valueFrom:
            fieldRef:
              fieldPath: metadata.name
        - name: POD_NAMESPACE
          valueFrom:
            fieldRef:
              fieldPath: metadata.namespace
        volumeMounts:
        - name: run
          mountPath: /run/flannel
        - name: flannel-cfg
          mountPath: /etc/kube-flannel/
      volumes:
      - name: run
        hostPath:
          path: /run/flannel
      - name: cni
        hostPath:
          path: /etc/cni/net.d
      - name: flannel-cfg
        configMap:
          name: kube-flannel-cfg

重新加载

kubectl delete -f kube-flannel.yml
kubectl delete -f flannel.yml
kubectl apply -f flannel.yaml

验证是否成功

Ready状态就行

[root@master ~]# kubectl get node
NAME STATUS ROLES AGE VERSION
master Ready master 5h12m v1.19.3

有flannel，都是running

[root@master ~]# kubectl get pods -n kube-system
NAME READY STATUS RESTARTS AGE
coredns-6d56c8448f-58d2t 1/1 Running 0 5h12m
coredns-6d56c8448f-b2w2q 1/1 Running 0 5h12m
etcd-master 1/1 Running 0 5h12m
kube-apiserver-master 1/1 Running 0 5h12m
kube-controller-manager-master 1/1 Running 0 5h12m
kube-flannel-ds-knchm 1/1 Running 0 3h34m
kube-proxy-tg9fj 1/1 Running 0 5h12m
kube-scheduler-master 1/1 Running 0 5h12m