溫馨提示×

您好，登錄后才能下訂單哦！

密碼登錄×
登錄注冊(cè)×
其他方式登錄
點(diǎn)擊 登錄注冊(cè) 即表示同意《億速云用戶服務(wù)條款》

Kubernetes部署（十）：儲(chǔ)存之glusterfs和heketi部署

發(fā)布時(shí)間：2020-05-31 19:02:12 來源：網(wǎng)絡(luò) 閱讀：5744 作者：李永峰Billy 欄目：云計(jì)算

相關(guān)內(nèi)容：

Kubernetes部署（一）：架構(gòu)及功能說明
Kubernetes部署（二）：系統(tǒng)環(huán)境初始化
Kubernetes部署（三）：CA證書制作
Kubernetes部署（四）：ETCD集群部署
Kubernetes部署（五）：Haproxy、Keppalived部署
Kubernetes部署（六）：Master節(jié)點(diǎn)部署
Kubernetes部署（七）：Node節(jié)點(diǎn)部署
Kubernetes部署（八）：Flannel網(wǎng)絡(luò)部署
Kubernetes部署（九）：CoreDNS、Dashboard、Ingress部署
Kubernetes部署（十）：儲(chǔ)存之glusterfs和heketi部署
Kubernetes部署（十一）：管理之Helm和Rancher部署
Kubernetes部署（十二）：helm部署harbor企業(yè)級(jí)鏡像倉庫

概觀

本指南支持在Kubernetes集群中集成，部署和管理GlusterFS容器化存儲(chǔ)節(jié)點(diǎn)。這使Kubernetes管理員能夠?yàn)槠溆脩籼峁┛煽康墓蚕泶鎯?chǔ)。

包括設(shè)置指南、其中包含一個(gè)示例服務(wù)器pod，它使用動(dòng)態(tài)配置的GlusterFS卷進(jìn)行存儲(chǔ)。對(duì)于那些希望測(cè)試或了解有關(guān)此主題的更多信息的人，請(qǐng)按照主要自述文件中的快速入門說明 了解gluster-kubernetes

本指南旨在演示Heketi在Kubernetes環(huán)境中管理Gluster的最小示例。

基礎(chǔ)設(shè)施要求

  • 一個(gè)正在運(yùn)行的Kubernetes集群，至少有三個(gè)Kubernetes工作節(jié)點(diǎn)，每個(gè)節(jié)點(diǎn)至少連接一個(gè)可用的原始?jí)K設(shè)備（如EBS卷或本地磁盤）。 
    #使用file -s 查看硬盤如果顯示為data則為原始?jí)K設(shè)備。如果不是data類型，可先用pvcreate，pvremove來變更。
[root@node-04 ~]# file -s /dev/sdc
/dev/sdc: x86 boot sector, code offset 0xb8
[root@node-04 ~]# pvcreate /dev/sdc
WARNING: dos signature detected on /dev/sdc at offset 510. Wipe it? [y/n]: y
Wiping dos signature on /dev/sdc.
Physical volume "/dev/sdc" successfully created.
[root@node-04 ~]# pvremove /dev/sdc
Labels on physical volume "/dev/sdc" successfully wiped.
[root@node-04 ~]# file -s /dev/sdc 
/dev/sdc: data
  • 在glusterfs節(jié)點(diǎn)的宿主機(jī)需要安裝glusterfs-client、glusterfs-fuse包和socat包。 
    yum install -y glusterfs-client glusterfs-fuse socat
  • 每個(gè)kubetnetes節(jié)點(diǎn)的宿主機(jī)需要加載dm_thin_pool模塊modprobe dm_thin_pool

客戶端安裝

Heketi提供CLI，為用戶提供管理Kubernetes中GlusterFS的部署和配置的方法。 在您的客戶端計(jì)算機(jī)上下載并安裝下載并安裝heketi-cli，下載的heketi-cli版本最好是和heketi服務(wù)端版本一致，不然可能會(huì)出現(xiàn)報(bào)錯(cuò)。

