Changing configOverrides doesn't restart NiFi pods

Affected version

23.7

Current and expected behavior

When I add a configOverrides entry to the NifiCluster resource the config-map -node-default will get updated, but as the pod doesn't restart the update doesn't have any effect.

I would expect that the operator ensures the pod will be restarted, so that the new config override will be active.

Possible solution

I think that's a usual issue with Kubernetes apps that ConfigMaps will be updated but the updates are not reflected inside the pod. There are several solutions available, e. g. kustomize appends a kind of hash to the ConfigMap name and has to update the deployment with the new name to force a restart of the pods.

I don't have any explicit solution here.

Additional context

No extra context, but the documentation is also a bit hard to understand in this regards (https://docs.stackable.tech/home/stable/nifi/usage_guide/configuration-environment-overrides). I was not sure where to put the configOverrides properties.. Looking at the CRD I found out I have to put it below nodes.

Environment

Client Version: v1.27.3
Kustomize Version: v5.0.1
Server Version: v1.26.8+k3s1
Stackable Version 23.7
NiFi product version: 1.21.0

Would you like to work on fixing this bug?

None

Start by tracing how the NifiCluster resource updates the config-map -node-default and how that change is reflected in the pod definition. Compare the available restart mechanisms for Kubernetes workloads, then verify that changing configOverrides causes the affected NiFi pods to restart and use the new configuration.