A fix has been released. Newly built apps on Mendix on Kubernetes and Mendix on Azure start normally again. If an environment failed to start, deploy the app to that environment again. This builds a new image that contains the fix. Restarting the environment is not enough, because a restart reuses the faulty image. Environments that kept running are not affected and do not need any action. You can deploy as usual again. If you pull the Mendix runtime base images through your own registry mirror, sync them again before you redeploy.

A fix has been implemented and we are monitoring the results.

We identified the root cause and prepared a fix. It is currently propagating through our release pipeline.

We are curently investigating the issue. Do not deploy or redeploy running environments until further notice. Restarting environments is safe. Do not downgrade the Operator, downgrading the Operator is unsupported an will not resolve the issue.