Kubernetes失败数次最后一次成功的k8s安装部署文档

最新推荐文章于 2023-04-29 11:48:25 发布
最新推荐文章于 2023-04-29 11:48:25 发布
阅读量3.2w 收藏
点赞数
分类专栏： 运维 文章标签： docker centos 运维 kubernetes kubeadm
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/xiaoku13141/article/details/111540536
版权

交流探索圣地: 巨微科技 点击链接加入群聊【8080实验室】：https://jq.qq.com/?_wv=1027&k=75ePDb3o

一、我的环境

  • 操作系统: windows 10
  • 虚拟机: VMware 16 Pro
  • Linux: CentOS 8.3
  • 内核: 4.18.0-240.el8.x86_64 (uname -r)
  • Master: 172.20.54.226
  • Docker: 19.03.5-3.el7
  • Kubeadm: v1.20.1
  • Kubectl: v1.20.1
  • Kubelet: v1.20.1
  • KubernetesDashboard: v2.0.0

二、环境准备

正式环境需要至少4-5台服务器方能实现有效集群, 此处用于学习, 只是搭建了个伪集群: Master、Node两个节点

  1. 各节点分别执行相应命令

    hostnamectl set-hostname master

    hostnamectl set-hostname node

  2. 所有节点执行地址映射命令

    cat <<EOF > /etc/hosts 
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4 
::1        localhost localhost.localdomain localhost6 localhost6.localdomain6 
172.20.54.226 master
172.20.54.108 node
EOF

  3. 所有节点关闭防火墙

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

systemctl disable firewalld  
systemctl stop firewalld

swapoff -a
sed -i 's/.*swap.*/#&/' /etc/fstab

  4. 所有节点加载模块

    modprobe br_netfilter
sh -c 'echo "br_netfilter" > /etc/modules-load.d/br_netfilter.conf'

  5. 所有节点配置内核参数

    执行以下命令后, 使用: ulimit -Hn 验证结果为655360, 否则重新连接客户端

    cat > /etc/sysctl.d/k8s.conf <<EOF 
net.bridge.bridge-nf-call-ip6tables = 1 
net.bridge.bridge-nf-call-iptables = 1 
EOF
sysctl -p /etc/sysctl.d/k8s.conf
echo "* soft nofile 655360" >> /etc/security/limits.conf
echo "* hard nofile 655360" >> /etc/security/limits.conf
echo "* soft nproc 655360"  >> /etc/security/limits.conf
echo "* hard nproc 655360"  >> /etc/security/limits.conf
echo "* soft  memlock  unlimited"  >> /etc/security/limits.conf
echo "* hard memlock  unlimited"  >> /etc/security/limits.conf
echo "DefaultLimitNOFILE=1024000"  >> /etc/systemd/system.conf
echo "DefaultLimitNPROC=1024000"  >> /etc/systemd/system.conf

  6. 所有节点配置国内镜像源

    rm -rf  /etc/yum.repos.d/*
wget -O /etc/yum.repos.d/CentOS-Base.repo http://mirrors.aliyun.com/repo/Centos-8.repo
wget -O /etc/yum.repos.d/epel.repo  http://mirrors.aliyun.com/repo/epel-7.repo

    cat <<EOF> /etc/yum.repos.d/kubernetes.repo 
[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 clean all && yum makecache

  7. 所有节点安装依赖

    yum install  -y conntrack ipvsadm ipset jq sysstat curl iptables libseccomp bash-completion yum-utils device-mapper-persistent-data lvm2 net-tools conntrack-tools vim libtool-ltdl

  8. 同步各节点时间

    yum -y install chrony
systemctl enable chronyd.service && systemctl start chronyd.service && systemctl status chronyd.service
chronyc sources

  9. 配置节点互信 (至少master)

    ssh-keygen # 全部回车
ssh-copy-id  node # 输入node节点密码

三、部署Docker

  1. 所有节点删除旧版本

    yum remove -y docker docker-ce docker-common docker-selinux docker-engine

  2. 所有节点设置Docker国内镜像源

    yum-config-manager --add-repo http://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo

  3. 所有节点安装新版容器

    dnf install --allowerasing http://mirrors.aliyun.com/docker-ce/linux/centos/8/x86_64/stable/Packages/containerd.io-1.4.3-3.1.el8.x86_64.rpm

  4. 所有节点安装指定版本Docker

    yum install -y docker-ce-19.03.5-3.el7.x86_64

  5. 所有节点配置加速器和存放路径

    mkdir -p /etc/docker/
vim /etc/docker/daemon.json
{  
  "exec-opts": ["native.cgroupdriver=systemd"],
  "registry-mirrors": ["https://q2hy3fzi.mirror.aliyuncs.com"], 
  "graph": "/tol/docker-data" 
}
systemctl restart docker

  6. 所有节点启动Docker

    systemctl daemon-reload && systemctl restart docker && systemctl enable docker && systemctl status docker

  7. 所有节点安装并启动k8s部署工具

    yum install -y kubelet kubeadm kubectl --disableexcludes=kubernetes
systemctl enable kubelet && systemctl start kubelet

四、部署Kubeadm

  1. 所有节点生成部署工具默认配置

    kubeadm config print init-defaults > kubeadm.conf
sed -i "s/imageRepository: .*/imageRepository: registry.aliyuncs.com\/google_containers/g" kubeadm.conf

  2. 所有节点安装指定版本Kubernetes

    sed -i "s/kubernetesVersion: .*/kubernetesVersion: v1.20.0/g" kubeadm.conf
