Skip to content

Commit 4f6f918

Browse files
Merge pull request #303059 from JackStromberg/patch-8
v1.7.9
2 parents cd31cc2 + aeb3a30 commit 4f6f918

File tree

4 files changed

+38
-10
lines changed

4 files changed

+38
-10
lines changed

articles/application-gateway/for-containers/alb-controller-helm-chart.md

Lines changed: 30 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: application-gateway
55
author: mbender-ms
66
ms.service: azure-appgw-for-containers
77
ms.topic: release-notes
8-
ms.date: 5/2/2025
8+
ms.date: 7/21/2025
99
ms.author: mbender
1010
# 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.
1111
---
@@ -19,6 +19,7 @@ A Helm chart to install the ALB Controller on Kubernetes.
1919

2020
The following parameters are supported for configuration during installation:
2121

22+
- nodeSelector
2223
- tolerations
2324
- name
2425
- installGatewayApiCRDs
@@ -31,6 +32,7 @@ The following parameters are supported for configuration during installation:
3132
| Key | Type | Default | Description |
3233
| ----- | ------ | --------- | ------------- |
3334
| albController.controller | object | `{"replicaCount":2,"resource":{"limits":{"cpu":"400m","memory":"400Mi"},"requests":{"cpu":"100m","memory":"200Mi"}},"tolerations":[]}` | ALB Controller parameters |
35+
| albController.controller.nodeSelector | object | {} | nodeselector for alb-cotnroller |
3436
| albController.controller.replicaCount | int | `2` | ALB Controller's replica count. |
3537
| albController.controller.resource | object | `{"limits":{"cpu":"400m","memory":"400Mi"},"requests":{"cpu":"100m","memory":"200Mi"}}` | ALB Controller's container resource parameters. |
3638
| albController.controller.tolerations | list | `[]` | Tolerations for ALB Controller |
@@ -48,6 +50,33 @@ The following parameters are supported for configuration during installation:
4850
| albController.namespace | string | `"azure-alb-system"` | Namespace to deploy ALB Controller components in. |
4951
| albController.securityPolicyFeatureFlag | bool | `false` | Enable Application Load Balancer Security Policy Resource (WAF Preview). |
5052

53+
## nodeSelector
54+
55+
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.
62+
63+
`kubectl label nodes <node-name> albController=true`
64+
65+
2. Specify the nodeSelector via the helm install command using the following example:
66+
67+
```bash
68+
HELM_NAMESPACE='<namespace for deployment>'
69+
CONTROLLER_NAMESPACE='azure-alb-system'
70+
VERSION='<latest_version>'
71+
az aks get-credentials --resource-group $RESOURCE_GROUP --name $AKS_NAME
72+
helm install alb-controller oci://mcr.microsoft.com/application-lb/charts/alb-controller \
73+
--namespace $HELM_NAMESPACE \
74+
--version $VERSION \
75+
--set albController.namespace=$CONTROLLER_NAMESPACE \
76+
--set albController.podIdentity.clientID=$(az identity show -g $RESOURCE_GROUP -n azure-alb-identity --query clientId -o tsv)
77+
--set nodeSelector.albController=true
78+
```
79+
5180
## Tolerations
5281

5382
Tolerations follow Kubernetes' implementation as defined [here](https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/).

articles/application-gateway/for-containers/alb-controller-release-notes.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: application-gateway
55
author: mbender-ms
66
ms.service: azure-appgw-for-containers
77
ms.topic: release-notes
8-
ms.date: 5/2/2025
8+
ms.date: 7/21/2025
99
ms.author: mbender
1010
# 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.
1111
---
@@ -27,12 +27,13 @@ Instructions for new or existing deployments of ALB Controller are found in the
2727

2828
| ALB Controller Version | Gateway API Version | Minimum Kubernetes Version | Release Notes |
2929
| ---------------------- | ------------------- | ------------------ | ------------- |
30-
| 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 |
3131

3232
## Release history
3333

