The following provides important information related to Usage Engine 2.0:
If you use the bundled ingress controller, i.e. setting helm value nginx.enabled=true, it should be noted that this is deprecated 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
If you want to upgrade to Usage Engine 2.0 from MediationZone 10.x, you need to be on a 10.6.x version.
In the upgrade scenario where the CRD already exist in the K8s cluster, a manual step prior to executing the helm upgrade command is required.
Once that information has been obtained, the following kubectl commands should be executed (note that you will need to replace “my-mz” and “my-mz-namespace” with whatever name and namespace you have in your environment):
This will effectively mean that the CRD is now owned by the existing MZ helm installation. Now the helm upgrade command can be executed as per the normal procedure.
This manual step is only required once. Any subsequent upgrades can be executed without this manual step.
If the manual step outlined above is not carried out, an error message like this will typically be returned when executing the helm upgrade command: