Merge pull request #267353 from JackStromberg/patch-154

GA Release

Author: AnnaMHuff

articles/application-gateway/for-containers/alb-controller-backend-health-metrics.md

@@ -6,7 +6,7 @@ author: greglin
 ms.service: application-gateway
 ms.subservice: appgw-for-containers
 ms.topic: article
-ms.date: 07/24/2023
+ms.date: 02/27/2024
 ms.author: greglin
 ---
 
@@ -15,17 +15,19 @@ ms.author: greglin
 Understanding backend health of your Kubernetes services and pods is crucial in identifying issues and assistance in troubleshooting.  To help facilitate visibility into backend health, ALB Controller exposes backend health and metrics endpoints in all ALB Controller deployments.
 
 ALB Controller's backend health exposes three different experiences:
+
 1. Summarized backend health by Application Gateway for Containers resource
 2. Summarized backend health by Kubernetes service
 3. Detailed backend health for a specified Kubernetes service
 
 ALB Controller's metric endpoint exposes both metrics and summary of backend health.  This endpoint enables exposure to Prometheus.
 
 Access to these endpoints can be reached via the following URLs:
+
 - Backend Health - http://\<alb-controller-pod-ip\>:8000/backendHealth
-   - Output is JSON format
+  - Output is JSON format
 - Metrics - http://\<alb-controller-pod-ip\>:8001/metrics
-   - Output is text format
+  - Output is text format
 
 Any clients or pods that have connectivity to this pod and port may access these endpoints. To restrict access, we recommend using [Kubernetes network policies](https://kubernetes.io/docs/concepts/services-networking/network-policies/) to restrict access to certain clients.
 
@@ -49,12 +51,14 @@ Example output:
 Once you have the IP address of your alb-controller pod, you may validate the backend health service is running by browsing to http://\<pod-ip\>:8000.
 
 For example, the following command may be run:
+
 ```bash
 curl http://10.1.0.247:8000
 ```
 
 Example response:
-```
+
+```text
 Available paths:
 Path: /backendHealth
 Description: Prints the backend health of the ALB.
@@ -74,11 +78,13 @@ This experience summarizes of all Kubernetes services with references to Applica
 This experience may be accessed by specifying the Application Gateway for Containers resource ID in the query of the request to the alb-controller pod.
 
 The following command can be used to probe backend health for the specified Application Gateway for Containers resource.
+
 ```bash
 curl http://\<alb-controller-pod-ip-address\>:8000/backendHealth?alb-id=/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/resourcegroups/yyyyyyyy/providers/Microsoft.ServiceNetworking/trafficControllers/zzzzzzzzzz
 ```
 
 Example output:
+
 ```json
 {
   "services": [
@@ -115,11 +121,13 @@ This experience searches for the health summary status of a given service.
 This experience may be accessed by specifying the name of the namespace, service, and port number of the service in the following format of the query string to the alb-controller pod: _\<namespace\>/\<service\>/\<service-port-number\>_
 
 The following command can be used to probe backend health for the specified Kubernetes service.
+
 ```bash
 curl http://\<alb-controller-pod-ip-address\>:8000/backendHealth?service-name=default/service-hello-world/80
 ```
 
 Example output:
+
 ```json
 {
   "services": [
@@ -145,11 +153,13 @@ This experience shows all endpoints that make up the service, including their co
 This experience may be accessed by specifying detailed=true in the query string to the alb-controller pod.
 
 For example, we can verify individual endpoint health by executing the following command:
+
 ```bash
 curl http://\<alb-controller-pod-ip-address\>:8000/backendHealth?service-name=default/service-hello-world/80\&detailed=true
 ```
 
 Example output:
+
 ```json
 {
   "services": [
@@ -182,7 +192,7 @@ ALB Controller currently surfaces metrics following [text based format](https://
 
 The following Application Gateway for Containers specific metrics are currently available today:
 
-| Metric Name | Description                                                                           | 
+| Metric Name | Description                                                                           |
 | ----------- | ------------------------------------------------------------------------------------- |
 | alb_connection_status | Connection status to an Application Gateway for Containers resource |
 | alb_reconnection_count | Number of reconnection attempts to an Application Gateway for Containers resources |

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

@@ -6,7 +6,7 @@ author: greglin
 ms.service: application-gateway
 ms.subservice: appgw-for-containers
 ms.topic: article
-ms.date: 12/05/2023
+ms.date: 02/27/2024
 ms.author: greglin
 ---
 
@@ -19,13 +19,20 @@ The ALB Controller is a Kubernetes deployment that orchestrates configuration an
 Each release of ALB Controller has a documented helm chart version and supported Kubernetes cluster version.
 
 Instructions for new or existing deployments of ALB Controller are found in the following links:
+
 - [New deployment of ALB Controller](quickstart-deploy-application-gateway-for-containers-alb-controller.md#for-new-deployments)
 - [Upgrade existing ALB Controller](quickstart-deploy-application-gateway-for-containers-alb-controller.md#for-existing-deployments)
 
 ## Latest Release (Recommended)
-0.6.3 - Hotfix to address handling of AGC frontends during controller restart in managed scenario 
+
+| ALB Controller Version | Gateway API Version | Kubernetes Version | Release Notes |
+| ---------------------- | ------------------- | ------------------ | ------------- |
+| 1.0.0| v1 | v1.26, v1.27, v1.28 | URL redirect for both Gateway and Ingress API, v1beta1 -> v1 of Gateway API, quality improvements<br/>Breaking Changes: TLS Policy for Gateway API [PolicyTargetReference](https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io%2fv1alpha2.PolicyTargetReferenceWithSectionName)<br/>Listener is now referred to as [SectionName](https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.SectionName)<br/>Fixes: Request timeout of 3 seconds, [HealthCheckPolicy interval](https://github.com/Azure/AKS/issues/4086), [pod crash for missing API fields](https://github.com/Azure/AKS/issues/4087) |
 
 ## Release history
+
+0.6.3 - Hotfix to address handling of AGC frontends during controller restart in managed scenario
+
 0.6.2 - Skipped
 
 November 6, 2023 - 0.6.1 - Gateway / Ingress API - Header rewrite support, Ingress API - URL rewrite support, Ingress multiple-TLS listener bug fix,
@@ -38,4 +45,5 @@ July 25, 2023 - 0.4.023971 - Ingress + Gateway coexistence improvements
 July 24, 2023 - 0.4.023961 - Improved Ingress support
 
 July 24, 2023 - 0.4.023921 - Initial release of ALB Controller
-* Minimum supported Kubernetes version: v1.25
+
+- Minimum supported Kubernetes version: v1.25