Problem Description
After a Aerospike Kubernetes Operator upgrade to 2.4.0 you may find your Aerospike node pod in a "CrashLoopBackoff" state
You will find this in the init pod logs
DEBUG:pod-name: aerospike-0-1 - Looking for initialized volumes in status.pod.aerospike-0-1.initializedVolumes DEBUG:pod-name: aerospike-0-1 - Checking for rack in rackConfig rack-id: 0 ERROR:pod-name: aerospike-0-1 - Unable to find cleanupThreads 'cleanupThreads'
Explanation
Root cause for this is due to an upgrade to 2.4.0. The upgrade brings a new attribute called cleanupThreads but does not properly initiate the attribute or set it and then when there's an issue we don't have it available. Editing the CR and then applying will refresh the stored CR and set the attribute in Kubernetes. This is slated to be fixed in Aerospike Kubernetes Operator 2.5.0.
Solution
You can update an attribute in the custom resource (CR) yaml such as size, cleanupThreads, or make a change in the AerospikeConfig and then apply it and this will refresh the CR within Kubernetes.