Kubernetes部署

  • 部署GlusterFS DaemonSet

    {
"kind": "DaemonSet",
"apiVersion": "extensions/v1beta1",
"metadata": {
    "name": "glusterfs",
    "labels": {
        "glusterfs": "deployment"
    },
    "annotations": {
        "description": "GlusterFS Daemon Set",
        "tags": "glusterfs"
    }
},
"spec": {
    "template": {
        "metadata": {
            "name": "glusterfs",
            "labels": {
                "glusterfs-node": "daemonset"
            }
        },
        "spec": {
            "nodeSelector": {
                "storagenode" : "glusterfs"
            },
            "hostNetwork": true,
            "containers": [
                {
                    "image": "gluster/gluster-centos:latest",
                    "imagePullPolicy": "Always",
                    "name": "glusterfs",
                    "volumeMounts": [
                        {
                            "name": "glusterfs-heketi",
                            "mountPath": "/var/lib/heketi"
                        },
                        {
                            "name": "glusterfs-run",
                            "mountPath": "/run"
                        },
                        {
                            "name": "glusterfs-lvm",
                            "mountPath": "/run/lvm"
                        },
                        {
                            "name": "glusterfs-etc",
                            "mountPath": "/etc/glusterfs"
                        },
                        {
                            "name": "glusterfs-logs",
                            "mountPath": "/var/log/glusterfs"
                        },
                        {
                            "name": "glusterfs-config",
                            "mountPath": "/var/lib/glusterd"
                        },
                        {
                            "name": "glusterfs-dev",
                            "mountPath": "/dev"
                        },
                        {
                            "name": "glusterfs-cgroup",
                            "mountPath": "/sys/fs/cgroup"
                        }
                    ],
                    "securityContext": {
                        "capabilities": {},
                        "privileged": true
                    },
                    "readinessProbe": {
                        "timeoutSeconds": 3,
                        "initialDelaySeconds": 60,
                        "exec": {
                            "command": [
                                "/bin/bash",
                                "-c",
                                "systemctl status glusterd.service"
                            ]
                        }
                    },
                    "livenessProbe": {
                        "timeoutSeconds": 3,
                        "initialDelaySeconds": 60,
                        "exec": {
                            "command": [
                                "/bin/bash",
                                "-c",
                                "systemctl status glusterd.service"
                            ]
                        }
                    }
                }
            ],
            "volumes": [
                {
                    "name": "glusterfs-heketi",
                    "hostPath": {
                        "path": "/var/lib/heketi"
                    }
                },
                {
                    "name": "glusterfs-run"
                },
                {
                    "name": "glusterfs-lvm",
                    "hostPath": {
                        "path": "/run/lvm"
                    }
                },
                {
                    "name": "glusterfs-etc",
                    "hostPath": {
                        "path": "/etc/glusterfs"
                    }
                },
                {
                    "name": "glusterfs-logs",
                    "hostPath": {
                        "path": "/var/log/glusterfs"
                    }
                },
                {
                    "name": "glusterfs-config",
                    "hostPath": {
                        "path": "/var/lib/glusterd"
                    }
                },
                {
                    "name": "glusterfs-dev",
                    "hostPath": {
                        "path": "/dev"
                    }
                },
                {
                    "name": "glusterfs-cgroup",
                    "hostPath": {
                        "path": "/sys/fs/cgroup"
                    }
                }
            ]
        }
    }
}
}
    $ kubectl create -f glusterfs-daemonset.json
  • 通過運(yùn)行獲取節(jié)點(diǎn)名稱：
$ kubectl get nodes
  • 通過storagenode=glusterfs在該節(jié)點(diǎn)上設(shè)置標(biāo)簽，將gluster容器部署到指定節(jié)點(diǎn)上。
[root@node-01 heketi]# kubectl label node 10.31.90.204 storagenode=glusterfs
[root@node-01 heketi]# kubectl label node 10.31.90.205 storagenode=glusterfs
[root@node-01 heketi]# kubectl label node 10.31.90.206 storagenode=glusterfs

