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
Copy file name to clipboardExpand all lines: content/en/docs/deployment/private-cloud/private-cloud-deploy/_index.md
+19-5Lines changed: 19 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -136,16 +136,24 @@ All environments are defined as production environments, which means that [secur
136
136
137
137
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.
138
138
139
-
There are three pre-defined sets of resources, **Small**, **Medium**, and **Large**. Choosing these will set the **CPU** and **Memory** values automatically.
139
+
There are six pre-defined sets of resources, **XS**, **S**, **M**, **L**, **XL**, and **XXL**.
140
+
141
+
Legacy plans are still visible with a **Legacy** prefix.
| Custom | own choice | own choice | own choice | own choice | own choice | own choice |
147
155
148
-
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.
156
+
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.
149
157
150
158
{{% 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 %}}
151
159
@@ -539,6 +547,12 @@ Images are not deleted from the container registry. You should delete those imag
539
547
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.
540
548
{{% /alert %}}
541
549
550
+
##### Custom JVM Heap Memory
551
+
552
+
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/).
[Read-only Root file system](/developerportal/deploy/private-cloud-cluster/#readonlyrootfs) can be enabled per environment. By default, this option is disabled.
0 commit comments