kubeadm config images pull --config kubeadm.conf

  3. 所有节点防屏蔽

    如果不打tag变成k8s.gcr.io，那么后面用kubeadm安装会出现问题:

    因为 kubeadm里面只认 google自身的模式, 我们执行下面命令即可完成tag标识更换

    vim tag.sh

    #!/bin/bash

newtag=k8s.gcr.io
for i in $(docker images | grep -v TAG |awk '{print $1 ":" $2}')
do
   image=$(echo $i | awk -F '/' '{print $3}')
   docker tag $i $newtag/$image
   docker rmi $i
done

    bash tag.sh

五、部署Master

  1. 使用部署工具初始化Master节点

    记得将172.20.54.226改成自己Master的IP

    kubeadm init --kubernetes-version=v1.20.0 --pod-network-cidr=172.22.0.0/16 --apiserver-advertise-address=172.20.54.226

  2. 测试验证

    mkdir -p /root/.kube
cp /etc/kubernetes/admin.conf /root/.kube/config

    获取pods列表命令: 其中coredns pod还处于Pending状态 (此处贴的是最终效果)

    # kubectl get pods --all-namespaces
NAMESPACE     NAME                                         READY   STATUS    RESTARTS   AGE
kube-system   calico-kube-controllers-7854b85cf7-5fnv8     1/1     Running   1          4h
kube-system   calico-node-tk4xs                            1/1     Running   1          4h
kube-system   calico-node-tpwtk                            1/1     Running   4          4h
kube-system   coredns-74ff55c5b-9pvr6                      1/1     Running   1          5h25m
kube-system   coredns-74ff55c5b-kfvsb                      1/1     Running   1          5h25m
kube-system   dashboard-metrics-scraper-5587f78f94-88b8h   1/1     Running   0          57m
kube-system   etcd-master                                  1/1     Running   6          5h25m
kube-system   kube-apiserver-master                        1/1     Running   7          5h25m
kube-system   kube-controller-manager-master               1/1     Running   7          4h46m
kube-system   kube-proxy-hvq8c                             1/1     Running   1          4h48m
kube-system   kube-proxy-xmltp                             1/1     Running   4          5h25m
kube-system   kube-scheduler-master                        1/1     Running   8          4h45m
kube-system   kubernetes-dashboard-68486945bd-k4rp8        1/1     Running   0          58m

  3. 查看集群状态

    # kubectl get cs
etcd-0               Healthy   {"health":"true"}   
controller-manager   Healthy   ok                  
scheduler            Healthy   ok

六、部署Node

  1. 下载安装镜像

    docker pull registry.aliyuncs.com/google_containers/kube-proxy:v1.13.0