3434
| ALB Controller Version | Gateway API Version | Minimum Kubernetes Version | Release Notes |
3535
| ---------------------- | ------------------- | ------------------ | ------------- |
36+
| 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 |
3637
| 1.5.2 | v1.1.1 | v1.26 | Support for Azure CNI Overlay |
3738
| 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 |
3839
| 1.3.7| v1.1 | v1.26 | Minor fixes and improvements |

articles/application-gateway/for-containers/quickstart-deploy-application-gateway-for-containers-alb-controller.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: mbender-ms
77
ms.service: azure-appgw-for-containers
88
ms.custom: devx-track-azurecli
99
ms.topic: quickstart
10-
ms.date: 7/9/2025
10+
ms.date: 7/21/2025
1111
ms.author: mbender
1212
# 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.
1313
---
@@ -147,7 +147,7 @@ You need to complete the following tasks before deploying Application Gateway fo
147147
az aks get-credentials --resource-group $RESOURCE_GROUP --name $AKS_NAME
148148
helm install alb-controller oci://mcr.microsoft.com/application-lb/charts/alb-controller \
149149
--namespace $HELM_NAMESPACE \
150-
--version 1.6.7 \
150+
--version 1.7.9 \
151151
--set albController.namespace=$CONTROLLER_NAMESPACE \
152152
--set albController.podIdentity.clientID=$(az identity show -g $RESOURCE_GROUP -n azure-alb-identity --query clientId -o tsv)
153153
```
@@ -165,7 +165,7 @@ You need to complete the following tasks before deploying Application Gateway fo
165165
az aks get-credentials --resource-group $RESOURCE_GROUP --name $AKS_NAME
166166
helm upgrade alb-controller oci://mcr.microsoft.com/application-lb/charts/alb-controller \
167167
--namespace $HELM_NAMESPACE \
168-
--version 1.6.7 \
168+
--version 1.7.9 \
169169
--set albController.namespace=$CONTROLLER_NAMESPACE \
170170
--set albController.podIdentity.clientID=$(az identity show -g $RESOURCE_GROUP -n azure-alb-identity --query clientId -o tsv)
171171
```

articles/application-gateway/for-containers/troubleshooting-guide.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: application-gateway
55
author: mbender-ms
66
ms.service: azure-appgw-for-containers
77
ms.topic: troubleshooting
8-
ms.date: 3/31/2025
8+
ms.date: 7/21/2025
99
ms.author: mbender
1010
# 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.
1111
---
@@ -27,7 +27,6 @@ Example output:
2727
| NAME | READY | UP-TO-DATE | AVAILABLE | AGE | CONTAINERS | IMAGES | SELECTOR |
2828
| ------------------------ | ----- | ---------- | --------- | ---- | ----------------------- | ------------------------------------------------------------------------------- | -------- |
2929
| alb-controller | 2/2 | 2 | 2 | 18d | alb-controller | mcr.microsoft.com/application-lb/images/alb-controller:**1.5.2** | app=alb-controller |
30-
| alb-controller-bootstrap | 1/1 | 1 | 1 | 18d | alb-controller-bootstrap | mcr.microsoft.com/application-lb/images/alb-controller-bootstrap:**1.5.2** | app=alb-controller-bootstrap |
3130

3231
In this example, the ALB controller version is **1.5.2**.
3332

@@ -54,11 +53,10 @@ Logs can be collected from the ALB Controller by using the _kubectl logs_ comman
5453
| ---------------------------------------- | ----- | ------- | -------- | ---- |
5554
| alb-controller-6648c5d5c-sdd9t | 1/1 | Running | 0 | 4d6h |
5655
| alb-controller-6648c5d5c-au234 | 1/1 | Running | 0 | 4d6h |
57-
| alb-controller-bootstrap-6648c5d5c-hrmpc | 1/1 | Running | 0 | 4d6h |
5856

5957
ALB controller uses an election provided by controller-runtime manager to determine an active and standby pod for high availability.
6058

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.
6260

6361
# [Linux](#tab/active-pod-linux)
6462

0 commit comments

Comments
 (0)