-
Notifications
You must be signed in to change notification settings - Fork 18k
x/build/vcs-test: migrate to GKE #53889
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
Comments
Better still, I would like to eliminate The caching issues with I'm still evaluating to what extent that's actually feasible. |
Sounds good, but will take at least a year to roll out by definition, so I'm not going to wait on it :) |
Change https://go.dev/cl/418298 mentions this issue: |
We currently run vcs-test as a VM image. Build it out as a GKE service. We run a pod with two containers, one for Apache serving SVN and one for the vcweb server. Because it needs to serve HTTP, not just HTTPS, we use a new ingress that doesn't force HTTPS redirects. Remove /tls, which will be useless now that it's behind a load balancer. AFAICT it's not used anywhere. The server is up and running at 34.110.184.62. $ tail -n1 /etc/hosts 34.110.184.62 vcs-test.golang.org $ git clone https://vcs-test.golang.org/git/gitrepo1 Cloning into 'gitrepo1'... remote: Enumerating objects: 19, done. remote: Counting objects: 100% (19/19), done. remote: Compressing objects: 100% (10/10), done. remote: Total 19 (delta 1), reused 0 (delta 0) Unpacking objects: 100% (19/19), 1.40 KiB | 476.00 KiB/s, done. $ svn co https://vcs-test.golang.org/svn/hello A hello/hello.go Checked out revision 1. For golang/go#53889. Change-Id: I3e3e5078b81867689a8b8dc49dd5914c4a6181f0 Reviewed-on: https://go-review.googlesource.com/c/build/+/418298 Run-TryBot: Heschi Kreinick <[email protected]> TryBot-Result: Gopher Robot <[email protected]> Reviewed-by: Jenny Rakoczy <[email protected]> Auto-Submit: Heschi Kreinick <[email protected]>
Change https://go.dev/cl/418777 mentions this issue: |
It's changing as part of the move to GKE. Keep the old IP temporarily accessible while the DNS change gradually propagates. For golang/go#53889. Updates golang/go#51444. Change-Id: I324623c3b79d1b7af0dd2d8f3aea5acec4b849f7 Reviewed-on: https://go-review.googlesource.com/c/build/+/418777 Reviewed-by: Heschi Kreinick <[email protected]> Run-TryBot: Dmitri Shuralyov <[email protected]> Reviewed-by: Carlos Amedee <[email protected]> Reviewed-by: Dmitri Shuralyov <[email protected]> Auto-Submit: Dmitri Shuralyov <[email protected]> TryBot-Result: Gopher Robot <[email protected]>
Change https://go.dev/cl/419080 mentions this issue: |
When I updated to the latest version of Debian, the container got python3 instead of 2. Update the hgweb script to work with 3. For golang/go#53889. Change-Id: Ieccb24f06841f1e69806b5a6500d065c64c3b04d Reviewed-on: https://go-review.googlesource.com/c/build/+/419080 Reviewed-by: Dmitri Shuralyov <[email protected]> Auto-Submit: Heschi Kreinick <[email protected]> TryBot-Result: Gopher Robot <[email protected]> Run-TryBot: Heschi Kreinick <[email protected]> Reviewed-by: Dmitri Shuralyov <[email protected]>
Since the CLs have landed, is there more to do for this issue? |
The DNS rollout finished over the weekend and I don't see failures on the dashboard, so nope, all done. |
Change https://go.dev/cl/423342 mentions this issue: |
Now that I've turned down the VM-based vcs-test server we don't need some code. Also disable autocert on the GKE version, which I think in retrospect I never needed. For golang/go#53889. Change-Id: I005bc61228c04a37765895decd485b10167b994e Reviewed-on: https://go-review.googlesource.com/c/build/+/423342 Run-TryBot: Heschi Kreinick <[email protected]> Reviewed-by: Dmitri Shuralyov <[email protected]> Reviewed-by: Dmitri Shuralyov <[email protected]> TryBot-Result: Gopher Robot <[email protected]>
I wanted to do this a year ago but never got around to it. I don't think we can use Ingress because it requires SSH access, but we can get rid of the VM at least.
cc @golang/release
The text was updated successfully, but these errors were encountered: