Skip to content

feat: behaviour differences when moving to Public Cloud Kubernetes #10242

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 20, 2025
Merged

feat: behaviour differences when moving to Public Cloud Kubernetes #10242

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
72a6570
feat: behaviour differences when moving to Public Cloud Kubernetes
pommi Oct 17, 2025
355817d
chore: language review
OlufunkeMoronfolu Oct 20, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions content/en/docs/deployment/mendix-cloud-deploy/behavior-of-app.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,3 +58,11 @@ Apps running in Mendix Cloud are subject to certain limitations. These behaviors
Therefore, do not assume that an established WebSocket connection will remain open indefinitely. To ensure connection stability and prevent unexpected disconnections:
* Enable periodic keepalive checks (for example, every 25–30 seconds). This ensures the connection remains active and prevents Network Address Translators (NATs) and firewalls from dropping long-idle tunnels.
* Implement robust reconnection logic to gracefully handle connectivity loss and automatically reestablish dropped connections.

## Move to Kubernetes

* Only [supported Mendix versions](https://docs.mendix.com/releasenotes/studio-pro/lts-mts/) are able to move to Kubernetes.
* The platform configures `CF_INSTANCE_INDEX=0` for 1 of the instances to define a leader instance and to make [Community Commons](/appstore/modules/community-commons-function-library/) function `GetCFInstanceIndex` partially backwards compatible. The leader instance will return `0`. All follower instances will return `-1`. We advise to stop using function `GetCFInstanceIndex` as it is Cloud Foundry specific.
* If your model is using the [SAML module](https://marketplace.mendix.com/link/component/1174), these versions are compatible with Kubernetes:
* Mendix 9 – Version 3.6.19 and higher.
* Mendix 10 – Version 4.1.0 and higher.