While GCP has IPv6 support for their global load balancers, it's very limited and not sufficient for many uses. For example, I've been working on contributing

While GCP has IPv6 support for their global load balancers, it's very limited and not sufficient for many uses. For example, I've been working on contributing IPv6 support to GitLab.com [0], which is hosted on GCP. Turns out it's impossible for the main site right now, because none of the global load balancer types allow port 22, which is used for Git traffic. I've no idea why there are even such restrictions, but there's of course a "feature" request for allowing port 22 [1]. I was able to repurpose the work for other parts of GitLab.com, but I've yet to get even those to work, due to the load balancers gobbling up HTTPS/SSL requests [2]. [0] https://gitlab.com/gitlab-com/gitlab-com-infrastructure/merge_requests/427 https://gitlab.com/gitlab-com/gitlab-com-infrastructure/merg... [1] https://issuetracker.google.com/issues/77944636 https://issuetracker.google.com/issues/77944636 [2] https://gitlab.com/gitlab-com/gitlab-com-infrastructure/merge_requests/427#note_102821029 https://gitlab.com/gitlab-com/gitlab-com-infrastructure/merg...