Skip to content

Document IPv6 feature for Azure #919

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
s4heid wants to merge 1 commit into
base: master
Choose a base branch
from
+12 −5
Open

Document IPv6 feature for Azure #919

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 9 additions & 2 deletions content/azure-cpi.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down Expand Up @@ -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.
Comment thread
coderabbitai[bot] marked this conversation as resolved.

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

Expand Down Expand Up @@ -251,7 +256,9 @@ vm_extensions:
# resource_group_name is optional
resource_group_name: <resource-group-name>
# backend_pool_name is optional
backend_pool_name: <backend-pool-name>
backend_pool_name: <ipv4-backend-pool-name>
# backend_pool_name_v6 is optional
backend_pool_name_v6: <ipv6-backend-pool-name>
```

Example of multiple load balancers (4 backend address pools of 3 LBs):
Expand Down
2 changes: 1 addition & 1 deletion content/dual-stack-networks.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:**

Expand Down
4 changes: 2 additions & 2 deletions content/networks.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -499,8 +499,8 @@ The Director does not enforce how many networks can be assigned to each instance
| **AWS** | Manual | Supported<sup>1</sup> | Supported<sup>2</sup> |
| | VIP | Supported<sup>1</sup> (from v107.0.2) | — |
| | | | |
| **Azure** | Manual | — | — |
| | VIP | — | — |
| **Azure** | Manual | [Supported](azure-cpi.md#dual-stack-networks) | — |
| | VIP | Supported | — |
| | | | |
| **OpenStack** | Manual | — | — |
| | VIP | — | — |
Expand Down