Limitations

General

• Multiple clusters can not be managed by a single operator
• Cluster and operator should belong to same k8s namespace
• Operator does not support Aerospike Community Edition (CE)

While deploying cluster

• AerospikeCluster name can not have char '-'
• Supported build base version:
• aeroapikeConfig can not be empty
• aeroapikeConfig.namespace can not be nil or empty
• ca-path in TLS config not allowed, Only ca-file is allowed
• Rack awareness not supported yet
• Strong consistency mode not supported yet
• Warm restart not supported yet

While updating an already deployed cluster

• BlockStorage config can not be updated
• FileStorage config can not be updated
• MultiPodPerHost can not be updated
• Cluster security config can not be updated
• TLS config can not be updated
• aerospikeConfig.namespace.replication-factor can not be update
• aeroapikeConfig.namespace list can not be updated. Hence no new namespace can be added
• Namespace storage device can not be resized. No new storage device can be added

These values can not be given in aerospikeConfig in yaml config file. These are fixed or determined at runtime.

• service.node-id
• service.cluster-name
• network.service.port
• network.service.access-port
• network.service.alternate-access-port
• network.service.alternate-access-address
• network.service.tls-port
• network.service.tls-access-port
• network.service.tls-access-address
• network.service.tls-alternate-access-port
• network.service.tls-alternate-access-address
• network.heartbeat.mode
• network.heartbeat.port
• network.heartbeat.tls-port
• network.fabric.port
• network.fabric.tls-port