You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -529,7 +529,7 @@ For a *connected* cluster, the top level MendixApp CRD will be deleted from the
529
529
530
530
* 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.
531
531
532
-
{{% 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 %}}
532
+
{{% 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 %}}
533
533
534
534
* Files related to that environment will be deleted from the S3/Minio storage bucket (or prefix if this is using a shared bucket).
535
535
@@ -549,10 +549,10 @@ If any of these garbage collection steps fail, you will no longer see the enviro
549
549
550
550
##### Custom JVM Heap Memory
551
551
552
-
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
552
+
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.
553
553
For more information, see [JVM Memory Tuning for Mendix on Kubernetes](/developerportal/deploy/private-cloud-jvm-memory-tuning/).
Copy file name to clipboardExpand all lines: content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ For information on the current status of deployment to Mendix on Kubernetes and
20
20
* We have aligned resource plans with Public Cloud standards and continue to support legacy plans.
21
21
* Added a warning clarifying that cross-cluster restores are not supported (this limitation already existed) and environments are only visible within the same cluster.
22
22
* We have fixed an issue where replicas with unknown status showed as licensed.
23
-
* We have fixed an issue where scheduled events were missing after pipeline deployment and API updates.(Ticket 270822)
23
+
* We have fixed an issue where scheduled events were missing after pipeline deployment and API updates.(Ticket 270822)
24
24
* 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.
0 commit comments