docker pull registry.aliyuncs.com/google_containers/pause:3.1
docker pull calico/node:v3.1.4
docker pull calico/cni:v3.1.4
docker pull calico/typha:v3.1.4

docker tag registry.aliyuncs.com/google_containers/kube-proxy:v1.13.0 k8s.gcr.io/kubeproxy:v1.13.0
docker tag registry.aliyuncs.com/google_containers/pause:3.1 k8s.gcr.io/pause:3.1
docker tag calico/node:v3.1.4 quay.io/calico/node:v3.1.4
docker tag calico/cni:v3.1.4 quay.io/calico/cni:v3.1.4
docker tag calico/typha:v3.1.4 quay.io/calico/typha:v3.1.4

docker rmi registry.aliyuncs.com/google_containers/kube-proxy:v1.13.0
docker rmi registry.aliyuncs.com/google_containers/pause:3.1
docker rmi calico/node:v3.1.4
docker rmi calico/cni:v3.1.4
docker rmi calico/typha:v3.1.4

  2. 在Master节点上获取加入集群的命令

    符号``内的命令即可在所有Node节点执行(下一步)

    # kubeadm token create --print-join-command
`kubeadm join 172.20.54.226:6443 --token 16l83a.e1tpcgkmze0i3fuy --discovery-token-ca-cert-hash sha256:233a3d9c6c0ed466642c08293e0bf2bb217359d414d3ccb0bf25afa1c00b7ca3`

  3. 在Node节点上执行获取到的: 加入集群命令

    # kubeadm join 172.20.54.226:6443 --token 16l83a.e1tpcgkmze0i3fuy --discovery-token-ca-cert-hash sha256:233a3d9c6c0ed466642c08293e0bf2bb217359d414d3ccb0bf25afa1c00b7ca3

七、部署Calico

该项操作只需要在Master节点上操作

  1. 下载安装标识calico镜像

    docker pull calico/node:v3.1.4
docker pull calico/cni:v3.1.4
docker pull calico/typha:v3.1.4
docker tag calico/node:v3.1.4 quay.io/calico/node:v3.1.4
docker tag calico/cni:v3.1.4 quay.io/calico/cni:v3.1.4
docker tag calico/typha:v3.1.4 quay.io/calico/typha:v3.1.4
docker rmi calico/node:v3.1.4
docker rmi calico/cni:v3.1.4
docker rmi calico/typha:v3.1.4

  2. 安装权限配置

    curl https://docs.projectcalico.org/v3.1/getting-started/kubernetes/installation/hosted/rbac-kdd.yaml -O
kubectl apply -f rbac-kdd.yaml

  3. 修改calico配置

    curl https://docs.projectcalico.org/v3.1/getting-started/kubernetes/installation/hosted/kubernetes-datastore/policy-only/1.7/calico.yaml -O

    修改typha_service_name: calico-typha

    kind: ConfigMap
apiVersion: v1
metadata:
  name: calico-config
  namespace: kube-system
data:
  typha_service_name: "calico-typha" # 原none

    修改apiVersion: apps/v1、 replicas: 1等

    apiVersion: apps/v1
kind: Deployment
metadata:
  name: calico-typha
  namespace: kube-system
  labels:
    k8s-app: calico-typha
spec:
  replicas: 1
  revisionHistoryLimit: 2

    - name: CALICO_IPV4POOL_CIDR
  value: "172.22.0.0/16"

    - name: CALICO_NETWORKING_BACKEND
  value: "bird"

  4. 部署calico网络

    # kubectl apply -f calico.yaml
# kubectl get pods --all-namespaces
# kubectl get nodes
NAME     STATUS   ROLES                  AGE     VERSION
master   Ready    control-plane,master   5h43m   v1.20.1
node     Ready    <none>                 5h5m    v1.20.1

八、部署Dashboard

  1. 下载镜像

    docker pull kubernetesui/dashboard:v2.0.0
docker pull kubernetesui/metrics-scraper:v1.0.4

  2. 部署权限服务

    vim dashboard-rbac.yaml

    apiVersion: v1
