From f853ebd0b42dc4b09660446084f70a5cbd19ef87 Mon Sep 17 00:00:00 2001
From: Justin Webster <justin.webster@gmail.com>
Date: Wed, 15 Dec 2021 10:37:14 -0800
Subject: [PATCH] Updated the "Example of a load balancer" section, and added 2
 new "Example of" sections for alternate Load Balancer configurations, for new
 and existing features related to the following Azure CPI PRs/issues:

- https://github.com/cloudfoundry/bosh-azure-cpi-release/pull/651 (Fixes https://github.com/cloudfoundry/bosh-azure-cpi-release/issues/644)
- https://github.com/cloudfoundry/bosh-azure-cpi-release/pull/541 (Fixed https://github.com/cloudfoundry/bosh-azure-cpi-release/issues/328)
- https://github.com/cloudfoundry/bosh-azure-cpi-release/pull/638 (Fixed https://github.com/cloudfoundry/bosh-azure-cpi-release/issues/111)

Note: This commit assumes that PR #651 will be included in a new `v37.7.0` release of the Azure CPI (in order to properly document the CPI version requirements of new features). If PR #651 is included in a different CPI version, then this PR will need to be amended appropriately.
---
 content/azure-cpi.md | 42 ++++++++++++++++++++++++++++++++++++++----
 1 file changed, 38 insertions(+), 4 deletions(-)

diff --git a/content/azure-cpi.md b/content/azure-cpi.md
index 98891efa..81765e08 100644
--- a/content/azure-cpi.md
+++ b/content/azure-cpi.md
@@ -193,15 +193,47 @@ vm_types:
       size: 30_720
 ```
 
-Example of a load balancer:
+Example of a load balancer (simple configuration):
 
 ```yaml
 vm_extensions:
-- name: load-balancer
+- name: load-balancer-example-1
   cloud_properties:
     load_balancer: <load-balancer-name>
 ```
 
+Example of a load balancer (complex configuration):
+
+```yaml
+vm_extensions:
+- name: load-balancer-example-2
+  cloud_properties:
+    load_balancer:
+      name: <load-balancer-name>
+      # resource_group_name is optional
+      resource_group_name: <resource-group-name>
+      # backend_pool_name is optional
+      backend_pool_name: <backend-pool-name>
+```
+
+Example of multiple load balancers (4 backend address pools of 3 LBs):
+
+```yaml
+vm_extensions:
+- name: load-balancer-example-3
+  cloud_properties:
+    load_balancer:
+      - name: <load-balancer-1-name>
+      # NOTE: the following LB is in a different Resource Group (than the `resource_group_name` in the global CPI settings)
+      - name: <load-balancer-2-name>
+        resource_group_name: <resource-group-name>
+      # NOTE: the following 2 attach the VMs to 2 separate backend address pools of the same LB
+      - name: <load-balancer-3-name>
+        backend_pool_name: <backend-pool-2-name>
+      - name: <load-balancer-3-name>
+        backend_pool_name: <backend-pool-4-name>
+```
+
 Example of an availability set:
 
 ```yaml
@@ -211,7 +243,7 @@ vm_extensions:
     availability_set: <availability-set-name>
 ```
 
-The above load-balancer cloud configuration examples are referenced within the deployment manifest as such:
+The above `vm_extensions` cloud configuration examples are referenced within the deployment manifest as such:
 
 ```yaml
 instance_groups:
@@ -224,7 +256,9 @@ instance_groups:
   jobs:
   - name: router
     release: default
-  vm_extensions: [load-balancer]
+  vm_extensions:
+  - load-balancer-example-1
+  - availability-set
 ```
 
 ---