Version 1.1. This version is no longer supported as outlined in the Anthos version support policy. For the latest patches and updates for security vulnerabilities, exposures, and issues impacting Anthos clusters on VMware (GKE on-prem), upgrade to a supported version. You can find the most recent version here.

Storage

GKE On-Prem integrates with external block or file storage systems through VMware vSphere storage, Kubernetes in-tree volume plugins, and Container Storage Interface (CSI) drivers.

vSphere storage

By default, both GKE On-Prem admin and user clusters use vSphere storage. The admin cluster requires a pre-provisioned VMware datastore for its etcd data.

When you create a user cluster, GKE On-Prem uses the vSphere Kubernetes volume plugin to dynamically provision a new virtual machine disk (VMDK) in the same VMware datastore used by the admin cluster. This VMDK holds the user cluster's etcd data.

The default StorageClass for a user cluster points to a VMware datastore. By default, Kubernetes PersistentVolumes provisioned for the user cluster are VMDKs that datastore. This is not necessarily the same datastore used by the admin cluster.

The VMware datastores used by the admin and user clusters may be backed by NFS, vSAN, or VMFS on a block device, such as an external storage array. In a multi-host environment, each block device must be attached to all the hosts in the environment, and the datastore must be configured on each host via the Mount Datastore on Additional Hosts option.

In GKE On-Prem, StatefulSets use PersistentVolumeClaims backed by StorageClasses that point to vSphere storage.

Kubernetes in-tree volume plugins

Kubernetes ships with a number of in-tree volume plugins. You have the option to use any of these to provide block or file storage for your stateful workloads. In-tree plugins enable workloads to connect directly to storage without having to go through vSphere storage.

Whereas vSphere storage automatically provides dynamic provisioning of volumes inside a datastore backed by any iSCSI, FC, or NFS storage device, many of the in-tree plugins don't support dynamic provisioning. They require that you manually create PersistentVolumes.

The following table describes several in-tree volume plugins:

In-tree volume pluginDescriptionSupported access modesDynamic provisioning
Fibre ChannelGeneric storage pluginRead/write single PodNo
iSCSIGeneric storage pluginRead/write single PodNo
NFSGeneric storage pluginRead/write multiple PodsNo
Ceph RBDOpen source software-defined storageRead/write single PodYes
CephFSOpen source software-defined storageRead/write multiple PodsNo
PortworxProprietary software-defined storageRead/write multiple PodsYes
QuobyteProprietary software-defined storageRead/write single PodYes
StorageOSProprietary software-defined storageRead/write single PodYes

Container Storage Interface

Container Storage Interface (CSI) is a standard API that enables Kubernetes to expose arbitrary storage systems to containerized workloads. When you deploy a CSI-compatible volume driver to a Kubernetes cluster, workloads can connect directly to storage without having to go through vSphere storage.

GKE On-Prem ships with Kubernetes 1.13+, which supports CSI v1.0. To use CSI in your cluster, you need to deploy the CSI driver provided by your storage vendor. Then, you can configure workloads to use the driver's StorageClass, or set it as the default StorageClass.

Troubleshooting

See Troubleshooting Storage.