kind: ServiceAccount
metadata:
  labels:
    k8s-app: kubernetes-dashboard
  name: kubernetes-dashboard
  namespace: kube-system
---
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
  labels:
    k8s-app: kubernetes-dashboard
  name: kubernetes-dashboard
  namespace: kube-system
rules:
  - apiGroups: [""]
    resources: ["secrets"]
    resourceNames: ["kubernetes-dashboard-key-holder", "kubernetes-dashboard-certs", "kubernetes-dashboard-csrf"]
    verbs: ["get", "update", "delete"]
  - apiGroups: [""]
    resources: ["configmaps"]
    resourceNames: ["kubernetes-dashboard-settings"]
    verbs: ["get", "update"]
  - apiGroups: [""]
    resources: ["services"]
    resourceNames: ["heapster", "dashboard-metrics-scraper"]
    verbs: ["proxy"]
  - apiGroups: [""]
    resources: ["services/proxy"]
    resourceNames: ["heapster", "http:heapster:", "https:heapster:", "dashboard-metrics-scraper", "http:dashboard-metrics-scraper"]
    verbs: ["get"]
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  labels:
    k8s-app: kubernetes-dashboard
  name: kubernetes-dashboard
rules:
  - apiGroups: ["metrics.k8s.io"]
    resources: ["pods", "nodes"]
    verbs: ["get", "list", "watch"]
---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  labels:
    k8s-app: kubernetes-dashboard
  name: kubernetes-dashboard
  namespace: kube-system
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: Role
  name: kubernetes-dashboard
subjects:
  - kind: ServiceAccount
    name: kubernetes-dashboard
    namespace: kube-system
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: kubernetes-dashboard
  namespace: kube-system
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: kubernetes-dashboard
subjects:
  - kind: ServiceAccount
    name: kubernetes-dashboard
    namespace: kube-system

    # kubectl apply -f dashboard-rbac.yaml

  3. 部署密钥服务

    vim dashboard-configmap-secret.yaml

    apiVersion: v1
kind: Secret
metadata:
  labels:
    k8s-app: kubernetes-dashboard
  name: kubernetes-dashboard-certs
  namespace: kube-system
type: Opaque
---
apiVersion: v1
kind: Secret
metadata:
  labels:
    k8s-app: kubernetes-dashboard
  name: kubernetes-dashboard-csrf
  namespace: kube-system
type: Opaque
data:
  csrf: ""
---
apiVersion: v1
kind: Secret
metadata:
  labels:
    k8s-app: kubernetes-dashboard
  name: kubernetes-dashboard-key-holder
  namespace: kube-system
type: Opaque
---
kind: ConfigMap
apiVersion: v1
metadata:
  labels:
    k8s-app: kubernetes-dashboard
  name: kubernetes-dashboard-settings
  namespace: kube-system

    # kubectl apply -f dashboard-configmap-secret.yaml

  4. 部署控制台服务

    vim dashboard-deploy.yaml

    ## Dashboard Service
kind: Service
apiVersion: v1
metadata:
  labels:
    k8s-app: kubernetes-dashboard
  name: kubernetes-dashboard
  namespace: kube-system
spec:
  type: NodePort
  ports:
    - port: 443
      nodePort: 30001
      targetPort: 8443
  selector:
    k8s-app: kubernetes-dashboard
---
## Dashboard Deployment
kind: Deployment
apiVersion: apps/v1
metadata:
  labels:
    k8s-app: kubernetes-dashboard
  name: kubernetes-dashboard
  namespace: kube-system
