Re: Do I Need To Download Pc Health Check
Tanesha Prately
Google Cloud provides health checking mechanisms thatdetermine whether backend instances respond properly to traffic. This documentdescribes how to create and use health checks for loadbalancers and Cloud Service Mesh.
You can also create a health check independently of load balancer configurationin the Google Cloud console. This is useful if you need to create yourhealth check first, or if you need to use a health check for multiple loadbalancers. You can create a health check using the Google Cloud console,the Google Cloud CLI, or the REST APIs.
Except for a health check's name, protocol, and scope, you can modify anyof the common flags, the port specificationflags, and other additional flags.To modify an existing health check, use the appropriate computehealth-checks updatecommand command.For flags that you omit, preconfigured settings are preserved.
Except for a health check's name, protocol, and scope, you can modify anyof the common flags, the port specificationflags, and other additional flagswith these API calls. Use patch API calls to preserve any preconfiguredsettings that are not explicitly set in the request.
If you create a health check by using the Google Cloud CLI or the API,you have two options to specify the health check's port. The following tableshows port specification options for valid load balancer and backendcombinations. The term instance group refers to unmanaged instance groups,zonal managed instance groups, or regional managed instance groups.
In addition to the common flags and port specification, you can use thefollowing optional flags for HTTP, HTTPS, and HTTP/2 health checks. This examplecreates an HTTP health check named hc-http-port-80 using port 80 with defaultinterval, timeout, and health threshold criteria.
In addition to the common flags and port specification, you can use thefollowing optional flags for SSL and TCP health checks. This example creates aTCP health check named hc-tcp-3268 using port 3268 with default interval,timeout, and health threshold criteria.
The --request and --response flags modify the success criteria for thehealth check probe. If you usethe --response flag, either by itself or in conjunction with the --requestflag, the response returned must exactly match the expected response string.
Your backend gRPC server must implement the gRPC health service as described inthe gRPC health checking protocol.Google Cloud sends a HealthCheckRequest message to your backends bycalling the Check method of the health service on your backend. The serviceparameter in the request is set to an empty string unless a gRPC service name isspecified.
A gRPC health check can check the status of a gRPC service. You can include astring, up to 1,024 ASCII characters long, that is the name of a particulargRPC service running on a backend VM or NEG. To do this, use the followingoptional flag for gRPC health checks:
If you create a health check against MyPackage.ServiceC, which is notregistered with the gRPC Health service, the health check probe returns thegRPC status NOT_FOUND, which is the equivalent of UNHEALTHY.
This section describes how to create, modify, and list legacy HTTP and HTTPShealth checks. You cannot convert a legacy health check to a health check, andyou cannot convert a health check to a legacy health check.
Although the Google Cloud console's health checks page lists and lets youedit both health checks and legacy health checks, you cannotcreate a new legacy health check from the Google Cloud console's healthchecks page.
You can create a legacy health check in the Google Cloud consoleonly while creating a target pool-basedexternal passthrough Network Load Balancer.To create the legacy health check by itself, use this section's gcloudor API instructions.
To modify a legacy HTTP health check, use the compute http-health-checksupdatecommand, replacing NAME with its name. When modifying a legacyhealth check with gcloud, preconfigured settings for flags you omit arepreserved. The OTHER_OPTIONS are the options described increating a legacy health check.
To modify a legacy HTTPS health check, use the compute https-health-checksupdatecommand, replacing NAME with its name. When modifying a legacyhealth check with gcloud, preconfigured settings for flags you omit arepreserved. The OTHER_OPTIONS are the options described increating a legacy health check.
Except for a legacy health check's name and type, you can modify any ofthe flags used for its creation. The patchAPI calls preserve any preconfigured settings that are not explicitly set inthe patch request.
You need to create ingress firewall rules applicable to all VMs being loadbalanced to allow traffic from health check prober IPranges. The followingexample creates a firewall rule that is applicable to VM instances identified bya specific target tag.
This example allows all TCP traffic from Google Cloud healthcheck systems to your VM instances. (TCP traffic includes SSL, HTTP, HTTPS, andHTTP/2 traffic.) If you prefer, you can specify ports along with the TCPprotocol; however, if you specify ports, your firewall rules might becomespecific to a particular health check. If you use tcp:80 for the protocol andport, this allows TCP traffic on port 80, so Google Cloud could contactyour VMs using HTTP on port 80, but it couldn't contact them using HTTPS onport 443.
Use the following gcloud command to create a firewall rule namedfw-allow-health-checks that lets incoming TCP connections, fromGoogle Cloud health check systems, to instances in yourVPC network with the allow-health-checks tag.Based on the load balancer type, a different set ofprobe IP ranges and firewall rulesis supported for IPv6 traffic to the backends. For example,2600:2d00:1:b029::/64 is used for global external Application Load Balancers andglobal external proxy Network Load Balancers.
To associate a health check with a new load balancer, refer to the setup guidefor the respective load balancer. This section describes how to associate ahealth check with an existing load balancer's backend service.
Identify the name and scope of the backend service. Theexternal passthrough Network Load Balancers, internal passthrough Network Load Balancers, regional internal proxy Network Load Balancers, andexternal proxy Network Load Balancers have only one backend service per loadbalancer. The external Application Load Balancers and internal Application Load Balancers have one or morebackend services associated with a single URL map.
To list backend services for external proxy Network Load Balancers using SSL, run thefollowing command. Backend services for these load balancers arealways global, regardless of the Network Service Tier.
To identify backend services for an external Application Load Balancer, first identify aURL map, and then describe the map. URL maps and backend services forexternal Application Load Balancers or cross-region internal Application Load Balancers are always global,regardless of the Network Service Tier. ReplaceURL_MAP_NAME with the name of the URL map. Thebackend services used by the load balancer are listed in the response.
To identify backend services for either a regional external Application Load Balancer ora regional internal Application Load Balancer, first identify a URL map, and then describe themap. Both URL maps and backend services for these load balancers are regional.Replace REGION_LIST with a comma-delimited list ofGoogle Cloud regions to query. ReplaceURL_MAP_NAME with the name of the URL map andREGION with its region. The backend services usedby the load balancer are listed in the response.
Associate a health check with the backend service by using the computebackend-servicesupdate command.Each backend service must reference a single health check. In thefollowing commands, replace BACKEND_SERVICE_NAME with the nameof the backend service, HEALTH_CHECK_NAME with the name of thehealth check, and, if necessary REGION with theGoogle Cloud region of the backend service, the health check, orboth.
To change the health check for an internal passthrough Network Load Balancer: Aninternal passthrough Network Load Balancer's backend service is regional. It can reference aglobal or regional health check. The following example shows aregional health check reference. If you're using a global health checkwith your internal passthrough Network Load Balancer, use --global-health-checks instead of--health-checks-region.
To change the health check for a backend service-basedexternal passthrough Network Load Balancer: An external passthrough Network Load Balancer's backend service isregional. It can reference a regional health check.
To change the health check for a global external proxy Network Load Balancer,classic proxy Network Load Balancer, global external Application Load Balancer, classic Application Load Balancer,or a cross-region internal Application Load Balancer: Both the backendservice and health check are global for these load balancers.Application Load Balancers can reference more thanone health check if it references more than one backend service.
To change the health check for either a regional external Application Load Balancer,a regional external proxy Network Load Balancer, a regional internal Application Load Balancer, or aregional internal proxy Network Load Balancer: Both the backendservice and health check are regional. Some load balancers mightreference more than one health check if they can reference more than onebackend service.
To associate a legacy health check with a new external passthrough Network Load Balancer, refer to Set upan external passthrough Network Load Balancer with a targetpool. This section describeshow to associate a legacy health check with a target pool-based external passthrough Network Load Balancer.
Associate the legacy health check with the target pool(s). In thefollowing commands, replace TARGET_POOL_NAME with the name ofthe target pool, REGION with its region, andLEGACY_CHECK_NAME with the name of the legacy healthcheck. The legacy health check must use the HTTP protocol.
d3342ee215