Documenation review and restructuring for MxonAzure General Availability #10288
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Nidhi251289
reviewed
Oct 29, 2025
|
|
||
| Yes. For production environments, you must supply runtime licenses for your Mendix apps to move the Mendix Runtime out of trial mode. This licensing process aligns with how Mendix on Kubernetes works (e.g., requesting and applying subscription keys). See [Licensing Apps outside Mendix Cloud](http://localhost:1313/developerportal/deploy/licensing-apps-outside-mxcloud/). | ||
|
|
||
| Note that the Operator license is applied automatically with Mendix on Azure and does not require a separate request. |
Contributor
There was a problem hiding this comment.
Can we remove this. As Operator license is irrelevant now
Contributor
Author
There was a problem hiding this comment.
Yes, last sentence can be removed
Nidhi251289
reviewed
Oct 29, 2025
|
|
||
| The Mendix account that initializes the cluster automatically gains the Cluster Manager role. | ||
|
|
||
| The Mendix on Kubernetes portal lets you add additional cluster managers. These users can view and manage the cluster through both the Mendix on Azure and Mendix on Kubernetes portals, provided they have an Owner or Contributor role on the Azure Managed Application hosting the cluster. |
Contributor
There was a problem hiding this comment.
@MXClyde In my view, only a Admin role(cluster manager added) can view the initialized cluster and not the Contributer.
Contributor
Author
There was a problem hiding this comment.
Cluster Manager on the Mendix side AND Contributor or Owner on the Azure side, in my experience
Contributor
There was a problem hiding this comment.
Ok, I verified this. A Contributer is able to edit the clusters in Azure portal. the changes are applied successfully
| description_list: true | ||
| --- | ||
|
|
||
| ## Introduction |
Nidhi251289
reviewed
Oct 29, 2025
|
|
||
| The Mendix on Kubernetes portal lets you add additional cluster managers. These users can view and manage the cluster through both the Mendix on Azure and Mendix on Kubernetes portals, provided they have an Owner or Contributor role on the Azure Managed Application hosting the cluster. | ||
|
|
||
| Additional cluster managers have the same configuration privileges as the original initializer. They can also view and comment on support tickets related to the cluster via the Mendix on Azure portal but cannot access the full Zendesk ticket. |
Contributor
There was a problem hiding this comment.
@MXClyde We mentioned Configuration privileges. Can we specify that these priviliges are on Mx on Azure portal and Private Cloud portal
| @@ -0,0 +1,101 @@ | |||
| --- | |||
| @@ -1,164 +1,144 @@ | |||
| --- | |||
| title: "Support Policy for Mendix on Azure" | |||
| title: "Support for Mendix on Azure" | |||
| @@ -0,0 +1,138 @@ | |||
| --- | |||
| @@ -0,0 +1,76 @@ | |||
| --- | |||
| @@ -0,0 +1,35 @@ | |||
| --- | |||
| @@ -0,0 +1,64 @@ | |||
| --- | |||
| @@ -0,0 +1,140 @@ | |||
| --- | |||
| * In order to minimize the risk of security breaches and networking issues, we have added a new **Enable AKS Network Isolation** feature when creating new clusters. Please note that this feature can be enabled in the Initialize cluster and Edit cluster flow. However, once enabled in Initialize flow, it cannot be disabled in the Edit Cluster flow. | ||
| * We have improved the log level handling in the Grafana dashboard. The logs are now available in JSON format. | ||
| * We have fixed the issue where the cluster tags were not added to the read replicas database. | ||
| * We have added a new preflight check in Cluster Initialization flow to validate that only one platform account should be used to initialize the cluster. |
| @@ -0,0 +1,33 @@ | |||
| --- | |||
| @@ -0,0 +1,30 @@ | |||
| --- | |||
| @@ -0,0 +1,92 @@ | |||
| --- | |||
| @@ -0,0 +1,52 @@ | |||
| --- | |||
katarzyna-koltun-mx
approved these changes
Oct 29, 2025
Collaborator
katarzyna-koltun-mx
left a comment
katarzyna-koltun-mx
left a comment
There was a problem hiding this comment.
Reviewed and asking for go ahead.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Review and restructuring for General Availability: