Invalid memory config error when upgrading NiFi from 24.11 to 25.3

A cluster running Stackable 24.11 and NiFi 2.0.0 was upgraded to Stackable 25.3 and NiFi 2.2.0. The only change to the NifiCluster definition was to change spec.image.productVersion from 2.0.0 to 2.2.0. When the updated CRD is applied an error is shown in the Stackable NiFi operator logs:

ERROR stackable_operator::logging::controller: Failed to reconcile object controller.name="nificluster.nifi.stackable.tech" error=reconciler for objec
t NifiCluster.v1alpha1.nifi.stackable.tech/poc-nifi.default failed error.sources=[Bootstrap configuration error, invalid JVM config, invalid memory config, invalid quantity unit
G"[]

Upon inspection the deployed CRD does show an invalid value of 8G for spec.nodes.config.resource.memory.limit. The issue can be resolved by explicitly setting spec.nodes.config.resource.memory.limit to valid value in the CRD.

The expectation is that upgrading the operator should not break an otherwise valid CRD or that an invalid CRD should not be accepted.

Start by reproducing the upgrade from Stackable 24.11/NiFi 2.0.0 to Stackable 25.3/NiFi 2.2.0 and inspect the NifiCluster CRD field spec.nodes.config.resource.memory.limit. Trace how the operator handles the existing 8G value during reconciliation and validate the result against the expected memory quantity format. Done means the upgrade preserves a valid configuration or rejects the invalid value with a clear validation error.