GCE Instance Group
How can applications survive Zonal failures using Managed Instance Groups?
Create Regional Managed Instance Group (Regional MIGs or Multi-zone MIGs)
How can VM Instances be replaced when they are unhealthy (VM State not in RUNNING state or Application in VM is unhealthy)?
Configure health checks (Auto-Healing)
How can you preserve the VM State in MIG ?
Use Stateful MIG which will preserve VM State (Instance name, persistent disks attached to VM and Metadata) Recommended for stateful workloads like databases and data processing applications.
How can you group VMs of different configurations into an Instance Group ?
Use Unmanaged Instance Groups option
In which type of MIGs we use Instance Template as a mandatory option?
In both stateful - MIG and stateless - MIG, Instance templates are mandatory
How do you achieve high availability in MIG when there are hardware/software updates from GCP cloud platform perspective ?
As usual, use the instance template with availability policy with options
- Automatic Restart: Enabled
- On-Host Maintenance: Migrate
These features ensures live migration and automatic restart of VM Instances
What is the major feature difference between Stateful-MIG and Stateless-MIG?
Autoscaling not supported in Stateful – MIGs Rest all features auto-healing, auto-updating, multi-zone deployments are supported in both type of MIGs
Top comments (0)