Create internal http(s) load balancer and backends inside shared vpc service projects
While using Shared VPC, GCP doesn't allow the creation of an internal http(s) load balancer and it's resources (backends) inside a service project. You must create everything inside the host project or in an isolated project with it's own VPC! This is unnaceptable, because the main purpose of using Shared VPCs is to isolate resources in service projects, keeping only common resources inside the host project. Imagine 30 or more service projects keeping all it's resources in the host project. It would be a huge mess. This situation breaks all the benefits of using Shared VPCs. External http(s) load balancers works fine. This is critical and the only workaround is to use a custom load balancer like NGinx inside a VM, losing all the benefits of scalability and usage of managed autoscaling groups. Please, review this as soon as possible. I don't think it's a feature request, it's a critical bug and an architecture problem.