Artifactory HA support a wide range of storage back ends (for more information, see Filestore Configuration).
In this chart, you will set the type of storage you want using
artifactory.persistence.type and pass the required configuration settings. The default storage in this chart is the
file-system replication, where the data is replicated to all nodes.
All storage configurations (except NFS) come with a default
artifactory.persistence.redundancy parameter. This is used to set the number replicas of a binary that should be stored in the cluster's nodes. Once this value is set on initial deployment, you can not update it using Helm. It is recommended to set this to a number greater than half of your cluster's size, and to never scale your cluster down to a size smaller than this number.
Alert: Use a PVC when Using an External Blob Storage
When using external blob storage (for example, AWS S3, Azure blob storage, or Google storage), there is still a need to persist temporary eventual storage in a PVC (Persistent Volume Claims) in cases of loss of connection to the external storage or if the Artifactory pod crashes.
Avoiding the usage of a PVC can lead to data loss in case of unplanned pod termination.
Deploying Artifactory on an OpenShift Cluster and Using the Azure PostgreSQL Database Service
When deploying Artifactory on an OpenShift Cluster while using the Azure PostgreSQL database service, the service requires a TLS encrypted database connection. To learn more, see Metadata Service Troubleshooting.