根據(jù)需要,驗(yàn)證pod正在節(jié)點(diǎn)上運(yùn)行，至少應(yīng)運(yùn)行三個(gè)pod。

$ kubectl get pods

  • 接下來我們將為Heketi創(chuàng)建一個(gè)ServiceAccount：

    {
"apiVersion": "v1",
"kind": "ServiceAccount",
"metadata": {
"name": "heketi-service-account"
}
}
    $ kubectl create -f heketi-service-account.json

  • 我們現(xiàn)在必須建立該服務(wù)帳戶控制gluster pod的能力。我們通過為新創(chuàng)建的服務(wù)帳戶創(chuàng)建集群角色綁定來實(shí)現(xiàn)此目的。

    $ kubectl create clusterrolebinding heketi-gluster-admin --clusterrole=edit --serviceaccount=default:heketi-service-account
  • 現(xiàn)在我們需要?jiǎng)?chuàng)建一個(gè)Kubernetes secret，它將保存我們的Heketi實(shí)例的配置。必須將配置文件設(shè)置為使用 kubernetes執(zhí)行程序，以便Heketi服務(wù)器控制gluster pod。除此之外，您可以隨意嘗試配置選項(xiàng)。
{
  "_port_comment": "Heketi Server Port Number",
  "port": "8080",

  "_use_auth": "Enable JWT authorization. Please enable for deployment",
  "use_auth": false,

  "_jwt": "Private keys for access",
  "jwt": {
    "_admin": "Admin has access to all APIs",
    "admin": {
      "key": "My Secret"
    },
    "_user": "User only has access to /volumes endpoint",
    "user": {
      "key": "My Secret"
    }
  },

  "_glusterfs_comment": "GlusterFS Configuration",
  "glusterfs": {
    "_executor_comment": "Execute plugin. Possible choices: mock, kubernetes, ssh",
    "executor": "kubernetes",

    "_db_comment": "Database file name",
    "db": "/var/lib/heketi/heketi.db",

    "kubeexec": {
      "rebalance_on_expansion": true
    },

    "sshexec": {
      "rebalance_on_expansion": true,
      "keyfile": "/etc/heketi/private_key",
      "fstab": "/etc/fstab",
      "port": "22",
      "user": "root",
      "sudo": false
    }
  },

  "_backup_db_to_kube_secret": "Backup the heketi database to a Kubernetes secret when running in Kubernetes. Default is off.",
  "backup_db_to_kube_secret": false
}