spec:
  replicas: 1
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      k8s-app: kubernetes-dashboard
  template:
    metadata:
      labels:
        k8s-app: kubernetes-dashboard
    spec:
      serviceAccountName: kubernetes-dashboard
      containers:
        - name: kubernetes-dashboard
          image: kubernetesui/dashboard:v2.0.0
          securityContext:
            allowPrivilegeEscalation: false
            readOnlyRootFilesystem: true
            runAsUser: 1001
            runAsGroup: 2001
          ports:
            - containerPort: 8443
              protocol: TCP
          args:
            - --auto-generate-certificates
            - --namespace=kube-system          #设置为当前部署的Namespace
          resources:
            limits:
              cpu: 1000m
              memory: 512Mi
            requests:
              cpu: 1000m
              memory: 512Mi
          livenessProbe:
            httpGet:
              scheme: HTTPS
              path: /
              port: 8443
            initialDelaySeconds: 30
            timeoutSeconds: 30
          volumeMounts:
            - name: kubernetes-dashboard-certs
              mountPath: /certs
            - name: tmp-volume
              mountPath: /tmp
            - name: localtime
              readOnly: true
              mountPath: /etc/localtime
      volumes:
        - name: kubernetes-dashboard-certs
          secret:
            secretName: kubernetes-dashboard-certs
        - name: tmp-volume
          emptyDir: {}
        - name: localtime
          hostPath:
            type: File
            path: /etc/localtime
      tolerations:
        - key: node-role.kubernetes.io/master
          effect: NoSchedule

    # kubectl apply -f dashboard-deploy.yaml

  5. 部署指标服务

    vim dashboard-metrics.yaml

    ## Dashboard Metrics Service
kind: Service
apiVersion: v1
metadata:
  labels:
    k8s-app: dashboard-metrics-scraper
  name: dashboard-metrics-scraper
  namespace: kube-system
spec:
  ports:
    - port: 8000
      targetPort: 8000
  selector:
    k8s-app: dashboard-metrics-scraper
---
## Dashboard Metrics Deployment
kind: Deployment
apiVersion: apps/v1
metadata:
  labels:
    k8s-app: dashboard-metrics-scraper
  name: dashboard-metrics-scraper
  namespace: kube-system
spec:
  replicas: 1
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      k8s-app: dashboard-metrics-scraper
  template:
    metadata:
      labels:
        k8s-app: dashboard-metrics-scraper
      annotations:
        seccomp.security.alpha.kubernetes.io/pod: 'runtime/default'
    spec:
      serviceAccountName: kubernetes-dashboard
      containers:
        - name: dashboard-metrics-scraper
          image: kubernetesui/metrics-scraper:v1.0.4
          securityContext:
            allowPrivilegeEscalation: false
            readOnlyRootFilesystem: true
            runAsUser: 1001
            runAsGroup: 2001
          ports:
            - containerPort: 8000
              protocol: TCP
          resources:
            limits:
              cpu: 1000m
              memory: 512Mi
            requests:
              cpu: 1000m
              memory: 512Mi
          livenessProbe:
            httpGet:
              scheme: HTTP
              path: /
              port: 8000
            initialDelaySeconds: 30
            timeoutSeconds: 30
          volumeMounts:
          - mountPath: /tmp
            name: tmp-volume
          - name: localtime
            readOnly: true
            mountPath: /etc/localtime
      volumes:
        - name: tmp-volume
          emptyDir: {}
        - name: localtime
          hostPath:
            type: File
            path: /etc/localtime
      nodeSelector:
        "beta.kubernetes.io/os": linux
      tolerations:
        - key: node-role.kubernetes.io/master
          effect: NoSchedule

    # kubectl apply -f dashboard-metrics.yaml

  6. 部署认证服务

    vim dashboard-token.yaml

    kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: admin
  annotations:
    rbac.authorization.kubernetes.io/autoupdate: "true"
roleRef:
  kind: ClusterRole
  name: cluster-admin
  apiGroup: rbac.authorization.k8s.io
subjects:
- kind: ServiceAccount
  name: admin
  namespace: kube-system
