Merge pull request mendix#10952 from mxashokkhedkar/portuns_release_7_27_0

Added release notes for Private cloud portal release 7.27.0

Author: Karuna-Mendix

content/en/docs/deployment/private-cloud/private-cloud-deploy/_index.md

@@ -130,22 +130,30 @@ All environments are defined as production environments, which means that [secur
 
 8. Click **Next**.
 
-    {{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/configureEnvResources.png" class="no-border" >}}
+    {{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/configure-env-resources.png" class="no-border" >}}
 
 9. Select **Core Resources**.
 
     For core resources, there are two sets of values. The **Request** value is the amount of core resources which are initially requested. The **Limit** value is the maximum amount of resource that the environment can use.
 
-    There are three pre-defined sets of resources, **Small**, **Medium**, and **Large**. Choosing these will set the **CPU** and **Memory** values automatically.
+    There are six pre-defined sets of resources, **XS**, **S**, **M**, **L**, **XL**, and **XXL**.
+
+    Legacy plans are still visible with a **Legacy** prefix.
 
     | **Name** | **CPU cores**: Limit | **Memory (GB)**: Limit | **Ephemeral Storage (GB)**: Limit | **CPU cores**: Request | **Memory (GB)**: Request | **Ephemeral Storage (GB)**: Request |
     | --- | --- | --- | --- | --- | --- | --- |
-    | Small | 1 | 0.5 | 1 | 0.1 | 0.5 | 1 |
-    | Medium | 2 | 2 | 1 | 1 | 1 | 1 |
-    | Large | 4 | 4 | 1 | 2 | 2 | 1 |
+    | XS | 0.25 | 1 | 1 | 0.25 | 1 | 1 |
+    | S | 0.5 | 2 | 1 | 0.5 | 2 | 1 |
+    | M | 1 | 4 | 1 | 1 | 4 | 1 |
+    | L | 2 | 8 | 1 | 2 | 8 | 1 |
+    | XL | 4 | 16 | 1 | 4 | 16 | 1 |
+    | XXL | 8 | 32 | 1 | 4 | 32 | 1 |
+    | Legacy Small | 1 | 0.5 | 1 | 0.1 | 0.5 | 1 |
+    | Legacy Medium | 2 | 2 | 1 | 1 | 1 | 1 |
+    | Legacy Large | 4 | 4 | 1 | 2 | 2 | 1 |
     | Custom | own choice | own choice | own choice | own choice | own choice | own choice |
 
-    Alternatively, you can choose **Custom**, and enter your own requirements for **CPU** and **Memory**. Ensure that these values are the same or greater than the values for a *Small* environment, otherwise you may run into problems running your app.
+    Alternatively, you can choose **Custom**, and enter your own requirements for **CPU** and **Memory**. Ensure that these values are the same or greater than the values for a *Legacy Small* environment, otherwise you may run into problems running your app. Existing environments will continue to utilize their legacy resources.
 
     {{% alert color="info" %}}If the cluster manager has added and enabled customized core resource plan on Cluster manager page, only the configured custom core resource plans will be visible for selection. Once the custom core resources plans are enabled, environments cannot be created using the default plans until all the associated environments using the custom core resource plan are deleted and the custom resource plan is disabled on the **Cluster manager** page.{{% /alert %}}
 
@@ -521,7 +529,7 @@ For a *connected* cluster, the top level MendixApp CRD will be deleted from the
 
 * The database will be dropped and the database user will be deleted from the database server — databases and users from other environments will remain untouched.
 
-    {{% alert color="info" %}}If the storage plan is using a JDBC plan (not Postgres or SQL Server), the database and the user will remain untouched).{{% /alert %}}
+    {{% alert color="info" %}}If the storage plan is using a JDBC plan (not Postgres or SQL Server), the database and the user will remain untouched.{{% /alert %}}
 
 * Files related to that environment will be deleted from the S3/Minio storage bucket (or prefix if this is using a shared bucket).
 
@@ -539,6 +547,13 @@ Images are not deleted from the container registry. You should delete those imag
 If any of these garbage collection steps fail, you will no longer see the environment in the Mendix Portal, and will have to [delete the storage instances](#delete-storage) manually.
 {{% /alert %}}
 
+##### Custom JVM Heap Memory
+
+Adjust the JVM memory usage manually if the default settings are not fully utilizing available memory. The JVM's memory usage must always remain below the total core resource memory to prevent application crashloops.
+For more information, see [JVM Memory Tuning for Mendix on Kubernetes](/developerportal/deploy/private-cloud-jvm-memory-tuning/).
+
+{{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/change-jvm-heapmemory.png" class="no-border" >}}
+
 ##### Read-Only Root Filesystem
 
 [Read-only Root file system](/developerportal/deploy/private-cloud-cluster/#readonlyrootfs) can be enabled per environment. By default, this option is disabled. 

content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md

@@ -12,6 +12,17 @@ For information on the current status of deployment to Mendix on Kubernetes and
 
 ## 2026
 
+### April 2, 2026
+
+#### Portal Improvements
+
+* We have introduced configurable heap memory to align with Public Cloud optimization logic as a default for Operator 2.26.0 and newer.
+* We have aligned resource plans with Public Cloud standards and continue to support legacy plans.
+* Added a warning clarifying that cross-cluster restores are not supported (this limitation already existed) and environments are only visible within the same cluster.
+* We have fixed an issue where replicas with unknown status showed as licensed.
+* We have fixed an issue where scheduled events were missing after pipeline deployment and API updates. (Ticket 270822)
+* We enhanced namespace and cluster invite emails to clearly identify the Mendix on Kubernetes portal as the sender, and updated the email notification messages accordingly.
+
 ### February 25, 2026
 
 #### Mendix Operator v2.26.0 {#2.26.0}