Skip to main content
Version: Operator 3.2.2

Warm Restart Aerospike Pods on Kubernetes

Aerospike operator 3.2.2 allows for warm restart of Aerospike pods on changes to the Aerospike server configuration in the Aerospike Config Section of your custom resource. This feature requires Aerospike server container images that use tini as the init process.


The warm restart feature does not apply to upgrades of Aerospike server. Pods will always cold start following an upgrade.

Aerospike Server and later

Container images for Aerospike enterprise server and later use tini init by default and will warm restart on Aerospike configuration changes.

Aerospike Server and prior

For Aerospike enterprise server and prior, container images that use tini have been tagged with the prefix 'tinistaticbackport'.