In the frame of RFC0038, we would like to extend bosh-bootloader with IPv6 to support dual stack networking.
This change starts with the Terraform scripts and enables the changes in BOSH to support dual stack networking.
Tasks:
- Adapt the implementation in Terraform
- Ensure that new deployments can be created IPv4 or dual stack
Allow existing deployments to be updated to dual stack from IPv4
A migration path for existing bbl deployments could also be something that is added via additional change later.
Details:
In the frame of RFC0038, we would like to extend bosh-bootloader with IPv6 to support dual stack networking.
This change starts with the Terraform scripts and enables the changes in BOSH to support dual stack networking.
Tasks:
Allow existing deployments to be updated to dual stack from IPv4A migration path for existing bbl deployments could also be something that is added via additional change later.
Details:
Extend or remove
IPandCIDRBlocktypes. They are hardcoded to support only IPv4. They could be extended using Go's nativenet.IP,net.IPMask, etc. to do the same thing but across IPv4 and IPv6.Enable IPv6 for AWS on terraform via the TF variable
dualstackNLBload balancer type variant for AWS, as that one is needed for IPv6 ingress. This NLB should also do TLS termination, likecf_lbalready does on AWS.dualstackvariable in all Terraform templatesdualstackoutput variable istrue.