Promoting GCP to a secondary caused it to start giving 503 "We are migrating to GCP" notifications to users inside the VPN
Seen in the 2018-08-07 failover attempt
After merging https://dev.gitlab.org/cookbooks/chef-repo/merge_requests/1989 to master and running chef-client
on the gstg
nodes, they started giving the normally-configured 503 "We are migrating to GCP" error page to users, even when they were coming from inside the VPN.
We need to work this out and fix it in time for the 2018-08-08 failover attempt, since we need the frontend to be up and running via the VPN or bastion hosts (I didn't test this method) for QA to work.