As of this writing, aerospike-operator
and the Aerospike cluster it manages have the following limitations:
-
aerospike-operator
supports Aerospike Community Edition only [1]. -
There must be exactly one Aerospike namespace per Aerospike cluster.
-
Fully customizing the Aerospike configuration file is not supported [2].
-
Raw device and file storage support are limited to 2TB per namespace.
-
The replication factor and the storage spec for an existing Aerospike namespace cannot be changed. In particular, this means that resizing existing persistent volumes is not supported.
-
The backup and restore functionality supports Google Cloud Storage only.