Skip to content
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.

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

Plan moving ALBs to their own subnet #788

Open
4 tasks
bengerman13 opened this issue Oct 28, 2020 · 0 comments
Open
4 tasks

Plan moving ALBs to their own subnet #788

bengerman13 opened this issue Oct 28, 2020 · 0 comments

Comments

@bengerman13
Copy link
Contributor

Currently, our ALBs are in the same subnets as bosh deployments. This means that it is possible for an ALB to take up an IP address that bosh wants to use for a scale-out. Bosh then fails with no straightforward workaround.
This has prevented scale-outs from working on multiple occasions.

We should move ALBs into a different, dedicated subnet, and ensure they still have access to the resources required.

there are a few ways we can go about this. I think the easiest and safest looks like this:

  • create a new subnet for ALBs
  • create the routing rules required
  • create new ALBs that are exact copies, except they exist in the new subnets
  • test the new ALBs manually
  • update relevant DNS entries. Where possible, these should include both the new and the old ALBs
  • wait some time
  • Update relevant DNS entries again, removing old ALBs
  • wait some time
  • remove old ALBs

Acceptance criteria:

  • list of ALBs to be moved
  • planned block for new subnet
  • plan for moving ALBs (I believe there will be some ALBs that are more difficult to move and some that are easier. There may even be some that do not require moving)

Extra credit:

  • can we upgrade all our old ELBs at the same time
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant