Specify URL instead of IP:port in network endpoints for applications behind reverse proxy

[aleksvujic]

We are using GCP external HTTPS load balancer, architecture is shown in the diagram below. The primary use of LB is redirecting users to static error site (hosted on Cloud Storage bucket) in case CE instance is down, Traefik crashes on CE, Docker crashes on CE, etc.

We have 4 backend services defined on load balancer:

1. static-error-page backend bucket
2. blog-backend-service, gallery-backend-service and shop-backend-service zonal network endpoint groups

Then, we defined host and path rules so that:

1. https://blog.company.com -> blog-backend-service
2. https://gallery.company.com -> gallery-backend-service
3. https://shop.company.com -> shop-backend-service
4. All unmatched (default) -> static-error-page

Each zonal network endpoint group (blog-backend-service, gallery-backend-service and shop-backend-service) has just 1 endpoint defined: 192.168.171:443 (192.168.171.3 is internal IP of CE instance).

However, since my websites are served behind reverse proxy (Traefik), specifying IP:port combination in network endpoint is useless because they all have the same IP:port. I would like to specify URL instead of IP:port in network endpoint (that way network endpoint would also show correct health status if website is down, it always reports healthy now, even if application is down).

Is it possible to specify URL instead of IP:port in network endpoint? If not, what are my alternatives?

(click on the image to enlarge it)

[Anik]

Hello 

Thank you for your question. You can try the option of Migrating from an IP:Port NEG to an FQDN:Port NEG as per the Gcp doc [1] to address your issue.

Also, It is worth mentioning that Google Groups is a place for non-technical how-to questions (where you're likely to find information like service status updates and release notes, and ranging from book recommendations to creative shortcuts) [2].

Therefore, I would recommend you to consider reaching out to Stack Exchange sites [3] (e.g. Server Fault [4] )where Google also participates that can help you find answers and troubleshoot problems. 

If you find any indication of a GCP specific issue, you may consider reporting [5] the issue with Issue Tracker with all the details [6] (omitting PII/sensitive information). You may also file a case with the GCP Support [7] and we will be more than happy to help. 

Regards

Anik

Reference:

[1]https://cloud.google.com/traffic-director/tutorials/set-up-internet-neg#migrate-to-internet-neg

[2] Discussions: Google Groups: https://cloud.google.com/support/docs/community#discussions_google_groups 

[3] Ask Technical Questions on Stack Exchange Sites: https://cloud.google.com/support/docs/stackexchange 

[4] Server Fault (A question and answer site for deploying and managing IT platforms): https://serverfault.com/questions/tagged/google-cloud-platform 

[5] Create new issue: https://cloud.google.com/support/docs/issue-trackers#trackers-list

[6] Report Issues with Issue Trackers: https://cloud.google.com/support/docs/issue-trackers

[7] GCP Support: https://cloud.google.com/support-hub