---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: admin
  namespace: kube-system
  labels:
    kubernetes.io/cluster-service: "true"
    addonmanager.kubernetes.io/mode: Reconcile

    # kubectl apply -f dashboard-token.yaml

  7. 登陆

    1. 访问链接: https://master:30001/

    2. 获取令牌: 执行以下命令

      kubectl describe secret/$(kubectl get secret -n kube-system |grep admin|awk '{print $1}') -n kube-system

       
   ```txt
   eyJhbGciOiJSUzI1NiIsImtpZCI6Ikp2bV9pZmNIR0xqLUxRREd3QlRzNU1pdnBkYnMxTXRlWG15alBidW0xNTAifQ.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJrdWJlLXN5c3RlbSIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VjcmV0Lm5hbWUiOiJhZG1pbi10b2tlbi1zandkdiIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VydmljZS1hY2NvdW50Lm5hbWUiOiJhZG1pbiIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VydmljZS1hY2NvdW50LnVpZCI6IjUxOTAxNmFkLTU3YjEtNDkzYS04ZGZiLTM2Mzg3NTIwODgwNiIsInN1YiI6InN5c3RlbTpzZXJ2aWNlYWNjb3VudDprdWJlLXN5c3RlbTphZG1pbiJ9.I4voTZHn83jPe7apabqOtTjsBuj0uEbkgQGu1fl2tAbbpocg89NjN-DrTkyrETa7qDVp2bmXCHbIbiJU64xlfifCgNFgO0HnWqvuMgztYnYMUpbYSRuQVumn-WCDsIxBnfK-lIbhdSGZZVS66PK4Rwlf4hQHdE_3oclzBYnoz_i11xoFaDDUhhSLxmIDuBA-HoR-n_LJRDtJEqD7VmCTiDkUECxVpIM2oQtVb-nLxuBQg7M7rsbdWFsp5MJ7f-AdRBFgszEQaezBCt4kf0Uuakl6AC_0fDGjwEo04M12Md5Q7JOkyUNKgPbw0S3p8rxuw07I_LBipTIW8Sznll_wzw
Jas°
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
Docker部署Minio (服务器上部署Minio)
qq_63055262的博客
05-01 1万+
使用Docker在服务器上快速部署Minio的参考教程
docker部署minio对象存储集群
IT
12-22 8069
docker部署minio集群 准备4个节点，配置时间同步，关闭防火墙和selinux。 node1 192.168.92.10 node2 192.168.92.11 node3 192.168.92.12 node4 192.168.92.13 安装docke yum install -y yum-utils device-mapper-persistent-data lvm2 yum-config-manager --add-repo https://mirrors.aliyun.com/docke
Docker部署minio
大爱仙尊
02-24 1651
docker部署minio和安装包部署minio
分布式集群MinIo搭建
ganjing222的博客
09-27 3888
1、分布式MinIO所有节点是通过MINIO_ROOT_USER和MINIO_ROOT_PASSWORD两个参数相互连接和信任，为此，建议在执行MinIO server命令前，为所有节点设置环境变量MINIO_ROOT_USER和MINIO_ROOT_PASSWORD。例如，一个16节点的Minio集群，每个节点16块硬盘，就算8台服务器器宕机，这个集群仍然是可读的，不过你需要9台服务器才能写数据。5、建议所有运行分布式MinIO设置的节点都是同构的，即相同的操作系统、相同的硬盘数量和相同的网络互连。
基于Docker的Minio集群部署
wu624218376的博客
10-25 5233
基于Docker的Minio集群部署
K8s安装部署文档说明记录
06-29
K8s安装部署文档说明记录，适用于初学者安装调试部署参考材料
kubernetes K8S超详细安装部署手册
最新发布
02-02
kubernetes的本质是一组服务器集群，它可以在集群的每个节点上运行特定的 程序，来对节点中的容器进行管理。目的是实现资源管理的自动化，主要提供了 如下的主要功能: 自我修复:一旦某一个容器崩溃，能够在1秒中...
k8s-auto-kubernetes/k8s一键安装
12-15
kubernetes/k8s自动安装程序，版本对应:v1.18.2，linux环境 使用kubeadm安装，改程序若环境不符合要求，是不能一键安装的，需按照程序指示分布安装，该程序是为了搭建测试环境时，简化繁琐的配置时所用，不能用作...
k8s安装部署
01-07
Kubernetes是容器集群管理系统，是一个开源的平台，可以实现容器集群的自动化部署、自动扩缩容、维护等功能。 快速部署应用 快速扩展应用 无缝对接新的应用功能 节省资源，优化硬件资源的使用 Kubernetes 特点 可...
k8s安装教程和部署的详细说明
01-24
本文档采用k8s v1.10.0二进制的集群部署方式，主要更改 使用kube-router 代理kube-proxy,使用ingress-nginx做边缘负载,使用haproxy+heartbeat实现高可用 本文档持续更新，后续将继续深入了解prometheus，helm等组件...
分布式minio环境搭建（详细）
m0_74870423的博客
04-13 2337
比如：我们的集群有4个节点，每个节点上一块盘，就算有2两个节点宕机，这个集群仍然是可读的，但是，我们需要3个节点才能让集群写数据。由于是非常轻量级的软件，所以架构上也没有这么复杂，他使用操作系统的文件系统作为存储介质，我们在向任意节点写数据的时候，minIO会自动同步数据到另外的节点，而机制叫做erasure code（纠删码）来保证集群的稳定，保证数据可用，所以我们建议至少使用4个节点来构建集群。早期版本中，每个租户至少有4个盘，最多有16个盘，这个是纠删码的限制，而新版本中是没有限制的。
KeepAlive + nginx的配置记录
weixin_43620243的博客
12-19 556
安装过程： yum install libnl libnl-devel openssl-devel -y wget http://www.keepalived.org/software/keepalived-2.0.10.tar.gz tar zxf keepalived-2.0.10.tar.gz cd keepalived-2.0.10 ./configure --prefix=/usr/lo...
Docker部署高性能分布式存储MinIO
u010797364的博客
06-27 3494
MinIO 是一个基于Apache License v2.0开源协议的对象存储服务。它兼容亚马逊S3云存储服务接口，非常适合于存储大容量非结构化的数据，如照片，视频，日志文件，备份和容器/ VM映像。对象的大小可以从几KB到最大5TB。......
Docker 部署 MinIO
有来技术
04-29 279
Docker 部署 MinIO
Minio部署（单机/单机EC/集群）
sosozha的博客
07-07 1万+
minio搭建
MinIO学习笔记
热门推荐
胜天半子
06-30 3万+
探探的实践：https://mp.weixin.qq.com/s?__biz=MzA4ODg0NDkzOA==&mid=2247487119&idx=1&sn=6e09abb32392e015911be3a1d7f066e5&source=41#wechat_redirect 一、竞品调研 当前的一些开源方案，这些存储方案里面可以分为两种： 一种是可以自定对象名称的； 另外一种是系统自动生成对象名称。 我们的对象名是自己生成的，里面包含了业务逻辑。 1、像 FS 就是国
minio分布式集群的详细搭建
sinat_15946141的博客
04-22 7570
一、基础环境 操作系统：CentOS 7.3 Minio下载 将下载好的minio移动到 /opt/minio/文件夹下 或 者进入到/opt/minio/文件夹下使用下面的命令下载： wgethttps://dl.minio.io/server/minio/release/linux-amd64/minio 二、准备工作 2.1、机器资源 192.168.129.133...
Minio分布式集群搭建
GIS摆渡人
01-16 3413
一、基础环境 操作系统：CentOS 7.3Minio下载 二、准备工作 2.1、机器资源 192.168.0.101 /minio/data1 /minio/data2 192.168.0.102 /minio/data1 /minio/data2 本集群由2台服务器构成（官方推荐集群最小4台服务器），每个服务器上挂载两个磁盘目录，最小数据挂载点为4个 2.2...
minio分布式搭建_Minio分布式集群搭建
weixin_39850143的博客
12-20 172
一、基础环境操作系统：CentOS 7.3二、准备工作2.1、机器资源192.168.0.101/minio/data1 /minio/data2192.168.0.102/minio/data1 /minio/data2本集群由2台服务器构成(官方推荐集群最小4台服务器)，每个服务器上挂载两个磁盘目录，最小数据挂载点为4个2.2、创建相关目录(所有节点)数据存储目录mkdir -p /minio...
Kubernetes K8S详尽安装与部署指南
本篇文章详细介绍了Kubernetes(K8S)的安装部署过程，Kubernetes是一种用于容器编排的开源系统，它将一组服务器集群组织起来，旨在自动化资源管理和容器的生命周期管理。以下是文章中的关键知识点： 1. **K8S前言**...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值