Managed instance group GCE – Static IP not working

google-cloud-platformgoogle-compute-enginestatic-ip

I have a problem with the ip of my instance group.

I have a managed instance group with (autoscaling enabled) on Google Compute Engine and I've setted a static IP on the 1st instance created. After a while (not a specific time) the IP changes and settings goes back to "Temporary ip".

There is a way to set static ip on a managed instance group and stay "safe" from ip change?

EDIT: Or there is a way to prevent the "delete" of the 1st instance created (the instance with the static IP)?

EDIT2: Think i can use a Load balancer setting manage group like backend, but i have a huge problem: I need to grab HTTP and RTMP requests, both from the same backend. I can't understand the correct configuration for this kind of things. Problem is that inside load balancer settings i can set only one backend service.
I need to set the same backend service (the same instance group) for both http and rtmp requests :/

Best Answer

For a managed group with auto-scaling enabled you should design or retrofit your application so that it is independent of specific instance properties that will not persist such as IP address or in-memory data. This is due to the stateless nature of the managed group as described in this document.

In such case, new instances can be created and others recreated following the configured instance template. For example, once utilization ( can be other set metric) decreases it should destroy unused instances and recreates new instance with changed IP addresses. Instances within managed groups are intended to be dynamically re-created, they get created from the instance template. That being said, due to the stateless nature of the managed group with auto-scaling enabled, even though you create instances with static IP it gets change every time with the auto-scaling operation.

Related Solutions

Google Cloud: Health Check is not removing failed instance from HTTP Load Balancer

health checks managed instance groups VS health checks load balancing

The health checks used by managed instance groups are the same health checks used by load balancing, with some differences in behavior. Health checks that you apply to load balancing services help a load balancer determine where to direct network traffic. These health checks do not cause Compute Engine to recreate instances. Health checks that you apply to managed instance groups will proactively signal to the managed instance group to delete and recreate instances if they become UNHEALTHY.

For the majority of scenarios, use separate health checks for load balancing and for monitoring managed instance groups. Health checking for load balancing can and should be more aggressive since these health checks determine whether an instance receives user traffic. Since customers might rely on your services, you want to catch non-responsive instances quickly so you can redirect traffic if necessary. In contrast, health checking for instance groups will cause Compute Engine proactively replace failing instances so you could create health checks that are more conservative than health checks for a load balancer.

https://cloud.google.com/compute/docs/instance-groups/creating-groups-of-managed-instances#monitoring_groups

Google cloud http(s) load balancer returning 502 despite healthy backend service

Traffic from the load balancer to your instance is not enabled by default. Unfortunately this is not well documented, and really, when you create a load balancer this should happen automatically.

Try adding this firewall rule the network that your load balancer and VMs are on:

130.211.0.0/22   tcp:1-5000   Apply to all targets

Best Answer

Related Solutions

Google Cloud: Health Check is not removing failed instance from HTTP Load Balancer

Google cloud http(s) load balancer returning 502 despite healthy backend service

Related Topic