无法理解 gluster 和 gluster-block 卷之间的区别
Cannot understand the difference between gluster and gluster-block volumes
我很难区分 GlusterFS 和 gluster-block 卷
如您在 openshift 文档中所见，提到 Glusterfs 一次只能由一个 node/client 安装。那是什么意思？这是否意味着如果我将 kubernetes 与 3 个容器一起使用，我不能与 3 个容器共享它？或者这是否意味着如果我在 kubernetes 和 3 pods 中有一个部署，只有这 3 个 pods 可以使用该卷而其他部署将无法使用它？
基于 openshift and kubernetes
中的文档
Gluster-block volumes can only be mounted by one node/client at a time which is in contrast to GlusterFS volumes which can be mounted by multiple nodes/clients
A glusterfs volume allows a Glusterfs (an open source networked filesystem) volume to be mounted into your Pod. Unlike emptyDir, which is erased when a Pod is removed, the contents of a glusterfs volume are preserved and the volume is merely unmounted. This means that a glusterfs volume can be pre-populated with data, and that data can be “handed off” between Pods. GlusterFS can be mounted by multiple writers simultaneously.
有一个 example 提供了有关如何允许容器使用 GlusterFS 卷的信息
A Pod is the basic execution unit of a Kubernetes application -> the smallest and simplest unit in the Kubernetes object model that you create or deploy. A Pod represents processes running on your Cluster.
You can have one or more containers inside Pod. All containers share a unique IP, storage, network and any other specification applied to the pod.
A Pod can specify a set of shared storage Volumes. All containers in the Pod can access the shared volumes, allowing those containers to share data. Volumes also allow persistent data in a Pod to survive in case one of the containers within needs to be restarted. See Volumes for more information on how Kubernetes implements shared storage in a Pod.
我很难区分 GlusterFS 和 gluster-block 卷
如您在 openshift 文档中所见，提到 Glusterfs 一次只能由一个 node/client 安装。那是什么意思？这是否意味着如果我将 kubernetes 与 3 个容器一起使用，我不能与 3 个容器共享它？或者这是否意味着如果我在 kubernetes 和 3 pods 中有一个部署，只有这 3 个 pods 可以使用该卷而其他部署将无法使用它？
基于 openshift and kubernetes
中的文档Gluster-block volumes can only be mounted by one node/client at a time which is in contrast to GlusterFS volumes which can be mounted by multiple nodes/clients
A glusterfs volume allows a Glusterfs (an open source networked filesystem) volume to be mounted into your Pod. Unlike emptyDir, which is erased when a Pod is removed, the contents of a glusterfs volume are preserved and the volume is merely unmounted. This means that a glusterfs volume can be pre-populated with data, and that data can be “handed off” between Pods. GlusterFS can be mounted by multiple writers simultaneously.
有一个 example 提供了有关如何允许容器使用 GlusterFS 卷的信息
A Pod is the basic execution unit of a Kubernetes application -> the smallest and simplest unit in the Kubernetes object model that you create or deploy. A Pod represents processes running on your Cluster.
You can have one or more containers inside Pod. All containers share a unique IP, storage, network and any other specification applied to the pod.
A Pod can specify a set of shared storage Volumes. All containers in the Pod can access the shared volumes, allowing those containers to share data. Volumes also allow persistent data in a Pod to survive in case one of the containers within needs to be restarted. See Volumes for more information on how Kubernetes implements shared storage in a Pod.