$ kubectl create secret generic heketi-config-secret --from-file=./heketi.json
  • 接下來，我們需要部署一個(gè)初始Pod和一個(gè)服務(wù)來訪問該pod。如下會(huì)有一個(gè)heketi-bootstrap.json文件。
    提交文件并驗(yàn)證一切正常運(yùn)行，如下所示： 
    {
"kind": "List",
"apiVersion": "v1",
"items": [
{
  "kind": "Service",
  "apiVersion": "v1",
  "metadata": {
    "name": "deploy-heketi",
    "labels": {
      "glusterfs": "heketi-service",
      "deploy-heketi": "support"
    },
    "annotations": {
      "description": "Exposes Heketi Service"
    }
  },
  "spec": {
    "selector": {
      "name": "deploy-heketi"
    },
    "ports": [
      {
        "name": "deploy-heketi",
        "port": 8080,
        "targetPort": 8080
      }
    ]
  }
},
{
  "kind": "Deployment",
  "apiVersion": "extensions/v1beta1",
  "metadata": {
    "name": "deploy-heketi",
    "labels": {
      "glusterfs": "heketi-deployment",
      "deploy-heketi": "deployment"
    },
    "annotations": {
      "description": "Defines how to deploy Heketi"
    }
  },
  "spec": {
    "replicas": 1,
    "template": {
      "metadata": {
        "name": "deploy-heketi",
        "labels": {
          "name": "deploy-heketi",
          "glusterfs": "heketi-pod",
          "deploy-heketi": "pod"
        }
      },
      "spec": {
        "serviceAccountName": "heketi-service-account",
        "containers": [
          {
            "image": "heketi/heketi:8",
            "imagePullPolicy": "Always",
            "name": "deploy-heketi",
            "env": [
              {
                "name": "HEKETI_EXECUTOR",
                "value": "kubernetes"
              },
              {
                "name": "HEKETI_DB_PATH",
                "value": "/var/lib/heketi/heketi.db"
              },
              {
                "name": "HEKETI_FSTAB",
                "value": "/var/lib/heketi/fstab"
              },
              {
                "name": "HEKETI_SNAPSHOT_LIMIT",
                "value": "14"
              },
              {
                "name": "HEKETI_KUBE_GLUSTER_DAEMONSET",
                "value": "y"
              }
            ],
            "ports": [
              {
                "containerPort": 8080
              }
            ],
            "volumeMounts": [
              {
                "name": "db",
                "mountPath": "/var/lib/heketi"
              },
              {
                "name": "config",
                "mountPath": "/etc/heketi"
              }
            ],
            "readinessProbe": {
              "timeoutSeconds": 3,
              "initialDelaySeconds": 3,
              "httpGet": {
                "path": "/hello",
                "port": 8080
              }
            },
            "livenessProbe": {
              "timeoutSeconds": 3,
              "initialDelaySeconds": 30,
              "httpGet": {
                "path": "/hello",
                "port": 8080
              }
            }
          }
        ],
        "volumes": [
          {
            "name": "db"
          },
          {
            "name": "config",
            "secret": {
              "secretName": "heketi-config-secret"
            }
          }
        ]
      }
    }
  }
}
]
}
# kubectl create -f heketi-bootstrap.json
service "deploy-heketi" created
deployment "deploy-heketi" created

[root@node-01 heketi]# kubectl get pod
NAME                            READY     STATUS    RESTARTS   AGE
deploy-heketi-8888799fd-cmfp6   1/1       Running   0          6m
glusterfs-7t5ls                 1/1       Running   0          8m
glusterfs-drsx9                 1/1       Running   0          8m
glusterfs-pnnn8                 1/1       Running   0          8m
  • 現(xiàn)在Bootstrap Heketi服務(wù)正在運(yùn)行，我們將配置端口轉(zhuǎn)發(fā)，以便我們可以使用Heketi CLI與服務(wù)進(jìn)行通信。使用Heketi pod的名稱，運(yùn)行以下命令：
kubectl port-forward deploy-heketi-8888799fd-cmfp6 :8080

如果在運(yùn)行命令的系統(tǒng)上本地端口8080空閑，則可以運(yùn)行port-forward命令，以便它為了方便而綁定到8080：

kubectl port-forward deploy-heketi-8888799fd-cmfp6 18080:8080

現(xiàn)在通過對(duì)Heketi服務(wù)運(yùn)行示例查詢來驗(yàn)證端口轉(zhuǎn)發(fā)是否正常工作。該命令應(yīng)該打印將要轉(zhuǎn)發(fā)的本地端口。將其合并到URL中以測(cè)試服務(wù)，如下所示：

curl http://localhost:18080/hello
Handling connection for 18080
Hello from Heketi

最后，為Heketi CLI客戶端設(shè)置環(huán)境變量，以便它知道如何到達(dá)Heketi Server。

export HEKETI_CLI_SERVER=http://localhost:18080

  • 接下來，我們將向Heketi提供有關(guān)要管理的GlusterFS集群的信息。我們通過拓?fù)湮募峁┐诵畔?。您克隆的repo中有一個(gè)示例拓?fù)湮募?，名為topology-sample.json。拓?fù)渲付ㄟ\(yùn)行GlusterFS容器的Kubernetes節(jié)點(diǎn)以及每個(gè)節(jié)點(diǎn)的相應(yīng)原始?jí)K設(shè)備。

  • 確保hostnames/manage指向下面顯示的確切名稱kubectl get nodes，并且hostnames/storage是存儲(chǔ)網(wǎng)絡(luò)的IP地址。

  • 重要信息：此時(shí)，必須使用與服務(wù)器版本匹配的heketi-cli版本加載拓?fù)湮募?。作為最后的手段，Heketi容器附帶了一份可以通過的方式訪問的heketi-cli kubectl exec ...。

