Added release notes for Private cloud portal release 7.27.0

Author: mxashokkhedkar

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

@@ -153,7 +153,7 @@ All environments are defined as production environments, which means that [secur
     | 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 *Legacy 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 %}}
 
@@ -549,7 +549,8 @@ If any of these garbage collection steps fail, you will no longer see the enviro
 
 ##### Custom JVM Heap Memory
 
-You only need to manually adjust JVM memory usage if the default settings aren't fully utilizing available memory. For more information, see [JVM Memory Tuning for Mendix on Kubernetes](/developerportal/deploy/private-cloud-jvm-memory-tuning/).
+You only need to manually adjust JVM memory usage if the default settings aren't 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/ChangeJVMHeapMemory.png" class="no-border" >}}
 

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

@@ -18,11 +18,10 @@ For information on the current status of deployment to Mendix on Kubernetes and
 
 * 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.
-* We have moved the Mendix on Azure information banner to the Cluster Manager homepage.
-* Cross-cluster restores are not supported. Environments are visible only within the same cluster.
+* 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.
-* We have added context to namespace and clusters invite emails to identify the Mendix on Kubernetes portal as the sender.
+* 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