Warm Restart Aerospike Pods on Kubernetes

The Aerospike Kubernetes Operator allows for warm restart of Aerospike pods on changes to the Aerospike server configuration in the Aerospike Config Section of your Custom Resource (CR) file. This feature requires Aerospike server container images that use tini as the init process.

If dynamic configuration is enabled, dynamic configuration changes do not trigger a warm restart.

note

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

Aerospike Database 5.7.0.9 and later

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

Aerospike Database 5.7.0.8 and earlier

For versions earlier than Aerospike Database 5.7.0.8, container images that use tini have been tagged with the prefix tinistaticbackport.

E.g.

aerospike/aerospike-server-enterprise:tinistaticbackport-5.7.0.8