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.

...

If you use the bundled ingress controller, i.e. setting helm value nginx.enabled=true, it should be noted that this is was deprecated a while back and will not work in Kubernetes v1.22 or later. Reason being that it relates to API:s that are removed in Kubernetes v1.22.To enable an ingress nginx controller compatible with Kubernetes v1.19 - v1.22, please set nginx.enabled=false and instead ingress-nginx-v4=true.
This will enable ingress-nginx as a sub-chart. For documentation of ingress-nginx, please refer to: https://github.com/kubernetes/ingress-nginx

The solution to this is to install the Ingress NGIX controller helm chart separately.