GlusterFS Kubernetes: Difference between revisions
Jump to navigation
Jump to search
| (4 intermediate revisions by the same user not shown) | |||
| Line 15: | Line 15: | ||
A hyper-converged GlusterFS cluster installation is an installation where GlusterFS infrastructure software is deployed within the Kubernetes cluster itself, as opposite to a [[#Separate_GlusterFS_Cluster_Installation|separate GlusterFS cluster installation]]. | A hyper-converged GlusterFS cluster installation is an installation where GlusterFS infrastructure software is deployed within the Kubernetes cluster itself, as opposite to a [[#Separate_GlusterFS_Cluster_Installation|separate GlusterFS cluster installation]]. | ||
<font color=darkgray> | |||
For prerequisites, followed https://github.com/gluster/gluster-kubernetes/blob/master/docs/setup-guide.md#infrastructure-requirements. | |||
The attempt to use the installation script (gk-deploy) failed with Kubernetes 1.15, as the script used deprecated kubectl CLI and made invalid assumptions about accessing Kubernetes services. | |||
</font> | |||
==Separate GlusterFS Cluster Installation== | ==Separate GlusterFS Cluster Installation== | ||
=<span id='glusterfs_Volumes'></span>glusterfs Kubernetes Volumes= | |||
{{Internal|Kubernetes_Storage_Concepts#glusterfs|glusterfs Kubernetes Volume}} | |||
Latest revision as of 23:00, 11 December 2019
External
- https://github.com/gluster/gluster-kubernetes
- https://github.com/kubernetes/examples/tree/master/staging/persistent-volume-provisioning#glusterfs
Internal
Overview
Installation
Hyper-Converged GlusterFS Cluster Installation
A hyper-converged GlusterFS cluster installation is an installation where GlusterFS infrastructure software is deployed within the Kubernetes cluster itself, as opposite to a separate GlusterFS cluster installation.
For prerequisites, followed https://github.com/gluster/gluster-kubernetes/blob/master/docs/setup-guide.md#infrastructure-requirements.
The attempt to use the installation script (gk-deploy) failed with Kubernetes 1.15, as the script used deprecated kubectl CLI and made invalid assumptions about accessing Kubernetes services.