From b36a8bb49f94717dda0700ac611d627bceba6faa Mon Sep 17 00:00:00 2001 From: Dmitrii Zolotukhin Date: Mon, 19 May 2025 14:51:36 +0200 Subject: [PATCH 1/7] DES-6890 Prepared release notes for Mx4PC 2.21.3. --- .../private-cloud/private-cloud-cluster/_index.md | 2 +- .../private-cloud-supported-environments.md | 4 ++-- .../releasenotes/deployment/mendix-for-private-cloud.md | 9 +++++++++ 3 files changed, 12 insertions(+), 3 deletions(-) diff --git a/content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md b/content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md index 787cba343ce..416a0562bd0 100644 --- a/content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md +++ b/content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md @@ -965,7 +965,7 @@ If your app works without issues when read-only root filesystem is enabled, it i {{% /alert %}} {{% alert color="warning" %}} -Enabling the `runtimeReadOnlyRootFilesystem` option causes the `model/resources` directory to be empty. If your app (or a Marketplace module such as SAML) uses the `model/resources` directory for resources such as configuration data, consider moving those resources to another location (for example, `model/userlib`) or loading them from FileDocument entities. +In Mendix Operator versions 2.21.0, 2.21.1 and 2.21.2, enabling the `runtimeReadOnlyRootFilesystem` option causes the `model/resources` directory to be empty. If your app (or a Marketplace module such as SAML) uses the `model/resources` directory for resources such as configuration data, consider upgrading to Mendix Operator 2.21.3 (or a later version), which is not affected by this issue. {{% /alert %}} ### GKE Autopilot Workarounds {#gke-autopilot-workarounds} diff --git a/content/en/docs/deployment/private-cloud/private-cloud-supported-environments.md b/content/en/docs/deployment/private-cloud/private-cloud-supported-environments.md index 075ca6c14a1..5c1684ed932 100644 --- a/content/en/docs/deployment/private-cloud/private-cloud-supported-environments.md +++ b/content/en/docs/deployment/private-cloud/private-cloud-supported-environments.md @@ -36,8 +36,8 @@ If deploying to Red Hat OpenShift, you need to specify that specifically when cr Mendix for Private Cloud Operator `v2.*.*` is the latest version which officially supports: -* Kubernetes versions 1.19 through 1.32 -* OpenShift 4.6 through 4.17 +* Kubernetes versions 1.19 through 1.33 +* OpenShift 4.6 through 4.18 {{% alert color="warning" %}} Kubernetes 1.22 is a [new release](https://kubernetes.io/blog/2021/08/04/kubernetes-1-22-release-announcement/) which removes support for several deprecated APIs and features. 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 5ca29d31b6f..c4207704afb 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,15 @@ For information on the current status of deployment to Mendix for Private Cloud ## 2025 +### May 23, 2025 + +#### Mendix Operator v2.21.3 {#2.21.3} + +* We have addressed an issue with accessing contents of the `model/resources` directory when using the [read-only root filesystem feature](/developerportal/deploy/private-cloud-cluster/#readonlyrootfs). + Starting from this version, the contents of `model/resources` will be available for use by the app (in read-only mode) even when the **Read-Only Root Filesystem** feature is enabled. +* Upgrading to Mendix Operator v2.21.3 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. +* We fixed an issue where an ovelapping `/tmp/mendix/img` path could cause issues with some Marketplace components such as [Azure Application Insights](https://marketplace.mendix.com/link/component/108303) (Ticket 248704). + ### May 08, 2025 #### Portal Improvements From 54d951ddc9f668fdf9dd3123d48212fd2dcbfc0e Mon Sep 17 00:00:00 2001 From: Dmitrii Zolotukhin Date: Tue, 20 May 2025 13:39:22 +0200 Subject: [PATCH 2/7] Added release notes for DES-6886. --- .../releasenotes/deployment/mendix-for-private-cloud.md | 7 ++++++- 1 file changed, 6 insertions(+), 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 c4207704afb..26e607864cd 100644 --- a/content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md +++ b/content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md @@ -14,12 +14,17 @@ For information on the current status of deployment to Mendix for Private Cloud ### May 23, 2025 +#### License Manage CLI v0.10.3 + +* We've added support for uploading license bundles with an extended license expiration date (Ticket 249344). + #### Mendix Operator v2.21.3 {#2.21.3} * We have addressed an issue with accessing contents of the `model/resources` directory when using the [read-only root filesystem feature](/developerportal/deploy/private-cloud-cluster/#readonlyrootfs). Starting from this version, the contents of `model/resources` will be available for use by the app (in read-only mode) even when the **Read-Only Root Filesystem** feature is enabled. -* Upgrading to Mendix Operator v2.21.3 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. * We fixed an issue where an ovelapping `/tmp/mendix/img` path could cause issues with some Marketplace components such as [Azure Application Insights](https://marketplace.mendix.com/link/component/108303) (Ticket 248704). +* We've added support for updating license expiration dates when a newer license is available in PCLM (Ticket 249344). +* Upgrading to Mendix Operator v2.21.3 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. ### May 08, 2025 From 4374d2653dac10d7a4ea88537d60a48c50e73345 Mon Sep 17 00:00:00 2001 From: Dmitrii Zolotukhin Date: Wed, 21 May 2025 18:03:40 +0200 Subject: [PATCH 3/7] Removed references to DES-6777. --- .../deployment/private-cloud/private-cloud-cluster/_index.md | 2 +- .../en/docs/releasenotes/deployment/mendix-for-private-cloud.md | 2 -- 2 files changed, 1 insertion(+), 3 deletions(-) diff --git a/content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md b/content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md index 416a0562bd0..787cba343ce 100644 --- a/content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md +++ b/content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md @@ -965,7 +965,7 @@ If your app works without issues when read-only root filesystem is enabled, it i {{% /alert %}} {{% alert color="warning" %}} -In Mendix Operator versions 2.21.0, 2.21.1 and 2.21.2, enabling the `runtimeReadOnlyRootFilesystem` option causes the `model/resources` directory to be empty. If your app (or a Marketplace module such as SAML) uses the `model/resources` directory for resources such as configuration data, consider upgrading to Mendix Operator 2.21.3 (or a later version), which is not affected by this issue. +Enabling the `runtimeReadOnlyRootFilesystem` option causes the `model/resources` directory to be empty. If your app (or a Marketplace module such as SAML) uses the `model/resources` directory for resources such as configuration data, consider moving those resources to another location (for example, `model/userlib`) or loading them from FileDocument entities. {{% /alert %}} ### GKE Autopilot Workarounds {#gke-autopilot-workarounds} 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 26e607864cd..2c5be383033 100644 --- a/content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md +++ b/content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md @@ -20,8 +20,6 @@ For information on the current status of deployment to Mendix for Private Cloud #### Mendix Operator v2.21.3 {#2.21.3} -* We have addressed an issue with accessing contents of the `model/resources` directory when using the [read-only root filesystem feature](/developerportal/deploy/private-cloud-cluster/#readonlyrootfs). - Starting from this version, the contents of `model/resources` will be available for use by the app (in read-only mode) even when the **Read-Only Root Filesystem** feature is enabled. * We fixed an issue where an ovelapping `/tmp/mendix/img` path could cause issues with some Marketplace components such as [Azure Application Insights](https://marketplace.mendix.com/link/component/108303) (Ticket 248704). * We've added support for updating license expiration dates when a newer license is available in PCLM (Ticket 249344). * Upgrading to Mendix Operator v2.21.3 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. From 79ba36cae5120910be876ca4044a4d460a6b93a2 Mon Sep 17 00:00:00 2001 From: Dmitrii Zolotukhin Date: Fri, 23 May 2025 10:31:29 +0200 Subject: [PATCH 4/7] Added a note that upgrading Mx4PC & PCLM is highly recommended. --- .../deployment/private-cloud/private-cloud-license-manager.md | 2 ++ .../docs/releasenotes/deployment/mendix-for-private-cloud.md | 3 +++ 2 files changed, 5 insertions(+) diff --git a/content/en/docs/deployment/private-cloud/private-cloud-license-manager.md b/content/en/docs/deployment/private-cloud/private-cloud-license-manager.md index 1a4c56b2387..bb5a5076dfb 100644 --- a/content/en/docs/deployment/private-cloud/private-cloud-license-manager.md +++ b/content/en/docs/deployment/private-cloud/private-cloud-license-manager.md @@ -9,6 +9,8 @@ beta: true {{% alert color="warning" %}} Private Cloud License Manager is currently in beta. For more information, see [Beta Releases](/releasenotes/beta-features/). + +We highly recommend to upgrade to the latest available version, as newer versions contain bugfixes and improvements to ensure that all apps get a valid, non-expired license. {{% /alert %}} ## Introduction 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 2c5be383033..08f0ca5e5a7 100644 --- a/content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md +++ b/content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md @@ -14,6 +14,9 @@ For information on the current status of deployment to Mendix for Private Cloud ### May 23, 2025 +In today's release, we've addressed an issue with updating expired licenses in PCLM and the Mendix Operator. +If you're using the Mendix Operator with PCLM, it's **highly recommended** to upgrade Mendix Operator to version 2.21.3 (or later) and PCLM to version 0.10.3 (or later). + #### License Manage CLI v0.10.3 * We've added support for uploading license bundles with an extended license expiration date (Ticket 249344). From 602a85f98d0d114796cd24624337466c5ce53d1b Mon Sep 17 00:00:00 2001 From: Mark van Ments Date: Fri, 23 May 2025 11:25:01 +0200 Subject: [PATCH 5/7] Proofread --- .../private-cloud/private-cloud-license-manager.md | 2 +- .../deployment/mendix-for-private-cloud.md | 13 ++++++++----- 2 files changed, 9 insertions(+), 6 deletions(-) diff --git a/content/en/docs/deployment/private-cloud/private-cloud-license-manager.md b/content/en/docs/deployment/private-cloud/private-cloud-license-manager.md index bb5a5076dfb..22ff9714c87 100644 --- a/content/en/docs/deployment/private-cloud/private-cloud-license-manager.md +++ b/content/en/docs/deployment/private-cloud/private-cloud-license-manager.md @@ -10,7 +10,7 @@ beta: true {{% alert color="warning" %}} Private Cloud License Manager is currently in beta. For more information, see [Beta Releases](/releasenotes/beta-features/). -We highly recommend to upgrade to the latest available version, as newer versions contain bugfixes and improvements to ensure that all apps get a valid, non-expired license. +Mendix highly recommends that you upgrade to the latest available version to ensure that all apps get a valid, non-expired license. Newer versions contain bugfixes and improvements. {{% /alert %}} ## Introduction 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 08f0ca5e5a7..d5ea0cb8239 100644 --- a/content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md +++ b/content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md @@ -14,17 +14,20 @@ For information on the current status of deployment to Mendix for Private Cloud ### May 23, 2025 -In today's release, we've addressed an issue with updating expired licenses in PCLM and the Mendix Operator. -If you're using the Mendix Operator with PCLM, it's **highly recommended** to upgrade Mendix Operator to version 2.21.3 (or later) and PCLM to version 0.10.3 (or later). +#### Fixes + +* We addressed an issue with updating expired licenses in PCLM and the Mendix Operator. + + If you are using the Mendix Operator with PCLM, it is **highly recommended** that you upgrade Mendix Operator to version 2.21.3 or above and PCLM to version 0.10.3 or above. #### License Manage CLI v0.10.3 -* We've added support for uploading license bundles with an extended license expiration date (Ticket 249344). +* We added support for uploading license bundles with an extended license expiration date. (Ticket 249344) #### Mendix Operator v2.21.3 {#2.21.3} -* We fixed an issue where an ovelapping `/tmp/mendix/img` path could cause issues with some Marketplace components such as [Azure Application Insights](https://marketplace.mendix.com/link/component/108303) (Ticket 248704). -* We've added support for updating license expiration dates when a newer license is available in PCLM (Ticket 249344). +* We fixed an issue where an overlapping `/tmp/mendix/img` path could cause issues with some Marketplace components, for example [Azure Application Insights](https://marketplace.mendix.com/link/component/108303). (Ticket 248704) +* We added support for updating license expiration dates when a newer license is available in PCLM. (Ticket 249344) * Upgrading to Mendix Operator v2.21.3 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. ### May 08, 2025 From 9e0dc9975ac8fe7c073ff8e27dd3055c394eabb1 Mon Sep 17 00:00:00 2001 From: Mark van Ments Date: Fri, 23 May 2025 11:31:38 +0200 Subject: [PATCH 6/7] Proofread --- .../docs/releasenotes/deployment/mendix-for-private-cloud.md | 4 ++-- 1 file changed, 2 insertions(+), 2 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 d5ea0cb8239..92219ca4d3e 100644 --- a/content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md +++ b/content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md @@ -172,7 +172,7 @@ This issue has been fixed in Mendix Operator [version 2.21.1](#2.21.1). #### Mendix Operator v2.20.1 {#2.20.1} * We have updated the m2ee-sidecar lifecycle to no longer stop the Mendix Runtime if a `ping` times out or fails; an app will now only be restarted by the liveness probe (Ticket 230648). -* We have adjusted AWS STS token expiration for envrionments using IRSA, which should prevent occasional *SQLState: 28000 Error code: 0 Message: "FATAL: PAM authentication failed for user …", retrying...(1/4)* errors (Ticket 234454). +* We have adjusted AWS STS token expiration for environments using IRSA, which should prevent occasional *SQLState: 28000 Error code: 0 Message: "FATAL: PAM authentication failed for user …", retrying...(1/4)* errors (Ticket 234454). * We have switched the log format to JSON for the `build`, `database` and `file` pods, to help with parsing the logs and automatically assigning log levels and timestamps. * We have updated a library used to validate licenses to the latest non-alpha version. * We have updated documentation that OpenShift 4.17 and Postgres 17 are supported by the Mendix Operator. @@ -183,7 +183,7 @@ This issue has been fixed in Mendix Operator [version 2.21.1](#2.21.1). At present, a Technical Contact can only be assigned to one application at a time instead of multiple applications. If an individual who is already a Technical Contact for an existing application creates another application, they are automatically assigned as the Technical Contact for the new application. However, this results in their removal as the Technical Contact for the previous application. -Additionally, being assigned as a Technical Contact grants the individual administrator-level access across all namespaces where environments are created. Consequently, in this scenario, the individual gaina administrator access to the namespaces for both applications with created environments. +Additionally, being assigned as a Technical Contact grants the individual administrator-level access across all namespaces where environments are created. Consequently, in this scenario, the individual grants administrator access to the namespaces for both applications with created environments. We are working on a fix, which is expected to be available in next release. Once the fix is available, make sure to check your applications and assign the Technical Contact accordingly. From 3a58b5133807a613d53b6d294240d5c3d233ee13 Mon Sep 17 00:00:00 2001 From: Mark van Ments Date: Fri, 23 May 2025 11:35:42 +0200 Subject: [PATCH 7/7] Update the refresh release note to be clearer. --- .../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 92219ca4d3e..74d8ccac0d3 100644 --- a/content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md +++ b/content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md @@ -27,7 +27,7 @@ For information on the current status of deployment to Mendix for Private Cloud #### Mendix Operator v2.21.3 {#2.21.3} * We fixed an issue where an overlapping `/tmp/mendix/img` path could cause issues with some Marketplace components, for example [Azure Application Insights](https://marketplace.mendix.com/link/component/108303). (Ticket 248704) -* We added support for updating license expiration dates when a newer license is available in PCLM. (Ticket 249344) +* We updated the license refresh mechanism to automatically refresh expired licenses from PCLM. (Ticket 249344) * Upgrading to Mendix Operator v2.21.3 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. ### May 08, 2025