From a8681a3645c86646da01e08845449fd9b20e87d0 Mon Sep 17 00:00:00 2001 From: Dmitrii Zolotukhin Date: Tue, 1 Apr 2025 11:11:20 +0200 Subject: [PATCH 1/5] Added release notes for mx4pc 2.21.2 and pclm 0.10.2. Added a note about needing Mendix 10.20 to address RUN-4429. --- .../reduced-downtime-deployment.md | 2 ++ .../deployment/mendix-for-private-cloud.md | 21 +++++++++++++++---- 2 files changed, 19 insertions(+), 4 deletions(-) diff --git a/content/en/docs/deployment/private-cloud/reduced-downtime-deployment.md b/content/en/docs/deployment/private-cloud/reduced-downtime-deployment.md index d69e2fe6653..115c385ccd2 100644 --- a/content/en/docs/deployment/private-cloud/reduced-downtime-deployment.md +++ b/content/en/docs/deployment/private-cloud/reduced-downtime-deployment.md @@ -116,3 +116,5 @@ spec: * If the new app version has UI changes, all clients are automatically logged out and will need to sign back into the app. * Deploying a new version of the app will cause downtime if there are changes in the domain model, or the Mendix version. * If an app is based on Mendix 9.12 or a later version, a Rolling update can run scheduled events on any replica. During an update, scheduled events might use a newer or older version of their associated microflows, which will be random. If there are major changes in a scheduled event microflow, consider temporarily disabling scheduled events during an update. +* Using Mendix 10.20 or later is highly recommended to ensure scheduled events [are correctly synchronized at startup](/releasenotes/studio-pro/10.20/#improvements). + diff --git a/content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md b/content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md index a97261523dc..c6d9065be9d 100644 --- a/content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md +++ b/content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md @@ -12,6 +12,19 @@ For information on the current status of deployment to Mendix for Private Cloud ## 2025 +### April ???, 2025 + +#### Mendix Operator v2.21.2 {#2.21.2} + +* We have updated components to use the latest dependency versions in order to improve security score ratings for container images. +* We have fixed a regression that caused the `mendix-operator` pod to crashloop after running the base installation in a new namespace. +* We have fixed an issue in the connection retry mechanism for the image builder and storage provisioners: when a retryable action failed for 63 times in a row, any following retry attempts would no longer wait for a delay. In this update, all retry attempts will wait for a variable, random delay regardless of the number of retry attempts. +* Upgrading to Mendix Operator v2.21.2 from a previous version now restarts environments managed by that version of the Operator. Environments with 2 or more replicas and a **PreferRolling** update strategy are restarted without downtime. + +#### License Manager CLI v0.10.2 + +* We have updated this component to use the latest dependency versions in order to improve security score ratings for container images. + ### March 20, 2025 #### Portal Improvements @@ -26,7 +39,7 @@ For information on the current status of deployment to Mendix for Private Cloud ### March 10, 2025 -#### License Manage CLI v0.10.1 +#### License Manager CLI v0.10.1 * We have updated this component to use the latest dependency versions in order to improve security score ratings for container images. This update will allow us to address CVE-2024-45337 and CVE-2024-45338. @@ -35,9 +48,9 @@ For information on the current status of deployment to Mendix for Private Cloud * We have updated components to use the latest dependency versions in order to improve security score ratings for container images. * For new installations, the Operator now uses ubi9 as the base image for Mendix apps. Existing installations will keep their configuration and stay on ubi8. For more information on base image versions, see the [Runtime Base Image](/developerportal/deploy/private-cloud-cluster/#runtime-base-image) section. * We have fixed a regression that caused the `model/resources` directory to appear empty and caused problems with some Marketplace modules, such as SAML (Ticket 242648). -* Upgrading to Mendix Operator v2.21.0 from a previous version now restarts environments managed by that version of the Operator. Environments with 2 or more replicas and a **PreferRolling** update strategy are restarted without downtime. +* Upgrading to Mendix Operator v2.21.1 from a previous version now restarts environments managed by that version of the Operator. Environments with 2 or more replicas and a **PreferRolling** update strategy are restarted without downtime. -##### Known Issues +##### Known Issue After completing the base installation, the Operator pod may enter a crash loop, reporting a missing endpoint. @@ -64,7 +77,7 @@ For the Global Operator, follow these steps to resolve the issue: type: service ``` -We are working on a patch which will resolve the crash loop issue. +This issue is addressed in Mendix Operator version 2.21.2. ### March 6, 2025 From a65522475fa90de4079d49280a1248846cfdb8ed Mon Sep 17 00:00:00 2001 From: Dmitrii Zolotukhin Date: Tue, 1 Apr 2025 11:37:09 +0200 Subject: [PATCH 2/5] Added ticket number for DES-6812. --- .../en/docs/releasenotes/deployment/mendix-for-private-cloud.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md b/content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md index c6d9065be9d..5f6ec3bb873 100644 --- a/content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md +++ b/content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md @@ -17,7 +17,7 @@ For information on the current status of deployment to Mendix for Private Cloud #### Mendix Operator v2.21.2 {#2.21.2} * We have updated components to use the latest dependency versions in order to improve security score ratings for container images. -* We have fixed a regression that caused the `mendix-operator` pod to crashloop after running the base installation in a new namespace. +* We have fixed a regression that caused the `mendix-operator` pod to crashloop after running the base installation in a new namespace (Ticket 244619). * We have fixed an issue in the connection retry mechanism for the image builder and storage provisioners: when a retryable action failed for 63 times in a row, any following retry attempts would no longer wait for a delay. In this update, all retry attempts will wait for a variable, random delay regardless of the number of retry attempts. * Upgrading to Mendix Operator v2.21.2 from a previous version now restarts environments managed by that version of the Operator. Environments with 2 or more replicas and a **PreferRolling** update strategy are restarted without downtime. From 5ce26398d217203b6f16c6527722ae29cea7e51e Mon Sep 17 00:00:00 2001 From: katarzyna-koltun-mx <108737161+katarzyna-koltun-mx@users.noreply.github.com> Date: Wed, 2 Apr 2025 13:15:25 +0200 Subject: [PATCH 3/5] Update reduced-downtime-deployment.md --- .../deployment/private-cloud/reduced-downtime-deployment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/deployment/private-cloud/reduced-downtime-deployment.md b/content/en/docs/deployment/private-cloud/reduced-downtime-deployment.md index 115c385ccd2..44add1a2bb5 100644 --- a/content/en/docs/deployment/private-cloud/reduced-downtime-deployment.md +++ b/content/en/docs/deployment/private-cloud/reduced-downtime-deployment.md @@ -116,5 +116,5 @@ spec: * If the new app version has UI changes, all clients are automatically logged out and will need to sign back into the app. * Deploying a new version of the app will cause downtime if there are changes in the domain model, or the Mendix version. * If an app is based on Mendix 9.12 or a later version, a Rolling update can run scheduled events on any replica. During an update, scheduled events might use a newer or older version of their associated microflows, which will be random. If there are major changes in a scheduled event microflow, consider temporarily disabling scheduled events during an update. -* Using Mendix 10.20 or later is highly recommended to ensure scheduled events [are correctly synchronized at startup](/releasenotes/studio-pro/10.20/#improvements). +* To ensure that scheduled events [are correctly synchronized at startup](/releasenotes/studio-pro/10.20/#improvements), it is recommended to use Mendix 10.20 or later. From 8aa5b13baa5d1a0c6cca0ba8c892223a88eac7fe Mon Sep 17 00:00:00 2001 From: katarzyna-koltun-mx <108737161+katarzyna-koltun-mx@users.noreply.github.com> Date: Wed, 2 Apr 2025 13:16:28 +0200 Subject: [PATCH 4/5] Update mendix-for-private-cloud.md --- .../releasenotes/deployment/mendix-for-private-cloud.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md b/content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md index 5f6ec3bb873..3067fe45a95 100644 --- a/content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md +++ b/content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md @@ -12,14 +12,14 @@ For information on the current status of deployment to Mendix for Private Cloud ## 2025 -### April ???, 2025 +### April 03, 2025 #### Mendix Operator v2.21.2 {#2.21.2} * We have updated components to use the latest dependency versions in order to improve security score ratings for container images. -* We have fixed a regression that caused the `mendix-operator` pod to crashloop after running the base installation in a new namespace (Ticket 244619). -* We have fixed an issue in the connection retry mechanism for the image builder and storage provisioners: when a retryable action failed for 63 times in a row, any following retry attempts would no longer wait for a delay. In this update, all retry attempts will wait for a variable, random delay regardless of the number of retry attempts. -* Upgrading to Mendix Operator v2.21.2 from a previous version now restarts environments managed by that version of the Operator. Environments with 2 or more replicas and a **PreferRolling** update strategy are restarted without downtime. +* We have fixed a regression that caused the `mendix-operator` pod to enter a crash loop after running the base installation in a new namespace (Ticket 244619). +* We have fixed an issue in the connection retry mechanism for the image builder and storage provisioners. Previously, when a retryable action failed for 63 times in a row, any following retry attempts would no longer wait for a delay. In this update, all retry attempts will wait for a variable, random delay regardless of the number of retry attempts. +* Upgrading to Mendix Operator v2.21.2 from a previous version now restarts environments managed by that version of the Operator. Environments with two or more replicas and a **PreferRolling** update strategy are restarted without downtime. #### License Manager CLI v0.10.2 From bef3bcc4efe26e48b2bf6103320033b76aeecad6 Mon Sep 17 00:00:00 2001 From: katarzyna-koltun-mx <108737161+katarzyna-koltun-mx@users.noreply.github.com> Date: Tue, 8 Apr 2025 13:20:50 +0200 Subject: [PATCH 5/5] Update mendix-for-private-cloud.md --- .../en/docs/releasenotes/deployment/mendix-for-private-cloud.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md b/content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md index 3067fe45a95..3a7707b3686 100644 --- a/content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md +++ b/content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md @@ -39,7 +39,7 @@ For information on the current status of deployment to Mendix for Private Cloud ### March 10, 2025 -#### License Manager CLI v0.10.1 +#### License Manager CLI v0.10.1 {#license-manage-cli-v0101} * We have updated this component to use the latest dependency versions in order to improve security score ratings for container images. This update will allow us to address CVE-2024-45337 and CVE-2024-45338.