a day ago
- IPv6 provides a massive number of addresses (e.g., a /64 subnet with 18.4 quintillion addresses) that can be used to assign unique IPv6 addresses to individual services on a single server.
- Using IPv6 with Cloudflare allows each service to listen on its own IPv6 address, while Cloudflare handles IPv4 to IPv6 translation for users without IPv6 support, eliminating the need for a reverse proxy for routing.
- This method reduces single points of failure compared to using a reverse proxy, as each service has its own address and can fail independently.
- Ephemeral environments can be deployed by assigning random IPv6 addresses via the Cloudflare API in CI/CD pipelines, with low collision risk.
- Docker’s IPv6 support is a major drawback, requiring workarounds like using '--network host' (which sacrifices security isolation) or 'macvlan' networks (which may lack IPv4 outbound connectivity).
- Docker 28.0 has added experimental IPv6-only network support, and Podman is noted for better IPv6 compatibility, suggesting gradual improvement in container IPv6 support.