Skip to content

Added release notes for Private cloud portal release 7.27.0 #10952

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

Open
mxashokkhedkar wants to merge 3 commits into
base: development
Choose a base branch
from
+12 −0
Open

Added release notes for Private cloud portal release 7.27.0 #10952

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
3bd787b
Added release notes for Private cloud portal release 7.27.0
mxashokkhedkar Mar 31, 2026
780a1a2
Added release notes for Private cloud portal release 7.27.0
mxashokkhedkar Mar 31, 2026
143cd56
Added release notes for Private cloud portal release 7.27.0
mxashokkhedkar Mar 31, 2026
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
12 changes: 12 additions & 0 deletions content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,18 @@ For information on the current status of deployment to Mendix on Kubernetes and

## 2026

### April 2, 2026

#### Portal Improvements

* We have introduced configurable heap memory to align with Public Cloud optimization logic as a default for Operator 2.26.0 and newer.
* We have aligned resource plans with Public Cloud standards and continue to support legacy plans.
* We have moved the Mendix on Azure information banner to the Cluster Manager homepage.
* Cross-cluster restores are not supported. Environments are visible only within the same cluster.
Copy link
Copy Markdown
Collaborator

@MarkvanMents MarkvanMents Mar 31, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this actually new in this release, or are we stating something which has always been the case?

Copy link
Copy Markdown
Contributor Author

@mxashokkhedkar mxashokkhedkar Mar 31, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We had this already, but it was showing environments across the different clusters and if the customer selects environments from different clusters while restoring backup was problematic in some cases so we blocked that now.

Copy link
Copy Markdown
Contributor Author

@mxashokkhedkar mxashokkhedkar Mar 31, 2026 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In case of update .claude/settings.json I am not sure how that appeared, but I can see that it was present in the development branch, as after forking the branch, I got it in my branch as well.
As I already had claude setup which was giving an error in VS code, so I asked it to fix it. Somehow it overwrote my sandbox details in that file.
So I reverted that, that's it.

* We have fixed an issue where replicas with unknown status showed as licensed.
* We have fixed an issue where scheduled events were missing after pipeline deployment.
* We have added context to namespace and clusters invite emails to identify the Mendix on Kubernetes portal as the sender.

### February 25, 2026

#### Mendix Operator v2.26.0 {#2.26.0}
Expand Down