修改拓?fù)湮募苑从衬龅倪x擇，然后部署它，如下所示：

{
  "clusters": [
    {
      "nodes": [
        {
          "node": {
            "hostnames": {
              "manage": [
                "10.31.90.204"
              ],
              "storage":[
                "10.31.90.204"
              ]
            },
            "zone": 1
          },
          "devices": [
            "/dev/sdc"
          ]
        },
        {
          "node": {
            "hostnames": {
              "manage": [
                "10.31.90.205"
              ],
              "storage":[
                "10.31.90.205"
              ]
            },
            "zone": 1
          },
          "devices": [
            "/dev/sdc"
          ]
        },
        {
          "node": {
            "hostnames": {
              "manage": [
                "10.31.90.206"
              ],
              "storage":[
                "10.31.90.206"
              ]
            },
            "zone": 1
          },
          "devices": [
            "/dev/sdc"
          ]
        }
      ]
    }
  ]
}

[root@node-01 ~]# heketi-cli topology load --json=top.json
Creating cluster ... ID: e758afb77ee26d5f969d7efee1516e64
        Allowing file volumes on cluster.
        Allowing block volumes on cluster.
        Creating node 10.31.90.204 ... ID: a6eedd58c118dcfe44a0db2af1a4f863
                Adding device /dev/sdc ... OK
        Creating node 10.31.90.205 ... ID: 4066962c14bcdebd28aca193b5690792
                Adding device /dev/sdc ... OK
        Creating node 10.31.90.206 ... ID: 91e42a2361f0266ae334354e5c34ce11
                Adding device /dev/sdc ... OK
  • 接下來我們將使用Heketi為它配置一個(gè)卷來存儲(chǔ)其數(shù)據(jù)庫：

執(zhí)行此命令后會(huì)生成一個(gè)heketi-storage.json的文件，我們最好是將此文件里的
"image": "heketi/heketi:dev"
改為
"image": "heketi/heketi:8"

# heketi-client/bin/heketi-cli setup-openshift-heketi-storage

然后在創(chuàng)建heketi相關(guān)服務(wù)

# kubectl create -f heketi-storage.json

陷阱：如果heketi-cli在運(yùn)行setup-openshift-heketi-storage子命令時(shí)報(bào)告“無空間”錯(cuò)誤，則可能無意中運(yùn)行topology load了服務(wù)器和heketi-cli的不匹配版本。停止正在運(yùn)行的Heketi pod（kubectl scale deployment deploy-heketi --replicas=0），手動(dòng)從存儲(chǔ)塊設(shè)備中刪除任何簽名，然后繼續(xù)運(yùn)行Heketi pod（kubectl scale deployment deploy-heketi --replicas=1）。然后使用匹配版本的heketi-cli重新加載拓?fù)洳⒅卦囋摬襟E。

  • 等到作業(yè)完成然后刪除引導(dǎo)程序Heketi：
