Articles in this section

Does the operator restart the pods after deployment thereby automatically reflecting changes in the aerospike.conf file in the pods?

Detail

When Aerospike operator is used to deploy the configuration changes, does the operator restart the pods after deployment so that the new configs are reflected automatically in the aerospike.conf file in the pods?

Answer

When using Aerospike Kubernetes Operator, the aerospike.conf in the pods is always regenerated from the Operator Custom Resource definition (CR) YAML file. These will be lost, if changes are made directly to the aerospike.conf.

It is recommended to make changes to custom resource YAML file. If changes are made to the Aerospike config section of the custom resource YAML file, the operator will regenerate the aerospike.conf and warm start the services.
Was this article helpful?
0 out of 0 found this helpful