Target groups provide a flexible way to manage load balancing nodes or targets.
...
| Expand |
|---|
| title | Click here to display details of create target group general info GCP |
|---|
|
As there are many types of target groups in Google Cloud, this page provides examples of two examples of target group types: instance groups and network endpoint groups. | Note |
|---|
In the platform, you cannot create target groups of these types: - MANAGED_INSTANCE_GROUP
- REGIONAL_MANAGED_INSTANCE_GROUP
But Abiquo onboards all target groups from GCP |
Unmanaged instance group example 
Field | Value |
|---|
Name | The Name of the target group. Google Cloud Platform will only accept the following characters: a-z, 0-9 and "-", and you cannot modify the name | Type | For a typical load balancer with VMs attached, create an UNMANAGED_INSTANCE_GROUP. - The other fields in this table are for an UNMANAGED_INSTANCE_GROUP
| | Named ports | Enter a port Name to identify each Port in the target group. Keep the names to enter them in load balancers | | Global network | The network that the VMs in the unmanaged instance group will use | | Subnet | A subnet of the global network that the VMs in the unmanaged instance group will belong to | Location | The public cloud region that the VMs will belong to in the global network | | Availability zone | The availability zone to use in the global network |
GCE IP port target group example  Abiquo recommends GCE_IP_PORT target groups. This screenshot shows an INTERNET_IP_PORT target group. The INTERNET_IP_PORT target group is only available with classic load balancers.
Field | Value |
|---|
Name | The Name of the target group. GCP will only accept the following characters: a-z, 0-9 and "-", and you cannot modify the name | Type | GCE_IP_PORT represents a Network Endpoint Group in GCP. It will load balance GCE IP addresses at the given port | | Port | The Port for communicating with the load balanced nodes |
|
...
| Expand |
|---|
| title | Click here to display details of create target group health check (for AWS and OCI) |
|---|
|
Field | Value |
|---|
Name | Name of the health check | Common protocols | Select one of the most common protocols to load presets | Protocol | The protocol with which the health check will be performed | Port | The port to which the health check will be performed | | Path | The server path to check. | | Status code | - OCI only: a request to the path of a healthy node will return this status code
| | Response body | - OCI only: Optional; a request to the path of a healthy node will return this response body
| | Interval (sec) | The interval in seconds between health checks | | Timeout (sec) | The timeout in seconds after which an attempted health check will be considered unsuccessful | | Attempts | The number of attempts before the health check will be considered unsuccessful |
|
Target group targets
In AWS, when you create the target group you can add targets.
...
Enter an IP address and port, or select a VM, and click Add. When you have finished adding all of the targets, to create the target group, click Save.
For more details see
GUI Edit target group Targets OCI GCP
| Expand |
|---|
| title | Click here to display details of edit target group targets OCI GCP |
|---|
|
Screenshot: Edit target group Targets OCI Image Added Screenshot: Edit target group Targets GCP VMs Image AddedScreenshot: Edit target group Targets GCP IP addresses and ports Image Added To add a target: - Select or enter a target and click Add
- When you have finished adding all of your targets, click Save
|