# kubectl delete all,service,jobs,deployment,secret --selector="deploy-heketi"
  • 創(chuàng)建長(zhǎng)期Heketi實(shí)例： 
    {
"kind": "List",
"apiVersion": "v1",
"items": [
{
  "kind": "Secret",
  "apiVersion": "v1",
  "metadata": {
    "name": "heketi-db-backup",
    "labels": {
      "glusterfs": "heketi-db",
      "heketi": "db"
    }
  },
  "data": {
  },
  "type": "Opaque"
},
{
  "kind": "Service",
  "apiVersion": "v1",
  "metadata": {
    "name": "heketi",
    "labels": {
      "glusterfs": "heketi-service",
      "deploy-heketi": "support"
    },
    "annotations": {
      "description": "Exposes Heketi Service"
    }
  },
  "spec": {
    "selector": {
      "name": "heketi"
    },
    "ports": [
      {
        "name": "heketi",
        "port": 8080,
        "targetPort": 8080
      }
    ]
  }
},
{
  "kind": "Deployment",
  "apiVersion": "extensions/v1beta1",
  "metadata": {
    "name": "heketi",
    "labels": {
      "glusterfs": "heketi-deployment"
    },
    "annotations": {
      "description": "Defines how to deploy Heketi"
    }
  },
  "spec": {
    "replicas": 1,
    "template": {
      "metadata": {
        "name": "heketi",
        "labels": {
          "name": "heketi",
          "glusterfs": "heketi-pod"
        }
      },
      "spec": {
        "serviceAccountName": "heketi-service-account",
        "containers": [
          {
            "image": "heketi/heketi:8",
            "imagePullPolicy": "Always",
            "name": "heketi",
            "env": [
              {
                "name": "HEKETI_EXECUTOR",
                "value": "kubernetes"
              },
              {
                "name": "HEKETI_DB_PATH",
                "value": "/var/lib/heketi/heketi.db"
              },
              {
                "name": "HEKETI_FSTAB",
                "value": "/var/lib/heketi/fstab"
              },
              {
                "name": "HEKETI_SNAPSHOT_LIMIT",
                "value": "14"
              },
              {
                "name": "HEKETI_KUBE_GLUSTER_DAEMONSET",
                "value": "y"
              }
            ],
            "ports": [
              {
                "containerPort": 8080
              }
            ],
            "volumeMounts": [
              {
                "mountPath": "/backupdb",
                "name": "heketi-db-secret"
              },
              {
                "name": "db",
                "mountPath": "/var/lib/heketi"
              },
              {
                "name": "config",
                "mountPath": "/etc/heketi"
              }
            ],
            "readinessProbe": {
              "timeoutSeconds": 3,
              "initialDelaySeconds": 3,
              "httpGet": {
                "path": "/hello",
                "port": 8080
              }
            },
            "livenessProbe": {
              "timeoutSeconds": 3,
              "initialDelaySeconds": 30,
              "httpGet": {
                "path": "/hello",
                "port": 8080
              }
            }
          }
        ],
        "volumes": [
          {
            "name": "db",
            "glusterfs": {
              "endpoints": "heketi-storage-endpoints",
              "path": "heketidbstorage"
            }
          },
          {
            "name": "heketi-db-secret",
            "secret": {
              "secretName": "heketi-db-backup"
            }
          },
          {
            "name": "config",
            "secret": {
              "secretName": "heketi-config-secret"
            }
          }
        ]
      }
    }
  }
}
]
}
# kubectl create -f heketi-deployment.json
service "heketi" created
deployment "heketi" created
  • 現(xiàn)在這樣做了，Heketi數(shù)據(jù)庫將保留在GlusterFS卷中，并且每次重啟Heketi pod時(shí)都不會(huì)重置。

使用諸如heketi-cli cluster list和之類的命令heketi-cli volume list 來確認(rèn)先前建立的集群是否存在，以及Heketi是否知道在引導(dǎo)階段創(chuàng)建的db存儲(chǔ)卷。

演示測(cè)試

  1. 接下來就是建立存儲(chǔ)卷，然后掛載測(cè)試。
    在測(cè)試之前我們需要先將heketi服務(wù)通過Ingress對(duì)外發(fā)布，將heketi.cnlinux.club的A記錄解析為10.31.90.200。 
    apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: ingress-heketi
annotations:
nginx.ingress.kubernetes.io/rewrite-target: /
kubernetes.io/ingress.class: nginx
spec:
rules:
- host: heketi.cnlinux.club
  http:
    paths:
      - path: 
        backend:
          serviceName: heketi
          servicePort: 8080
    [root@node-01 heketi]# kubectl create -f ingress-heketi.yaml

    在瀏覽器訪問http://heketi.cnlinux.club/hello
    Kubernetes部署（十）：儲(chǔ)存之glusterfs和heketi部署

  2. 創(chuàng)建StorageClass
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: gluster-heketi
provisioner: kubernetes.io/glusterfs
parameters:
  resturl: "http://heketi.cnlinux.club"
  restauthenabled: "false" 
  volumetype: "replicate:2"
