Dual Stack (add IPv6) Support for BOSH Bootloader (AWS)
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- aws, go, terraform
- Domain
- cloud, infrastructure
Research direction
Start with the Terraform AWS implementation and the Go IP and CIDRBlock types referenced in the completed tasks. Review the dualstack variable, NLB load-balancer templates, and generated BOSH ops-file configuration, while checking the linked pull requests and BOSH dependency. Done means new AWS deployments support IPv4 or dual stack with correct ingress and BOSH configuration.
Written by the indexing model from the issue text.
Description
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:
- https://github.com/cloudfoundry/bosh-bootloader/pull/633
Extend or removeIPandCIDRBlocktypes. 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. - https://github.com/cloudfoundry/bosh-bootloader/pull/640
Enable IPv6 for AWS on terraform via the TF variabledualstack -
https://github.com/cloudfoundry/bosh-bootloader/pull/644https://github.com/cloudfoundry/bosh-bootloader/pull/669: Add theNLBload 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.- correct handling of LB type and
dualstackvariable in all Terraform templates
- correct handling of LB type and
- Configure BOSH via generated ops files for dual stack, when
dualstackoutput variable istrue.
- Dominant language
- Go
- Stars
- 181
- Forks
- 179
- Avg merge
- 9h 54m
- Merged PRs (30d)
- 2
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from cloudfoundry/bosh-bootloader
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
cloudfoundry/bosh-bootloader#701 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
cloudfoundry/bosh-bootloader#698 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 58/100
cloudfoundry/bosh-bootloader#681 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
cloudfoundry/bosh-bootloader#676 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
cloudfoundry/bosh-bootloader#641 · 2 comments ·
All issues in cloudfoundry/bosh-bootloader
Similar issues
-
area/docs framework/hugo help wanted language/markdown
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:other issue-rating: 🦞 diamond lobster no-stale P2
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
openclaw/crabbox#3060 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
kubeflow/semantic-operator#52 ·
Maintainers usually reply within 10 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
enhancement help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
PramodBasavarajMenasi/siftwise#52 ·
Maintainers usually reply within 1 day