ArcGIS Enterprise on Kubernetes requires persistent volumes (PVs) for system storage, which can be provisioned dynamically through a storage class or statically by an administrator prior to creating the organization.
For dynamic provisioning, a StorageClass is required. Review the following recommendations:
- The reclaimPolicy field can be set to Delete to simplify administration. This will clean up the associated PV when a PVC is deleted (for example, when you undeploy the software).
- A separate StorageClass should be used for the hosted backup store configuration with its reclaimPolicy field set to Retain so that the PV persists when you undeploy and redeploy.
- The allowVolumeExpansion field on the StorageClass can be set to true if your storage provider supports the expansion of PVs.
- For clusters spanning multiple availability zones, the volumeBindingMode must be set to WaitForFirstConsumer for the associated storage class to avoid node-volume affinity conflicts.
Note:
Not all VM types support premium disks in Azure. Use a premium disk when the VM type supports it.For clusters with default storage classes you can use the default storage class, but you must confirm that the values set for the reclaimPolicy and allowVolumeExpansion fields meet your needs prior to creating the organization.
For more information, see the example YAML files for Azure Kubernetes Service, Amazon EKS, Google Kubernetes Engine, and Red Hat OpenShift, or consult the provider's documentation.