[root@node-01 heketi]# kubectl create -f storageclass-gluster-heketi.yaml
[root@node-01 heketi]# kubectl get sc
NAME             PROVISIONER               AGE
gluster-heketi   kubernetes.io/glusterfs   10s
  1. 創(chuàng)建pvc 
    apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: pvc-gluster-heketi
spec:
storageClassName: gluster-heketi
accessModes:
- ReadWriteOnce
resources:
requests:
  storage: 1Gi
    [root@node-01 heketi]# kubectl create -f pvc-gluster-heketi.yaml 
[root@node-01 heketi]# kubectl get pvc
NAME                 STATUS    VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS     AGE
pvc-gluster-heketi   Bound     pvc-d978f524-0b74-11e9-875c-005056826470   1Gi        RWO            gluster-heketi   30s
  2. 在pod里掛載pvc 
    apiVersion: v1
kind: Pod
metadata:
name: pod-pvc
spec:
containers:
- name: pod-pvc
image: busybox:latest
command:
- sleep
- "3600"
volumeMounts:
- name: gluster-volume
  mountPath: "/pv-data"
volumes:
- name: gluster-volume
  persistentVolumeClaim:
    claimName: pvc-gluster-heketi
    [root@node-01 heketi]# kubectl create -f pod-pvc.yaml

    進(jìn)入容器查看是否已經(jīng)掛載成功

    [root@node-01 heketi]# kubectl exec pod-pvc -it /bin/sh
/ # df -h
Filesystem                Size      Used Available Use% Mounted on
overlay                  47.8G      4.3G     43.5G   9% /
tmpfs                    64.0M         0     64.0M   0% /dev
tmpfs                     1.9G         0      1.9G   0% /sys/fs/cgroup
10.31.90.204:vol_675cc9fe0e959157919c886ea7786d33
                   1014.0M     42.7M    971.3M   4% /pv-data
/dev/sda3                47.8G      4.3G     43.5G   9% /dev/termination-log
/dev/sda3                47.8G      4.3G     43.5G   9% /etc/resolv.conf
/dev/sda3                47.8G      4.3G     43.5G   9% /etc/hostname
/dev/sda3                47.8G      4.3G     43.5G   9% /etc/hosts

    #往/pv-data寫文件，當(dāng)容量超過1G時(shí)就自動(dòng)退出了，證明容量限制是生效的。

    / # cd /pv-data/
/pv-data # dd if=/dev/zero of=/pv-data/test.img bs=8M count=300
123+0 records in
122+0 records out
1030225920 bytes (982.5MB) copied, 24.255925 seconds, 40.5MB/s

    在宿主機(jī)磁盤里查看是否創(chuàng)建了test.img文件

    [root@node-04 cfg]# mount /dev/vg_2631413b8b87bbd6cb526568ab697d37/brick_1691ef862dd504e12e8384af76e5a9f2 /mnt
[root@node-04 cfg]# ll -h /mnt/brick/
total 982M
-rw-r--r-- 2 root 2001 982M Jan  2 15:14 test.img

    至此，所有的操作都已完成。

向AI問一下細(xì)節(jié)

免責(zé)聲明：本站發(fā)布的內(nèi)容（圖片、視頻和文字）以原創(chuàng)、轉(zhuǎn)載和分享為主，文章觀點(diǎn)不代表本網(wǎng)站立場(chǎng)，如果涉及侵權(quán)請(qǐng)聯(lián)系站長(zhǎng)郵箱：is@yisu.com進(jìn)行舉報(bào)，并提供相關(guān)證據(jù)，一經(jīng)查實(shí)，將立刻刪除涉嫌侵權(quán)內(nèi)容。

AI
助
手