<p>I have a website (front-end + backend) published on my own GKE cluster. The current configuration relies on one static IP allocated in GCP + one GCE Ingress instance to open the website to internet traffic. It works.</p>
<p>Is there a way to not use a static IP and rely on &quot;ghs.googlehosted.com.&quot; ? I don't mind having a fixed static IP. I've tried to set up the DNS as GCP advises on <a href="https://console.cloud.google.com/appengine/settings/domains?project=YOURPROJECTID" rel="nofollow noreferrer">https://console.cloud.google.com/appengine/settings/domains?project=YOURPROJECTID</a> but it doesn't work. Looking at the service logs my FE can communicate internally to my BE. It is just the Ingress + LB configuration that doesn't let the <code>googlehosted.com</code> infra know my website is waiting for traffic and all requests should be sent there. Does such a configuration even exist?</p>

Dr. Vick
<p>If you take each piece of the architecture:</p>
<ul>
<li>You have your cluster with your services</li>
<li>You want to expose the services. You create a load balancer</li>
<li>The load balancer is created with an IP address</li>
</ul>
<p>So, at the end, you only have an IP, there is no other way to expose a service with GKE. You have to use a Load Balancer, and the load balancer expose an IP.</p>
<p><em>Other cloud providers, like AWS, expose a subdomain and not an IP when you create a load balancer, and thus you aren't linked to an IP. It's not the case of GCP, at least for GKE</em></p>
