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

Migrate to IPv6-native #34

Open
7 tasks
jayaddison opened this issue Nov 8, 2022 · 0 comments
Open
7 tasks

Migrate to IPv6-native #34

jayaddison opened this issue Nov 8, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@jayaddison
Copy link
Member

jayaddison commented Nov 8, 2022

Is your feature request related to a problem? Please describe.
Tasks could include, and are not limited to:

  • Determining a suitable IPv6 allocation range to use from our ISP
  • Migrating pods within the microservice cluster to an IPv6 range
    • Should the Kubernetes host node be public and/or routable?
    • Should the Kubernetes pods be public and/or routable?
  • Migrating stateful services (opensearch, postgresql, squid) to use IPv6 addresses
  • Updating haproxy, nginx configurations as-required
  • Configuring production site network (routing, forwarding, and so on) as-required
  • Adding IPv6 DNS records for *.reciperadar.com
  • Testing connectivity from a range of source networks (cellular, IPv6 native, IPv4 native)

Describe the solution you'd like
Browsing to https://www.reciperadar.com should be possible from IPv6-based network environments, without the involvement of any IPv4-based networking.

IPv4 support may be retained if it proves straightforward to do that, but it isn't a goal of this migration.

@jayaddison jayaddison added the enhancement New feature or request label Nov 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

No branches or pull requests

1 participant