Skip to content

Commit ca0b1fa

Browse files
committed
Documented that ephemeral-storage limits might need adjustment after
upgrading. Added default ephemeral-storage values in examples.
1 parent d296412 commit ca0b1fa

2 files changed

Lines changed: 23 additions & 0 deletions

File tree

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

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -439,9 +439,11 @@ spec:
439439
limits:
440440
cpu: 1
441441
memory: 512Mi
442+
ephemeral-storage: 4Mi
442443
requests:
443444
cpu: 100m
444445
memory: 512Mi
446+
ephemeral-storage: 4Mi
445447
# ...
446448
# omitted lines for brevity
447449
# ...
@@ -462,30 +464,38 @@ spec:
462464
limits:
463465
cpu: 250m
464466
memory: 32Mi
467+
ephemeral-storage: 4Mi
465468
requests:
466469
cpu: 100m
467470
memory: 16Mi
471+
ephemeral-storage: 4Mi
468472
metricsSidecarResources:
469473
limits:
470474
cpu: 100m
471475
memory: 32Mi
476+
ephemeral-storage: 4Mi
472477
requests:
473478
cpu: 100m
474479
memory: 16Mi
480+
ephemeral-storage: 4Mi
475481
buildResources:
476482
limits:
477483
cpu: '1'
478484
memory: 256Mi
485+
ephemeral-storage: 2Gi
479486
requests:
480487
cpu: 250m
481488
memory: 64Mi
489+
ephemeral-storage: 2Gi
482490
runtimeResources:
483491
limits:
484492
cpu: 1000m
485493
memory: 512Mi
494+
ephemeral-storage: 256Mi
486495
requests:
487496
cpu: 100m
488497
memory: 512Mi
498+
ephemeral-storage: 256Mi
489499
runtimeLivenessProbe:
490500
initialDelaySeconds: 60
491501
periodSeconds: 15
@@ -629,9 +639,11 @@ resources:
629639
limits:
630640
cpu: 1
631641
memory: 512Mi
642+
ephemeral-storage: 256Mi
632643
requests:
633644
cpu: 100m
634645
memory: 512Mi
646+
ephemeral-storage: 256Mi
635647
```
636648

637649
This section allows the configuration of the lower and upper resource boundaries, the `requests` and `limits` respectively.
@@ -976,16 +988,20 @@ spec:
976988
limits:
977989
cpu: "1"
978990
memory: 256Mi
991+
ephemeral-storage: 2Gi
979992
requests:
980993
cpu: "1"
981994
memory: 256Mi
995+
ephemeral-storage: 2Gi
982996
metricsSidecarResources:
983997
limits:
984998
cpu: 100m
985999
memory: 32Mi
1000+
ephemeral-storage: 4Mi
9861001
requests:
9871002
cpu: 100m
9881003
memory: 32Mi
1004+
ephemeral-storage: 4Mi
9891005
```
9901006

9911007
Run the following command in order to update the core resources in the `OperatorConfiguration`:

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

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,11 +17,18 @@ For information on the current status of deployment to Mendix for Private Cloud
1717
#### Mendix Operator v2.21.0 {#2.21.0}
1818

1919
* 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.
2021
* 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).
2122
* We have updated components to use the latest dependency versions in order to improve security score ratings for container images.
2223
* 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.
2324
* 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.
2425

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.
31+
2532
### February 12, 2025
2633

2734
#### Documentation Updates

0 commit comments

Comments
 (0)