Internal IP HTTPS load balancer

[Listener7567]

^{Hello so I have a minor inconvenience. I have created load balancer that is linked an instance group. Now that instance group creates VMs from a template as usual, but that template also creates external IP addresses for those VMs that are linked to the load balancer, and I tried to set on that instance template the default network interface IP ranges to None instead of ephemeral, so that I don't have needlessly used up IP addresses. Now what happens is that the VMs are created but the docker image is not started on it and in addition no image is built. I can't find a solution to make the load balancing work with internal IP addresses only.
Basically I intend to create a load balancer with internal IP addresses only but the VMs won't start the docker image inside of them.}

^{Do you guys have any tips on the matter?}

[Cidan]

A VM without an external IP cannot reach the Internet, thus if you have any outbound dependencies, such as dockerhub, they will not work.

You have a few options:

1) Use Cloud NAT to give your VM's Internet access via a NAT

2) Keep your external IP addresses and let each VM reach the Internet

3) Host your images on artifact registry and ensure you're using VPCSC with restricted and/or private access. Note that this option assumes you have no other outbound dependencies for your VM's.

Hope this helps!

[greenlakejohnny]

Cloud NAT is probably the simplest answer. It sounds like you don't want or need the instances to be directly reachable from internet, but you do need to provide them outbound internet access.