The following provides important information related to 2.0:

...

• The mzOperator.* values have been moved to operator.*.
• The operator has been made more event driven and less dependent on frequent periodic synchronizations.
  As a result the default synchronization period has changed from 30 seconds to 300 seconds (5 minutes).
  Use the operator.syncPeriod value to set a different synchronization period.

• The default memory limits for the platform JVM has changed. What used to be:

  Code Block
  jvmArgs: - XX:MaxDirectMemorySize=4096m - XX:MaxMetaspaceSize=256m - Xms256m - Xmx512m

  Is now:

  Code Block
  jvmArgs: - XX:MaxMetaspaceSize=512m - Xms256m - Xmx2g

  


Anchor
rollback rollback

Action Required for Rollback from 3.x to 2.x

If you need to perform a helm rollback from a 3.x version to a 2.x version, the existing EC Deployment need to patched after having run the helm rollback command.

...

kubectl get deployments.apps -o custom-columns=NAME:metadata.name --no-headers | while read depl; do \
if [[ -n $(kubectl get deployments.apps $depl -o=jsonpath="{.spec.template.metadata.labels.ECDeployment}") ]]; \
then kubectl patch deployments.apps $depl -p '{"spec":{"template":{"spec":{"readinessGates":null}}}}'; \
fi; \
done

The reason for this is that the custom readiness gate introduced in version 3.0.0 will otherwise block the existing EC Deployments from being fully rolled back.

...