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: articles/application-gateway/for-containers/alb-controller-release-notes.md
+9-3Lines changed: 9 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,11 +31,17 @@ Instructions for new or existing deployments of ALB Controller are found in the
31
31
32
32
## Release history
33
33
34
-
0.6.3 - Hotfix to address handling of AGC frontends during controller restart in managed scenario
34
+
January 23, 2024 - 0.7.2
35
35
36
-
0.6.2 - Skipped
36
+
January 11, 2024 - 0.6.6
37
37
38
-
November 6, 2023 - 0.6.1 - Gateway / Ingress API - Header rewrite support, Ingress API - URL rewrite support, Ingress multiple-TLS listener bug fix,
38
+
December 14, 2023 - 0.6.4
39
+
40
+
December 5, 2023 - 0.6.3 - Hotfix to address handling of AGC frontends during controller restart in managed scenario
41
+
42
+
November 2, 2023 - 0.6.24971
43
+
44
+
November 3, 2023 - 0.6.1 - Gateway / Ingress API - Header rewrite support, Ingress API - URL rewrite support, Ingress multiple-TLS listener bug fix,
39
45
two certificates maximum per host, adopting [semantic versioning (semver)](https://semver.org/), quality improvements
40
46
41
47
September 25, 2023 - 0.5.024542 - Custom Health Probes, Controller HA, Multi-site support for Ingress, [helm_release via Terraform fix](https://github.com/Azure/AKS/issues/3857), Path rewrite for Gateway API, status for Ingress resources, quality improvements
Copy file name to clipboardExpand all lines: articles/application-gateway/quick-create-portal.md
+32-16Lines changed: 32 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ Sign in to the [Azure portal](https://portal.azure.com) with your Azure account.
29
29
30
30
## Create an application gateway
31
31
32
-
You'll create the application gateway using the tabs on the **Create application gateway** page.
32
+
Create the application gateway using the tabs on the **Create application gateway** page.
33
33
34
34
1. On the Azure portal menu or from the **Home** page, select **Create a resource**.
35
35
2. Under **Categories**, select **Networking** and then select **Application Gateway** in the **Popular Azure services** list.
@@ -40,8 +40,9 @@ You'll create the application gateway using the tabs on the **Create application
40
40
41
41
-**Resource group**: Select **myResourceGroupAG** for the resource group. If it doesn't exist, select **Create new** to create it.
42
42
-**Application gateway name**: Enter *myAppGateway* for the name of the application gateway.
43
+
- Use the default selections for other settings.
43
44
44
-

45
+

45
46
46
47
2. For Azure to communicate between the resources that you create, a virtual network is needed. You can either create a new virtual network or use an existing one. In this example, you'll create a new virtual network at the same time that you create the application gateway. Application Gateway instances are created in separate subnets. You create two subnets in this example: One for the application gateway, and another for the backend servers.
47
48
@@ -53,16 +54,12 @@ You'll create the application gateway using the tabs on the **Create application
53
54
-**Name**: Enter *myVNet* for the name of the virtual network.
54
55
55
56
-**Subnet name** (Application Gateway subnet): The **Subnets** grid will show a subnet named *default*. Change the name of this subnet to *myAGSubnet*.<br>The application gateway subnet can contain only application gateways. No other resources are allowed. The default IP address range provided is 10.0.0.0/24.
56
-
57
-
-**Subnet name** (backend server subnet): In the second row of the **Subnets** grid, enter *myBackendSubnet* in the **Subnet name** column.
58
57
59
-
-**Address range** (backend server subnet): In the second row of the **Subnets** Grid, enter an address range that doesn't overlap with the address range of *myAGSubnet*. For example, if the address range of *myAGSubnet* is 10.0.0.0/24, enter *10.0.1.0/24* for the address range of *myBackendSubnet*.
58
+

60
59
61
60
Select **OK** to close the **Create virtual network** window and save the virtual network settings.
62
-
63
-

64
61
65
-
3.On the **Basics** tab, accept the default values for the other settings and then select**Next: Frontends**.
62
+
3. Select**Next: Frontends**.
66
63
67
64
### Frontends tab
68
65
@@ -72,7 +69,7 @@ You'll create the application gateway using the tabs on the **Create application
72
69
73
70
2. Select **Add new** for the **Public IP address** and enter *myAGPublicIPAddress* for the public IP address name, and then select **OK**.
74
71
75
-

72
+

76
73
77
74
> [!NOTE]
78
75
> Application Gateway frontend now supports dual-stack IP addresses (Public Preview). You can now create up to four frontend IP addresses: Two IPv4 addresses (public and private) and two IPv6 addresses (public and private).
@@ -93,7 +90,7 @@ The backend pool is used to route requests to the backend servers that serve the
93
90
94
91
3. In the **Add a backend pool** window, select **Add** to save the backend pool configuration and return to the **Backends** tab.
95
92
96
-

93
+

97
94
98
95
4. On the **Backends** tab, select **Next: Configuration**.
99
96
@@ -115,33 +112,52 @@ On the **Configuration** tab, you'll connect the frontend and backend pool you c
115
112
116
113
Accept the default values for the other settings on the **Listener** tab, then select the **Backend targets** tab to configure the rest of the routing rule.
117
114
118
-

115
+

119
116
120
117
4. On the **Backend targets** tab, select **myBackendPool** for the **Backend target**.
121
118
122
119
5. For the **Backend setting**, select **Add new** to add a new Backend setting. The Backend setting will determine the behavior of the routing rule. In the **Add Backend setting** window that opens, enter *myBackendSetting* for the **Backend settings name** and *80* for the **Backend port**. Accept the default values for the other settings in the **Add Backend setting** window, then select **Add** to return to the **Add a routing rule** window.
123
120
124
-

121
+

125
122
126
123
6. On the **Add a routing rule** window, select **Add** to save the routing rule and return to the **Configuration** tab.
127
124
128
-

125
+

129
126
130
127
7. Select **Next: Tags** and then **Next: Review + create**.
131
128
132
129
### Review + create tab
133
130
134
131
Review the settings on the **Review + create** tab, and then select **Create** to create the virtual network, the public IP address, and the application gateway. It can take several minutes for Azure to create the application gateway. Wait until the deployment finishes successfully before moving on to the next section.
135
132
133
+

134
+
136
135
## Add backend targets
137
136
138
137
In this example, you'll use virtual machines as the target backend. You can either use existing virtual machines or create new ones. You'll create two virtual machines as backend servers for the application gateway.
139
138
140
139
To do this, you'll:
141
140
142
-
1. Create two new VMs, *myVM* and *myVM2*, to be used as backend servers.
143
-
2. Install IIS on the virtual machines to verify that the application gateway was created successfully.
144
-
3. Add the backend servers to the backend pool.
141
+
1. Add a backend subnet.
142
+
2. Create two new VMs, *myVM* and *myVM2*, to be used as backend servers.
143
+
3. Install IIS on the virtual machines to verify that the application gateway was created successfully.
144
+
4. Add the backend servers to the backend pool.
145
+
146
+
### Add a backend subnet
147
+
148
+
The subnet *myAGSubnet* can only contain the application gateway, so we need another subnet to add backend targets.
149
+
150
+
To create a backend subnet:
151
+
152
+
1. Select the **myVNet** resource. You can select it under **Deployment details** after deployment of the application gateway is complete, or you can search for Virtual networks and select it from the list.
153
+
2. Under **Settings**, select **Subnets** and then select **+ Subnet** to begin adding a new subnet.
154
+
155
+
-**Name**: Enter *myBackendSubnet*.
156
+
-**Subnet address range**: Enter an address range that doesn't overlap with the address range of *myAGSubnet*. For example, if the address range of *myAGSubnet* is 10.0.0.0/24, enter *10.0.1.0/24* for the address range of *myBackendSubnet*. This address range might be already entered by default.
157
+
158
+
3. Use the default settings for other items and then select **Save**.
159
+
160
+

0 commit comments