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-helm-chart.md
+30-1Lines changed: 30 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ services: application-gateway
5
5
author: mbender-ms
6
6
ms.service: azure-appgw-for-containers
7
7
ms.topic: release-notes
8
-
ms.date: 5/2/2025
8
+
ms.date: 7/21/2025
9
9
ms.author: mbender
10
10
# Customer intent: As a Kubernetes operator, I want to install the ALB Controller using a Helm chart, so that I can manage Application Load Balancer resources effectively within my container environment.
11
11
---
@@ -19,6 +19,7 @@ A Helm chart to install the ALB Controller on Kubernetes.
19
19
20
20
The following parameters are supported for configuration during installation:
21
21
22
+
- nodeSelector
22
23
- tolerations
23
24
- name
24
25
- installGatewayApiCRDs
@@ -31,6 +32,7 @@ The following parameters are supported for configuration during installation:
nodeSelector follows Kubernetes' implementation as defined [here](https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#nodeselector)
56
+
57
+
nodeSelector will only provision ALB Controller pods to nodes with a defined label.
58
+
59
+
In this example, we will label a set of nodes with a node label called `albController`.
60
+
61
+
1. Label each node you desire to run the ALB controller pods.
Copy file name to clipboardExpand all lines: articles/application-gateway/for-containers/alb-controller-release-notes.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ services: application-gateway
5
5
author: mbender-ms
6
6
ms.service: azure-appgw-for-containers
7
7
ms.topic: release-notes
8
-
ms.date: 5/2/2025
8
+
ms.date: 7/21/2025
9
9
ms.author: mbender
10
10
# Customer intent: As a Kubernetes operator, I want to access the release notes for the ALB Controller, so that I can understand the latest updates and changes to optimize my configuration and deployments of Application Gateway for Containers.
11
11
---
@@ -27,12 +27,13 @@ Instructions for new or existing deployments of ALB Controller are found in the
27
27
28
28
| ALB Controller Version | Gateway API Version | Minimum Kubernetes Version | Release Notes |
| 1.6.7| v1.1.1 | v1.27 |[Fix for SSE timeout value of 0](https://aka.ms/qa2153620), [Overlay CNI fix](https://github.com/Azure/AKS/issues/4950), [support readinessProbe port by name](https://github.com/Azure/AKS/issues/4861), leverage init container during bootstrap, misc. bug fixes and improvements |
30
+
| 1.7.9| v1.2.1 | v1.27 |[Web Application Firewall (WAF) Public Preview](https://aka.ms/agc/waf), Updated to Gateway API v1.2.1, [nodeSelector support](https://github.com/Azure/AKS/issues/4370#issuecomment-2894487836), [Permissions fix for Overlay networks](https://github.com/Azure/AKS/issues/5039), fix for SAN regex matching, misc. performance improvements |
31
31
32
32
## Release history
33
33
34
34
| ALB Controller Version | Gateway API Version | Minimum Kubernetes Version | Release Notes |
| 1.6.7 | v1.1.1 | v1.27 |[Fix for SSE timeout value of 0](https://aka.ms/qa2153620), [Overlay CNI fix](https://github.com/Azure/AKS/issues/4950), [support readinessProbe port by name](https://github.com/Azure/AKS/issues/4861), leverage init container during bootstrap, misc. bug fixes and improvements |
36
37
| 1.5.2 | v1.1.1 | v1.26 | Support for Azure CNI Overlay |
37
38
| 1.4.12 | v1.1.1 | v1.26 | Updated to Gateway API version 1.1.1, Regex match support for path and header match in HTTP and GRPC routes, [Wildcard hostname fix](https://github.com/Azure/AKS/issues/4713), Misc. bug fixes and improvements |
38
39
| 1.3.7| v1.1 | v1.26 | Minor fixes and improvements |
Copy file name to clipboardExpand all lines: articles/application-gateway/for-containers/quickstart-deploy-application-gateway-for-containers-alb-controller.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ author: mbender-ms
7
7
ms.service: azure-appgw-for-containers
8
8
ms.custom: devx-track-azurecli
9
9
ms.topic: quickstart
10
-
ms.date: 7/9/2025
10
+
ms.date: 7/21/2025
11
11
ms.author: mbender
12
12
# Customer intent: As a Kubernetes administrator, I want to install the Application Gateway for Containers ALB Controller on my AKS cluster, so that I can efficiently manage load balancing rules and enhance application traffic handling.
13
13
---
@@ -147,7 +147,7 @@ You need to complete the following tasks before deploying Application Gateway fo
147
147
az aks get-credentials --resource-group $RESOURCE_GROUP --name $AKS_NAME
Copy file name to clipboardExpand all lines: articles/application-gateway/for-containers/troubleshooting-guide.md
+2-4Lines changed: 2 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ services: application-gateway
5
5
author: mbender-ms
6
6
ms.service: azure-appgw-for-containers
7
7
ms.topic: troubleshooting
8
-
ms.date: 3/31/2025
8
+
ms.date: 7/21/2025
9
9
ms.author: mbender
10
10
# Customer intent: As a cloud platform administrator, I want to troubleshoot issues with Application Gateway for Containers, so that I can ensure the service operates smoothly and effectively resolves any deployment or configuration problems.
11
11
---
@@ -27,7 +27,6 @@ Example output:
27
27
| NAME | READY | UP-TO-DATE | AVAILABLE | AGE | CONTAINERS | IMAGES | SELECTOR |
ALB controller uses an election provided by controller-runtime manager to determine an active and standby pod for high availability.
60
58
61
-
Copy the name of each alb-controller pod (not the bootstrap pod, in this case: `alb-controller-6648c5d5c-sdd9t` and `alb-controller-6648c5d5c-au234`) and run the following command to determine the active pod.
59
+
Copy the name of each alb-controller pod (in this case: `alb-controller-6648c5d5c-sdd9t` and `alb-controller-6648c5d5c-au234`) and run the following command to determine the active pod.
0 commit comments