From 841e264aa2ac8b102f6f4c93d29c096fd362e020 Mon Sep 17 00:00:00 2001 From: Sebastian Heid <8442432+s4heid@users.noreply.github.com> Date: Tue, 18 Aug 2026 13:15:32 +0200 Subject: [PATCH] Document IPv6 feature for Azure --- content/azure-cpi.md | 11 +++++++++-- content/dual-stack-networks.md | 2 +- content/networks.md | 4 ++-- 3 files changed, 12 insertions(+), 5 deletions(-) diff --git a/content/azure-cpi.md b/content/azure-cpi.md index 2333cc67..687ac51e 100644 --- a/content/azure-cpi.md +++ b/content/azure-cpi.md @@ -54,6 +54,10 @@ networks: accelerated_networking: true ``` +### Dual-stack Networks {: #dual-stack-networks } + +The Azure CPI can place IPv4 and IPv6 manual networks on the same NIC. Configure both address families on one Azure subnet, have both BOSH networks reference the same `resource_group_name`, `virtual_network_name`, and `subnet_name`, and assign the networks the same [`nic_group`](network-interface-groups.md) in the deployment manifest. See [Dual Stack Networks](dual-stack-networks.md) for the manifest structure. + ### Vip Network Schema for `cloud_properties` section: @@ -120,8 +124,9 @@ Schema for `cloud_properties` section: - **name** [String, required]: The name of the load balancer. - **resource\_group\_name** [String, optional]: The name of the load balancer's resource group. Default value is the `resource_group_name` specified in the global CPI settings. - - **backend\_pool\_name** [String, optional]: The name of the load balancer backend address pool which VMs' IPs should be attached to. If not specified, defaults to the load balancer's "first" backend pool (as returned by the Azure API). + - **backend\_pool\_name** [String, optional]: The name of the load balancer backend address pool which VMs' IPv4 addresses should be attached to. If not specified, defaults to the load balancer's "first" backend pool (as returned by the Azure API). - This property is supported in CPI [v37.7.0+](https://github.com/cloudfoundry/bosh-azure-cpi-release/releases/tag/v37.7.0). + - **backend\_pool\_name\_v6** [String, optional]: The name of the load balancer backend address pool which VMs' IPv6 addresses should be attached to. If not specified, IPv6 addresses are not attached to a backend pool. - **application_gateway** [String, optional]: Name of the [application gateway](https://azure.microsoft.com/en-us/services/application-gateway/) which the VMs should be attached to. @@ -251,7 +256,9 @@ vm_extensions: # resource_group_name is optional resource_group_name: # backend_pool_name is optional - backend_pool_name: + backend_pool_name: + # backend_pool_name_v6 is optional + backend_pool_name_v6: ``` Example of multiple load balancers (4 backend address pools of 3 LBs): diff --git a/content/dual-stack-networks.md b/content/dual-stack-networks.md index ec498787..fe6fccdd 100644 --- a/content/dual-stack-networks.md +++ b/content/dual-stack-networks.md @@ -31,7 +31,7 @@ The cloud config defines how BOSH allocates network resources. For dual stack, c - **Reserved Ranges**: Reserve gateway and infrastructure addresses to prevent conflicts !!! tip - For IaaS-specific network configuration details, see [Network cloud properties](aws-cpi.md#networks). + For IaaS-specific configuration, see [CPI-specific network cloud properties](networks.md#cloud-properties). **Basic Dual Stack Example:** diff --git a/content/networks.md b/content/networks.md index 5b7bc0be..bffd02e3 100644 --- a/content/networks.md +++ b/content/networks.md @@ -499,8 +499,8 @@ The Director does not enforce how many networks can be assigned to each instance | **AWS** | Manual | Supported1 | Supported2 | | | VIP | Supported1 (from v107.0.2) | — | | | | | | -| **Azure** | Manual | — | — | -| | VIP | — | — | +| **Azure** | Manual | [Supported](azure-cpi.md#dual-stack-networks) | — | +| | VIP | Supported | — | | | | | | | **OpenStack** | Manual | — | — | | | VIP | — | — |