Google Cloud compute routing subdomains

[zkassis]

I am new to google cloud and I am trying to understand an existing setup, but I don't have access to the person who created it.

I have multiple compute engine VMs (Debian):

VM	External IP
VM 1: development	123
VM 2: test	345
VM 3: Prod 1	567
VM 3: Prod 2	789

Other components available:
- I also have a backend setup that holds both production instances.
- One front end linked to the backend above with external IP 123
- There is also one external load balancer where only the front end and backend are linked and I can't find any rule linking the load balancer to the test and dev instances.
- There is no DNS zone or rules setup on the google cloud console.
- I have a wildcard SSL that is applied. I updated the SSL and the policy setup but it is currently only reflecting on the production and not the other environments

I am trying to understand the existing setup, mainly how the routing/forwarding can be done. My question is, I have 3 different subdomains:

- prod.domainName.com
- test.domainName.com
- dev.domainName.com

the A record for all 3 sub-domains points to IP 123 on GoDaddy, where can the routing be set up since the domain DNS seems to be pointing to the public IP of the front end, and as I said there is no DNS set up on the google cloud.

Appreciate any help or pointers, I have been going through the Google Cloud documentation and researching this for hours with no luck yet.

Thank you in advance!

[grobledo]

This forum is designed to answer general questions about GCP Products.

Your particular issue would require taking a look at your project; I recommend you to open a case through the Support Hub page, and someone from GCP will follow up there.

[pfrankwicz]

Hi zkassis, Here are some thoughts from a rank beginner in GCP. Your ecosystem reads as basically PROD VM3 with a backend-LB and “wildcard SSL{?}”.  VM1 TEST & VM2 DEV are isolated – no backend or LB.  No description of VPC conductivity between VMs PROD – DEV or TEST. I would start with provisioning DEV & TEST in GCP.   Set up DEV and TEST cloud environments in GCP: create new external load balancer and two backends [bckend_DEV & bckend_TEST]; Create a Google managed SSL for *.domainName.com.  Setup GCP DNS for the DEV & TEST [A & CNAME, etc records]. [I assume IP123 is attached to VM3 - not VM1.]   Debug, test and monitor DEV & TEST environments in their GCP ecosystems.  At a later date, migrate PROD off GoDaddy DNS to GCP DNS.   Phase two would be setting up GCP load balancer that will https traffic of PROD, DEV & TEST to each respective backends.   Proceed with caution with the PROD side of the ecosystem.  Take “an existing setup” – break it, fix it and make it on your own.  Good luck clouding, pfrankwicz.