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/deployment/mx-azure/mx-azure-installation.md
+24-6Lines changed: 24 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -60,7 +60,19 @@ To create a cluster for your Mendix on Azure app, perform the following steps:
60
60
61
61
10. Click **Initialize**.
62
62
63
-
The initialization process takes ca. 15 minutes. It creates a resource group in the managed app that you created in step 3 above. Once the cluster is initialized successfully, a corresponding cluster and namespace are created in the the Private Cloud portal. The namespace is also configured automatically, as described in [Standard Operator: Running the Tool](https://docs.mendix.com/developerportal/deploy/standard-operator/#running-the-tool). The cluster cannot be deleted from the Private Cloud portal. If you want to remove it, you must delete it in the Microsoft Azure portal.
63
+
The initialization process takes approximately 15 minutes. It creates a resource group in the managed app that you created in step 3 above. Once the cluster is initialized successfully, a corresponding cluster and namespace are created in the the Private Cloud portal. The namespace is also configured automatically, as described in [Standard Operator: Running the Tool](https://docs.mendix.com/developerportal/deploy/standard-operator/#running-the-tool). The cluster cannot be deleted from the Private Cloud portal or the Mendix on Azure portal. If you want to remove it, you must delete it in the Microsoft Azure portal.
64
+
65
+
## Editing the Cluster in the Mendix on Azure Portal
66
+
67
+
If required, you can change the following options for your cluster:
68
+
69
+
* AKS service tier
70
+
* AKS node size
71
+
* VM type
72
+
* Load balancer type
73
+
* Postgres compute SKU
74
+
* Postgres performance tier for storage IOPS
75
+
* Custom tags
64
76
65
77
## Enabling Connections Between Different Azure Resource Groups
66
78
@@ -99,7 +111,7 @@ To enable virtual network peering for your Mendix on Azure app, perform the foll
99
111
8. If you want to enable connections from your Mendix app to a virtual back-end machine in the other network, perform the following additional steps:
100
112
101
113
1. In the Azure portal, create another private DNS zone for the virtual machine, with auto-registration enabled.
102
-
2. In the **Environment Details** page of your Mendix environment, go to [Model Options](/developerportal/deploy/environments-details/#model-options).
114
+
2. In the Mendix portal, in the **Environment Details** page, go to [Model Options](/developerportal/deploy/environments-details/#model-options).
103
115
3. In the [Constants](/developerportal/deploy/environments-details/#constants) section, find and edit the **RestClient.RestServiceUrl** constant.
104
116
4. In the **New value** field, enter the URL and port of your back-end machine, and then click **Save and Apply**.
105
117
5. In the Azure portal, configure the virtual network link to link the private DNS zone with the virtual network of your managed Mendix application.
@@ -152,14 +164,20 @@ To enable private endpoints for your Mendix on Azure app, perform the following
152
164
4. Create a private endpoint in your Mendix managed resource group.
153
165
5. In the **Resource** tab, specify the following settings:
154
166
155
-
***Resource type** - **privateLinkServices**
156
-
***Resource** - the private link that you created in step 12-b above.
167
+
***Resource type** - **privateLinkServices**
168
+
***Resource** - the private link that you created in step 12-b above.
157
169
158
170
6. In the **Virtual Network** tab, specify the following settings:
159
171
160
-
***Virtual network** - the virtual network managed by Mendix
172
+
***Virtual network** - the virtual network managed by Mendix
173
+
174
+
7. Create a [DNS record](https://learn.microsoft.com/en-us/azure/dns/dns-operations-recordsets-portal) for the IP address of the back-end service's private endpoint.
175
+
8. In the Mendix portal, in the **Environment Details** page, go to [Model Options](/developerportal/deploy/environments-details/#model-options).
176
+
9. In the [Constants](/developerportal/deploy/environments-details/#constants) section, find and edit the **RestClient.RestServiceUrl** constant.
177
+
10. In the **New value** field, enter the URL and port of your back-end machine, and then click **Save and Apply**.
161
178
179
+
Your Mendix app can now connect to a back-end server in the other virtual network.
162
180
163
181
## Deploying an App to an Azure Cluster
164
182
165
-
After creating your cluster in Microsoft Azure, you can deploy now deploy your applications to the cluster. The deployment process is the same as with Mendix for Private Cloud. For more information, see [Deploying a Mendix App to a Private Cloud Cluster](/developerportal/deploy/private-cloud-deploy/).
183
+
After creating your cluster in Microsoft Azure, you can deploy now deploy your applications to the cluster. The deployment process is the same as with Mendix for Private Cloud. For more information, see [Deploying a Mendix App to a Private Cloud Cluster](/developerportal/deploy/private-cloud-deploy/).
0 commit comments