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/releasenotes/deployment/mendix-for-private-cloud.md
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,11 +17,18 @@ For information on the current status of deployment to Mendix for Private Cloud
17
17
#### Mendix Operator v2.21.0 {#2.21.0}
18
18
19
19
* We have switched all system containers to use a read-only root filesystem, and added an option to run Mendix app containers with a read-only rootfs.
20
+
* We have added a default on ephemeral storage usage - to ensure that temporary file storage is reserved and is limited, so that a container gets a guaranteed amount of temporary file storage that cannot be exceeded.
20
21
* We have added a check in `mxpc-cli` to prevent CRD downgrades; starting from `mxpc-cli` version 2.21.0, the installation or upgrade process will keep cluster CRDs unchanged if the cluster has newer CRDs (compared to what is included with the installer).
21
22
* We have updated components to use the latest dependency versions in order to improve security score ratings for container images.
22
23
* We have fixed a _Failed to determine if DDL migration needs approval_ error message that sometimes appeared when using a **Recreate** deployment strategy. This error message doesn't mean there's an issue and can be ignored.
23
24
* Upgrading to Mendix Operator v2.21.0 from a previous version will restart environments managed by that version of the Operator. Environments with 2 or more replicas and a **PreferRolling** update strategy will be restarted without downtime.
24
25
26
+
#### Known Issue
27
+
28
+
With the introduction of ephemeral storage requests and limits, building an app requires at least 2GB of ephemeral storage available on the Kubernetes node.
29
+
If your nodes don't have enough temporary storage, build pods won't be able to start and will stay in a `Pending` phase.
30
+
To resolve this issue, you can lower the valus for `ephemeral-storage` in the [buildResources](/developerportal/deploy/private-cloud-cluster/#resource-definition-ocm) configuration.
0 commit comments