Google Cloud Native is in preview. Google Cloud Classic is fully supported.
google-native.compute/alpha.RegionHealthCheck
Explore with Pulumi AI
Google Cloud Native is in preview. Google Cloud Classic is fully supported.
Creates a HealthCheck resource in the specified project using the data included in the request.
Create RegionHealthCheck Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new RegionHealthCheck(name: string, args: RegionHealthCheckArgs, opts?: CustomResourceOptions);@overload
def RegionHealthCheck(resource_name: str,
                      args: RegionHealthCheckArgs,
                      opts: Optional[ResourceOptions] = None)
@overload
def RegionHealthCheck(resource_name: str,
                      opts: Optional[ResourceOptions] = None,
                      region: Optional[str] = None,
                      project: Optional[str] = None,
                      unhealthy_threshold: Optional[int] = None,
                      name: Optional[str] = None,
                      http2_health_check: Optional[HTTP2HealthCheckArgs] = None,
                      http_health_check: Optional[HTTPHealthCheckArgs] = None,
                      https_health_check: Optional[HTTPSHealthCheckArgs] = None,
                      kind: Optional[str] = None,
                      log_config: Optional[HealthCheckLogConfigArgs] = None,
                      healthy_threshold: Optional[int] = None,
                      grpc_health_check: Optional[GRPCHealthCheckArgs] = None,
                      request_id: Optional[str] = None,
                      description: Optional[str] = None,
                      source_regions: Optional[Sequence[str]] = None,
                      ssl_health_check: Optional[SSLHealthCheckArgs] = None,
                      tcp_health_check: Optional[TCPHealthCheckArgs] = None,
                      timeout_sec: Optional[int] = None,
                      type: Optional[RegionHealthCheckType] = None,
                      udp_health_check: Optional[UDPHealthCheckArgs] = None,
                      check_interval_sec: Optional[int] = None)func NewRegionHealthCheck(ctx *Context, name string, args RegionHealthCheckArgs, opts ...ResourceOption) (*RegionHealthCheck, error)public RegionHealthCheck(string name, RegionHealthCheckArgs args, CustomResourceOptions? opts = null)
public RegionHealthCheck(String name, RegionHealthCheckArgs args)
public RegionHealthCheck(String name, RegionHealthCheckArgs args, CustomResourceOptions options)
type: google-native:compute/alpha:RegionHealthCheck
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.
Parameters
- name string
- The unique name of the resource.
- args RegionHealthCheckArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- resource_name str
- The unique name of the resource.
- args RegionHealthCheckArgs
- The arguments to resource properties.
- opts ResourceOptions
- Bag of options to control resource's behavior.
- ctx Context
- Context object for the current deployment.
- name string
- The unique name of the resource.
- args RegionHealthCheckArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args RegionHealthCheckArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args RegionHealthCheckArgs
- The arguments to resource properties.
- options CustomResourceOptions
- Bag of options to control resource's behavior.
Constructor example
The following reference example uses placeholder values for all input properties.
var regionHealthCheckResource = new GoogleNative.Compute.Alpha.RegionHealthCheck("regionHealthCheckResource", new()
{
    Region = "string",
    Project = "string",
    UnhealthyThreshold = 0,
    Name = "string",
    Http2HealthCheck = new GoogleNative.Compute.Alpha.Inputs.HTTP2HealthCheckArgs
    {
        Host = "string",
        Port = 0,
        PortName = "string",
        PortSpecification = GoogleNative.Compute.Alpha.HTTP2HealthCheckPortSpecification.UseFixedPort,
        ProxyHeader = GoogleNative.Compute.Alpha.HTTP2HealthCheckProxyHeader.None,
        RequestPath = "string",
        Response = "string",
        WeightReportMode = GoogleNative.Compute.Alpha.HTTP2HealthCheckWeightReportMode.Disable,
    },
    HttpHealthCheck = new GoogleNative.Compute.Alpha.Inputs.HTTPHealthCheckArgs
    {
        Host = "string",
        Port = 0,
        PortName = "string",
        PortSpecification = GoogleNative.Compute.Alpha.HTTPHealthCheckPortSpecification.UseFixedPort,
        ProxyHeader = GoogleNative.Compute.Alpha.HTTPHealthCheckProxyHeader.None,
        RequestPath = "string",
        Response = "string",
        WeightReportMode = GoogleNative.Compute.Alpha.HTTPHealthCheckWeightReportMode.Disable,
    },
    HttpsHealthCheck = new GoogleNative.Compute.Alpha.Inputs.HTTPSHealthCheckArgs
    {
        Host = "string",
        Port = 0,
        PortName = "string",
        PortSpecification = GoogleNative.Compute.Alpha.HTTPSHealthCheckPortSpecification.UseFixedPort,
        ProxyHeader = GoogleNative.Compute.Alpha.HTTPSHealthCheckProxyHeader.None,
        RequestPath = "string",
        Response = "string",
        WeightReportMode = GoogleNative.Compute.Alpha.HTTPSHealthCheckWeightReportMode.Disable,
    },
    Kind = "string",
    LogConfig = new GoogleNative.Compute.Alpha.Inputs.HealthCheckLogConfigArgs
    {
        Enable = false,
    },
    HealthyThreshold = 0,
    GrpcHealthCheck = new GoogleNative.Compute.Alpha.Inputs.GRPCHealthCheckArgs
    {
        GrpcServiceName = "string",
        Port = 0,
        PortName = "string",
        PortSpecification = GoogleNative.Compute.Alpha.GRPCHealthCheckPortSpecification.UseFixedPort,
    },
    RequestId = "string",
    Description = "string",
    SourceRegions = new[]
    {
        "string",
    },
    SslHealthCheck = new GoogleNative.Compute.Alpha.Inputs.SSLHealthCheckArgs
    {
        Port = 0,
        PortName = "string",
        PortSpecification = GoogleNative.Compute.Alpha.SSLHealthCheckPortSpecification.UseFixedPort,
        ProxyHeader = GoogleNative.Compute.Alpha.SSLHealthCheckProxyHeader.None,
        Request = "string",
        Response = "string",
    },
    TcpHealthCheck = new GoogleNative.Compute.Alpha.Inputs.TCPHealthCheckArgs
    {
        Port = 0,
        PortName = "string",
        PortSpecification = GoogleNative.Compute.Alpha.TCPHealthCheckPortSpecification.UseFixedPort,
        ProxyHeader = GoogleNative.Compute.Alpha.TCPHealthCheckProxyHeader.None,
        Request = "string",
        Response = "string",
    },
    TimeoutSec = 0,
    Type = GoogleNative.Compute.Alpha.RegionHealthCheckType.Grpc,
    UdpHealthCheck = new GoogleNative.Compute.Alpha.Inputs.UDPHealthCheckArgs
    {
        Port = 0,
        PortName = "string",
        Request = "string",
        Response = "string",
    },
    CheckIntervalSec = 0,
});
example, err := compute.NewRegionHealthCheck(ctx, "regionHealthCheckResource", &compute.RegionHealthCheckArgs{
	Region:             pulumi.String("string"),
	Project:            pulumi.String("string"),
	UnhealthyThreshold: pulumi.Int(0),
	Name:               pulumi.String("string"),
	Http2HealthCheck: &compute.HTTP2HealthCheckArgs{
		Host:              pulumi.String("string"),
		Port:              pulumi.Int(0),
		PortName:          pulumi.String("string"),
		PortSpecification: compute.HTTP2HealthCheckPortSpecificationUseFixedPort,
		ProxyHeader:       compute.HTTP2HealthCheckProxyHeaderNone,
		RequestPath:       pulumi.String("string"),
		Response:          pulumi.String("string"),
		WeightReportMode:  compute.HTTP2HealthCheckWeightReportModeDisable,
	},
	HttpHealthCheck: &compute.HTTPHealthCheckTypeArgs{
		Host:              pulumi.String("string"),
		Port:              pulumi.Int(0),
		PortName:          pulumi.String("string"),
		PortSpecification: compute.HTTPHealthCheckPortSpecificationUseFixedPort,
		ProxyHeader:       compute.HTTPHealthCheckProxyHeaderNone,
		RequestPath:       pulumi.String("string"),
		Response:          pulumi.String("string"),
		WeightReportMode:  compute.HTTPHealthCheckWeightReportModeDisable,
	},
	HttpsHealthCheck: &compute.HTTPSHealthCheckTypeArgs{
		Host:              pulumi.String("string"),
		Port:              pulumi.Int(0),
		PortName:          pulumi.String("string"),
		PortSpecification: compute.HTTPSHealthCheckPortSpecificationUseFixedPort,
		ProxyHeader:       compute.HTTPSHealthCheckProxyHeaderNone,
		RequestPath:       pulumi.String("string"),
		Response:          pulumi.String("string"),
		WeightReportMode:  compute.HTTPSHealthCheckWeightReportModeDisable,
	},
	Kind: pulumi.String("string"),
	LogConfig: &compute.HealthCheckLogConfigArgs{
		Enable: pulumi.Bool(false),
	},
	HealthyThreshold: pulumi.Int(0),
	GrpcHealthCheck: &compute.GRPCHealthCheckArgs{
		GrpcServiceName:   pulumi.String("string"),
		Port:              pulumi.Int(0),
		PortName:          pulumi.String("string"),
		PortSpecification: compute.GRPCHealthCheckPortSpecificationUseFixedPort,
	},
	RequestId:   pulumi.String("string"),
	Description: pulumi.String("string"),
	SourceRegions: pulumi.StringArray{
		pulumi.String("string"),
	},
	SslHealthCheck: &compute.SSLHealthCheckArgs{
		Port:              pulumi.Int(0),
		PortName:          pulumi.String("string"),
		PortSpecification: compute.SSLHealthCheckPortSpecificationUseFixedPort,
		ProxyHeader:       compute.SSLHealthCheckProxyHeaderNone,
		Request:           pulumi.String("string"),
		Response:          pulumi.String("string"),
	},
	TcpHealthCheck: &compute.TCPHealthCheckArgs{
		Port:              pulumi.Int(0),
		PortName:          pulumi.String("string"),
		PortSpecification: compute.TCPHealthCheckPortSpecificationUseFixedPort,
		ProxyHeader:       compute.TCPHealthCheckProxyHeaderNone,
		Request:           pulumi.String("string"),
		Response:          pulumi.String("string"),
	},
	TimeoutSec: pulumi.Int(0),
	Type:       compute.RegionHealthCheckTypeGrpc,
	UdpHealthCheck: &compute.UDPHealthCheckArgs{
		Port:     pulumi.Int(0),
		PortName: pulumi.String("string"),
		Request:  pulumi.String("string"),
		Response: pulumi.String("string"),
	},
	CheckIntervalSec: pulumi.Int(0),
})
var regionHealthCheckResource = new RegionHealthCheck("regionHealthCheckResource", RegionHealthCheckArgs.builder()
    .region("string")
    .project("string")
    .unhealthyThreshold(0)
    .name("string")
    .http2HealthCheck(HTTP2HealthCheckArgs.builder()
        .host("string")
        .port(0)
        .portName("string")
        .portSpecification("USE_FIXED_PORT")
        .proxyHeader("NONE")
        .requestPath("string")
        .response("string")
        .weightReportMode("DISABLE")
        .build())
    .httpHealthCheck(HTTPHealthCheckArgs.builder()
        .host("string")
        .port(0)
        .portName("string")
        .portSpecification("USE_FIXED_PORT")
        .proxyHeader("NONE")
        .requestPath("string")
        .response("string")
        .weightReportMode("DISABLE")
        .build())
    .httpsHealthCheck(HTTPSHealthCheckArgs.builder()
        .host("string")
        .port(0)
        .portName("string")
        .portSpecification("USE_FIXED_PORT")
        .proxyHeader("NONE")
        .requestPath("string")
        .response("string")
        .weightReportMode("DISABLE")
        .build())
    .kind("string")
    .logConfig(HealthCheckLogConfigArgs.builder()
        .enable(false)
        .build())
    .healthyThreshold(0)
    .grpcHealthCheck(GRPCHealthCheckArgs.builder()
        .grpcServiceName("string")
        .port(0)
        .portName("string")
        .portSpecification("USE_FIXED_PORT")
        .build())
    .requestId("string")
    .description("string")
    .sourceRegions("string")
    .sslHealthCheck(SSLHealthCheckArgs.builder()
        .port(0)
        .portName("string")
        .portSpecification("USE_FIXED_PORT")
        .proxyHeader("NONE")
        .request("string")
        .response("string")
        .build())
    .tcpHealthCheck(TCPHealthCheckArgs.builder()
        .port(0)
        .portName("string")
        .portSpecification("USE_FIXED_PORT")
        .proxyHeader("NONE")
        .request("string")
        .response("string")
        .build())
    .timeoutSec(0)
    .type("GRPC")
    .udpHealthCheck(UDPHealthCheckArgs.builder()
        .port(0)
        .portName("string")
        .request("string")
        .response("string")
        .build())
    .checkIntervalSec(0)
    .build());
region_health_check_resource = google_native.compute.alpha.RegionHealthCheck("regionHealthCheckResource",
    region="string",
    project="string",
    unhealthy_threshold=0,
    name="string",
    http2_health_check={
        "host": "string",
        "port": 0,
        "port_name": "string",
        "port_specification": google_native.compute.alpha.HTTP2HealthCheckPortSpecification.USE_FIXED_PORT,
        "proxy_header": google_native.compute.alpha.HTTP2HealthCheckProxyHeader.NONE,
        "request_path": "string",
        "response": "string",
        "weight_report_mode": google_native.compute.alpha.HTTP2HealthCheckWeightReportMode.DISABLE,
    },
    http_health_check={
        "host": "string",
        "port": 0,
        "port_name": "string",
        "port_specification": google_native.compute.alpha.HTTPHealthCheckPortSpecification.USE_FIXED_PORT,
        "proxy_header": google_native.compute.alpha.HTTPHealthCheckProxyHeader.NONE,
        "request_path": "string",
        "response": "string",
        "weight_report_mode": google_native.compute.alpha.HTTPHealthCheckWeightReportMode.DISABLE,
    },
    https_health_check={
        "host": "string",
        "port": 0,
        "port_name": "string",
        "port_specification": google_native.compute.alpha.HTTPSHealthCheckPortSpecification.USE_FIXED_PORT,
        "proxy_header": google_native.compute.alpha.HTTPSHealthCheckProxyHeader.NONE,
        "request_path": "string",
        "response": "string",
        "weight_report_mode": google_native.compute.alpha.HTTPSHealthCheckWeightReportMode.DISABLE,
    },
    kind="string",
    log_config={
        "enable": False,
    },
    healthy_threshold=0,
    grpc_health_check={
        "grpc_service_name": "string",
        "port": 0,
        "port_name": "string",
        "port_specification": google_native.compute.alpha.GRPCHealthCheckPortSpecification.USE_FIXED_PORT,
    },
    request_id="string",
    description="string",
    source_regions=["string"],
    ssl_health_check={
        "port": 0,
        "port_name": "string",
        "port_specification": google_native.compute.alpha.SSLHealthCheckPortSpecification.USE_FIXED_PORT,
        "proxy_header": google_native.compute.alpha.SSLHealthCheckProxyHeader.NONE,
        "request": "string",
        "response": "string",
    },
    tcp_health_check={
        "port": 0,
        "port_name": "string",
        "port_specification": google_native.compute.alpha.TCPHealthCheckPortSpecification.USE_FIXED_PORT,
        "proxy_header": google_native.compute.alpha.TCPHealthCheckProxyHeader.NONE,
        "request": "string",
        "response": "string",
    },
    timeout_sec=0,
    type=google_native.compute.alpha.RegionHealthCheckType.GRPC,
    udp_health_check={
        "port": 0,
        "port_name": "string",
        "request": "string",
        "response": "string",
    },
    check_interval_sec=0)
const regionHealthCheckResource = new google_native.compute.alpha.RegionHealthCheck("regionHealthCheckResource", {
    region: "string",
    project: "string",
    unhealthyThreshold: 0,
    name: "string",
    http2HealthCheck: {
        host: "string",
        port: 0,
        portName: "string",
        portSpecification: google_native.compute.alpha.HTTP2HealthCheckPortSpecification.UseFixedPort,
        proxyHeader: google_native.compute.alpha.HTTP2HealthCheckProxyHeader.None,
        requestPath: "string",
        response: "string",
        weightReportMode: google_native.compute.alpha.HTTP2HealthCheckWeightReportMode.Disable,
    },
    httpHealthCheck: {
        host: "string",
        port: 0,
        portName: "string",
        portSpecification: google_native.compute.alpha.HTTPHealthCheckPortSpecification.UseFixedPort,
        proxyHeader: google_native.compute.alpha.HTTPHealthCheckProxyHeader.None,
        requestPath: "string",
        response: "string",
        weightReportMode: google_native.compute.alpha.HTTPHealthCheckWeightReportMode.Disable,
    },
    httpsHealthCheck: {
        host: "string",
        port: 0,
        portName: "string",
        portSpecification: google_native.compute.alpha.HTTPSHealthCheckPortSpecification.UseFixedPort,
        proxyHeader: google_native.compute.alpha.HTTPSHealthCheckProxyHeader.None,
        requestPath: "string",
        response: "string",
        weightReportMode: google_native.compute.alpha.HTTPSHealthCheckWeightReportMode.Disable,
    },
    kind: "string",
    logConfig: {
        enable: false,
    },
    healthyThreshold: 0,
    grpcHealthCheck: {
        grpcServiceName: "string",
        port: 0,
        portName: "string",
        portSpecification: google_native.compute.alpha.GRPCHealthCheckPortSpecification.UseFixedPort,
    },
    requestId: "string",
    description: "string",
    sourceRegions: ["string"],
    sslHealthCheck: {
        port: 0,
        portName: "string",
        portSpecification: google_native.compute.alpha.SSLHealthCheckPortSpecification.UseFixedPort,
        proxyHeader: google_native.compute.alpha.SSLHealthCheckProxyHeader.None,
        request: "string",
        response: "string",
    },
    tcpHealthCheck: {
        port: 0,
        portName: "string",
        portSpecification: google_native.compute.alpha.TCPHealthCheckPortSpecification.UseFixedPort,
        proxyHeader: google_native.compute.alpha.TCPHealthCheckProxyHeader.None,
        request: "string",
        response: "string",
    },
    timeoutSec: 0,
    type: google_native.compute.alpha.RegionHealthCheckType.Grpc,
    udpHealthCheck: {
        port: 0,
        portName: "string",
        request: "string",
        response: "string",
    },
    checkIntervalSec: 0,
});
type: google-native:compute/alpha:RegionHealthCheck
properties:
    checkIntervalSec: 0
    description: string
    grpcHealthCheck:
        grpcServiceName: string
        port: 0
        portName: string
        portSpecification: USE_FIXED_PORT
    healthyThreshold: 0
    http2HealthCheck:
        host: string
        port: 0
        portName: string
        portSpecification: USE_FIXED_PORT
        proxyHeader: NONE
        requestPath: string
        response: string
        weightReportMode: DISABLE
    httpHealthCheck:
        host: string
        port: 0
        portName: string
        portSpecification: USE_FIXED_PORT
        proxyHeader: NONE
        requestPath: string
        response: string
        weightReportMode: DISABLE
    httpsHealthCheck:
        host: string
        port: 0
        portName: string
        portSpecification: USE_FIXED_PORT
        proxyHeader: NONE
        requestPath: string
        response: string
        weightReportMode: DISABLE
    kind: string
    logConfig:
        enable: false
    name: string
    project: string
    region: string
    requestId: string
    sourceRegions:
        - string
    sslHealthCheck:
        port: 0
        portName: string
        portSpecification: USE_FIXED_PORT
        proxyHeader: NONE
        request: string
        response: string
    tcpHealthCheck:
        port: 0
        portName: string
        portSpecification: USE_FIXED_PORT
        proxyHeader: NONE
        request: string
        response: string
    timeoutSec: 0
    type: GRPC
    udpHealthCheck:
        port: 0
        portName: string
        request: string
        response: string
    unhealthyThreshold: 0
RegionHealthCheck Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.
Inputs
In Python, inputs that are objects can be passed either as argument classes or as dictionary literals.
The RegionHealthCheck resource accepts the following input properties:
- Region string
- CheckInterval intSec 
- How often (in seconds) to send a health check. The default value is 5 seconds.
- Description string
- An optional description of this resource. Provide this property when you create the resource.
- GrpcHealth Pulumi.Check Google Native. Compute. Alpha. Inputs. GRPCHealth Check 
- HealthyThreshold int
- A so-far unhealthy instance will be marked healthy after this many consecutive successes. The default value is 2.
- Http2HealthCheck Pulumi.Google Native. Compute. Alpha. Inputs. HTTP2Health Check 
- HttpHealth Pulumi.Check Google Native. Compute. Alpha. Inputs. HTTPHealth Check 
- HttpsHealth Pulumi.Check Google Native. Compute. Alpha. Inputs. HTTPSHealth Check 
- Kind string
- Type of the resource.
- LogConfig Pulumi.Google Native. Compute. Alpha. Inputs. Health Check Log Config 
- Configure logging on this health check.
- Name string
- Name of the resource. Provided by the client when the resource is created. The name must be 1-63 characters long, and comply with RFC1035. For example, a name that is 1-63 characters long, matches the regular expression [a-z]([-a-z0-9]*[a-z0-9])?, and otherwise complies with RFC1035. This regular expression describes a name where the first character is a lowercase letter, and all following characters are a dash, lowercase letter, or digit, except the last character, which isn't a dash.
- Project string
- RequestId string
- An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported ( 00000000-0000-0000-0000-000000000000).
- SourceRegions List<string>
- The list of cloud regions from which health checks are performed. If any regions are specified, then exactly 3 regions should be specified. The region names must be valid names of GCP regions. This can only be set for global health check. If this list is non-empty, then there are restrictions on what other health check fields are supported and what other resources can use this health check: - SSL, HTTP2, and GRPC protocols are not supported. - The TCP request field is not supported. - The proxyHeader field for HTTP, HTTPS, and TCP is not supported. - The checkIntervalSec field must be at least 30. - The health check cannot be used with BackendService nor with managed instance group auto-healing.
- SslHealth Pulumi.Check Google Native. Compute. Alpha. Inputs. SSLHealth Check 
- TcpHealth Pulumi.Check Google Native. Compute. Alpha. Inputs. TCPHealth Check 
- TimeoutSec int
- How long (in seconds) to wait before claiming failure. The default value is 5 seconds. It is invalid for timeoutSec to have greater value than checkIntervalSec.
- Type
Pulumi.Google Native. Compute. Alpha. Region Health Check Type 
- Specifies the type of the healthCheck, either TCP, SSL, HTTP, HTTPS, HTTP2 or GRPC. Exactly one of the protocol-specific health check fields must be specified, which must match type field.
- UdpHealth Pulumi.Check Google Native. Compute. Alpha. Inputs. UDPHealth Check 
- UnhealthyThreshold int
- A so-far healthy instance will be marked unhealthy after this many consecutive failures. The default value is 2.
- Region string
- CheckInterval intSec 
- How often (in seconds) to send a health check. The default value is 5 seconds.
- Description string
- An optional description of this resource. Provide this property when you create the resource.
- GrpcHealth GRPCHealthCheck Check Args 
- HealthyThreshold int
- A so-far unhealthy instance will be marked healthy after this many consecutive successes. The default value is 2.
- Http2HealthCheck HTTP2HealthCheck Args 
- HttpHealth HTTPHealthCheck Check Type Args 
- HttpsHealth HTTPSHealthCheck Check Type Args 
- Kind string
- Type of the resource.
- LogConfig HealthCheck Log Config Args 
- Configure logging on this health check.
- Name string
- Name of the resource. Provided by the client when the resource is created. The name must be 1-63 characters long, and comply with RFC1035. For example, a name that is 1-63 characters long, matches the regular expression [a-z]([-a-z0-9]*[a-z0-9])?, and otherwise complies with RFC1035. This regular expression describes a name where the first character is a lowercase letter, and all following characters are a dash, lowercase letter, or digit, except the last character, which isn't a dash.
- Project string
- RequestId string
- An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported ( 00000000-0000-0000-0000-000000000000).
- SourceRegions []string
- The list of cloud regions from which health checks are performed. If any regions are specified, then exactly 3 regions should be specified. The region names must be valid names of GCP regions. This can only be set for global health check. If this list is non-empty, then there are restrictions on what other health check fields are supported and what other resources can use this health check: - SSL, HTTP2, and GRPC protocols are not supported. - The TCP request field is not supported. - The proxyHeader field for HTTP, HTTPS, and TCP is not supported. - The checkIntervalSec field must be at least 30. - The health check cannot be used with BackendService nor with managed instance group auto-healing.
- SslHealth SSLHealthCheck Check Args 
- TcpHealth TCPHealthCheck Check Args 
- TimeoutSec int
- How long (in seconds) to wait before claiming failure. The default value is 5 seconds. It is invalid for timeoutSec to have greater value than checkIntervalSec.
- Type
RegionHealth Check Type 
- Specifies the type of the healthCheck, either TCP, SSL, HTTP, HTTPS, HTTP2 or GRPC. Exactly one of the protocol-specific health check fields must be specified, which must match type field.
- UdpHealth UDPHealthCheck Check Args 
- UnhealthyThreshold int
- A so-far healthy instance will be marked unhealthy after this many consecutive failures. The default value is 2.
- region String
- checkInterval IntegerSec 
- How often (in seconds) to send a health check. The default value is 5 seconds.
- description String
- An optional description of this resource. Provide this property when you create the resource.
- grpcHealth GRPCHealthCheck Check 
- healthyThreshold Integer
- A so-far unhealthy instance will be marked healthy after this many consecutive successes. The default value is 2.
- http2HealthCheck HTTP2HealthCheck 
- httpHealth HTTPHealthCheck Check 
- httpsHealth HTTPSHealthCheck Check 
- kind String
- Type of the resource.
- logConfig HealthCheck Log Config 
- Configure logging on this health check.
- name String
- Name of the resource. Provided by the client when the resource is created. The name must be 1-63 characters long, and comply with RFC1035. For example, a name that is 1-63 characters long, matches the regular expression [a-z]([-a-z0-9]*[a-z0-9])?, and otherwise complies with RFC1035. This regular expression describes a name where the first character is a lowercase letter, and all following characters are a dash, lowercase letter, or digit, except the last character, which isn't a dash.
- project String
- requestId String
- An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported ( 00000000-0000-0000-0000-000000000000).
- sourceRegions List<String>
- The list of cloud regions from which health checks are performed. If any regions are specified, then exactly 3 regions should be specified. The region names must be valid names of GCP regions. This can only be set for global health check. If this list is non-empty, then there are restrictions on what other health check fields are supported and what other resources can use this health check: - SSL, HTTP2, and GRPC protocols are not supported. - The TCP request field is not supported. - The proxyHeader field for HTTP, HTTPS, and TCP is not supported. - The checkIntervalSec field must be at least 30. - The health check cannot be used with BackendService nor with managed instance group auto-healing.
- sslHealth SSLHealthCheck Check 
- tcpHealth TCPHealthCheck Check 
- timeoutSec Integer
- How long (in seconds) to wait before claiming failure. The default value is 5 seconds. It is invalid for timeoutSec to have greater value than checkIntervalSec.
- type
RegionHealth Check Type 
- Specifies the type of the healthCheck, either TCP, SSL, HTTP, HTTPS, HTTP2 or GRPC. Exactly one of the protocol-specific health check fields must be specified, which must match type field.
- udpHealth UDPHealthCheck Check 
- unhealthyThreshold Integer
- A so-far healthy instance will be marked unhealthy after this many consecutive failures. The default value is 2.
- region string
- checkInterval numberSec 
- How often (in seconds) to send a health check. The default value is 5 seconds.
- description string
- An optional description of this resource. Provide this property when you create the resource.
- grpcHealth GRPCHealthCheck Check 
- healthyThreshold number
- A so-far unhealthy instance will be marked healthy after this many consecutive successes. The default value is 2.
- http2HealthCheck HTTP2HealthCheck 
- httpHealth HTTPHealthCheck Check 
- httpsHealth HTTPSHealthCheck Check 
- kind string
- Type of the resource.
- logConfig HealthCheck Log Config 
- Configure logging on this health check.
- name string
- Name of the resource. Provided by the client when the resource is created. The name must be 1-63 characters long, and comply with RFC1035. For example, a name that is 1-63 characters long, matches the regular expression [a-z]([-a-z0-9]*[a-z0-9])?, and otherwise complies with RFC1035. This regular expression describes a name where the first character is a lowercase letter, and all following characters are a dash, lowercase letter, or digit, except the last character, which isn't a dash.
- project string
- requestId string
- An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported ( 00000000-0000-0000-0000-000000000000).
- sourceRegions string[]
- The list of cloud regions from which health checks are performed. If any regions are specified, then exactly 3 regions should be specified. The region names must be valid names of GCP regions. This can only be set for global health check. If this list is non-empty, then there are restrictions on what other health check fields are supported and what other resources can use this health check: - SSL, HTTP2, and GRPC protocols are not supported. - The TCP request field is not supported. - The proxyHeader field for HTTP, HTTPS, and TCP is not supported. - The checkIntervalSec field must be at least 30. - The health check cannot be used with BackendService nor with managed instance group auto-healing.
- sslHealth SSLHealthCheck Check 
- tcpHealth TCPHealthCheck Check 
- timeoutSec number
- How long (in seconds) to wait before claiming failure. The default value is 5 seconds. It is invalid for timeoutSec to have greater value than checkIntervalSec.
- type
RegionHealth Check Type 
- Specifies the type of the healthCheck, either TCP, SSL, HTTP, HTTPS, HTTP2 or GRPC. Exactly one of the protocol-specific health check fields must be specified, which must match type field.
- udpHealth UDPHealthCheck Check 
- unhealthyThreshold number
- A so-far healthy instance will be marked unhealthy after this many consecutive failures. The default value is 2.
- region str
- check_interval_ intsec 
- How often (in seconds) to send a health check. The default value is 5 seconds.
- description str
- An optional description of this resource. Provide this property when you create the resource.
- grpc_health_ GRPCHealthcheck Check Args 
- healthy_threshold int
- A so-far unhealthy instance will be marked healthy after this many consecutive successes. The default value is 2.
- http2_health_ HTTP2Healthcheck Check Args 
- http_health_ HTTPHealthcheck Check Args 
- https_health_ HTTPSHealthcheck Check Args 
- kind str
- Type of the resource.
- log_config HealthCheck Log Config Args 
- Configure logging on this health check.
- name str
- Name of the resource. Provided by the client when the resource is created. The name must be 1-63 characters long, and comply with RFC1035. For example, a name that is 1-63 characters long, matches the regular expression [a-z]([-a-z0-9]*[a-z0-9])?, and otherwise complies with RFC1035. This regular expression describes a name where the first character is a lowercase letter, and all following characters are a dash, lowercase letter, or digit, except the last character, which isn't a dash.
- project str
- request_id str
- An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported ( 00000000-0000-0000-0000-000000000000).
- source_regions Sequence[str]
- The list of cloud regions from which health checks are performed. If any regions are specified, then exactly 3 regions should be specified. The region names must be valid names of GCP regions. This can only be set for global health check. If this list is non-empty, then there are restrictions on what other health check fields are supported and what other resources can use this health check: - SSL, HTTP2, and GRPC protocols are not supported. - The TCP request field is not supported. - The proxyHeader field for HTTP, HTTPS, and TCP is not supported. - The checkIntervalSec field must be at least 30. - The health check cannot be used with BackendService nor with managed instance group auto-healing.
- ssl_health_ SSLHealthcheck Check Args 
- tcp_health_ TCPHealthcheck Check Args 
- timeout_sec int
- How long (in seconds) to wait before claiming failure. The default value is 5 seconds. It is invalid for timeoutSec to have greater value than checkIntervalSec.
- type
RegionHealth Check Type 
- Specifies the type of the healthCheck, either TCP, SSL, HTTP, HTTPS, HTTP2 or GRPC. Exactly one of the protocol-specific health check fields must be specified, which must match type field.
- udp_health_ UDPHealthcheck Check Args 
- unhealthy_threshold int
- A so-far healthy instance will be marked unhealthy after this many consecutive failures. The default value is 2.
- region String
- checkInterval NumberSec 
- How often (in seconds) to send a health check. The default value is 5 seconds.
- description String
- An optional description of this resource. Provide this property when you create the resource.
- grpcHealth Property MapCheck 
- healthyThreshold Number
- A so-far unhealthy instance will be marked healthy after this many consecutive successes. The default value is 2.
- http2HealthCheck Property Map
- httpHealth Property MapCheck 
- httpsHealth Property MapCheck 
- kind String
- Type of the resource.
- logConfig Property Map
- Configure logging on this health check.
- name String
- Name of the resource. Provided by the client when the resource is created. The name must be 1-63 characters long, and comply with RFC1035. For example, a name that is 1-63 characters long, matches the regular expression [a-z]([-a-z0-9]*[a-z0-9])?, and otherwise complies with RFC1035. This regular expression describes a name where the first character is a lowercase letter, and all following characters are a dash, lowercase letter, or digit, except the last character, which isn't a dash.
- project String
- requestId String
- An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported ( 00000000-0000-0000-0000-000000000000).
- sourceRegions List<String>
- The list of cloud regions from which health checks are performed. If any regions are specified, then exactly 3 regions should be specified. The region names must be valid names of GCP regions. This can only be set for global health check. If this list is non-empty, then there are restrictions on what other health check fields are supported and what other resources can use this health check: - SSL, HTTP2, and GRPC protocols are not supported. - The TCP request field is not supported. - The proxyHeader field for HTTP, HTTPS, and TCP is not supported. - The checkIntervalSec field must be at least 30. - The health check cannot be used with BackendService nor with managed instance group auto-healing.
- sslHealth Property MapCheck 
- tcpHealth Property MapCheck 
- timeoutSec Number
- How long (in seconds) to wait before claiming failure. The default value is 5 seconds. It is invalid for timeoutSec to have greater value than checkIntervalSec.
- type "GRPC" | "HTTP" | "HTTP2" | "HTTPS" | "INVALID" | "SSL" | "TCP" | "UDP"
- Specifies the type of the healthCheck, either TCP, SSL, HTTP, HTTPS, HTTP2 or GRPC. Exactly one of the protocol-specific health check fields must be specified, which must match type field.
- udpHealth Property MapCheck 
- unhealthyThreshold Number
- A so-far healthy instance will be marked unhealthy after this many consecutive failures. The default value is 2.
Outputs
All input properties are implicitly available as output properties. Additionally, the RegionHealthCheck resource produces the following output properties:
- CreationTimestamp string
- Creation timestamp in 3339 text format.
- Id string
- The provider-assigned unique ID for this managed resource.
- SelfLink string
- Server-defined URL for the resource.
- SelfLink stringWith Id 
- Server-defined URL for this resource with the resource id.
- CreationTimestamp string
- Creation timestamp in 3339 text format.
- Id string
- The provider-assigned unique ID for this managed resource.
- SelfLink string
- Server-defined URL for the resource.
- SelfLink stringWith Id 
- Server-defined URL for this resource with the resource id.
- creationTimestamp String
- Creation timestamp in 3339 text format.
- id String
- The provider-assigned unique ID for this managed resource.
- selfLink String
- Server-defined URL for the resource.
- selfLink StringWith Id 
- Server-defined URL for this resource with the resource id.
- creationTimestamp string
- Creation timestamp in 3339 text format.
- id string
- The provider-assigned unique ID for this managed resource.
- selfLink string
- Server-defined URL for the resource.
- selfLink stringWith Id 
- Server-defined URL for this resource with the resource id.
- creation_timestamp str
- Creation timestamp in 3339 text format.
- id str
- The provider-assigned unique ID for this managed resource.
- self_link str
- Server-defined URL for the resource.
- self_link_ strwith_ id 
- Server-defined URL for this resource with the resource id.
- creationTimestamp String
- Creation timestamp in 3339 text format.
- id String
- The provider-assigned unique ID for this managed resource.
- selfLink String
- Server-defined URL for the resource.
- selfLink StringWith Id 
- Server-defined URL for this resource with the resource id.
Supporting Types
GRPCHealthCheck, GRPCHealthCheckArgs    
- GrpcService stringName 
- The gRPC service name for the health check. This field is optional. The value of grpc_service_name has the following meanings by convention: - Empty service_name means the overall status of all services at the backend. - Non-empty service_name means the health of that gRPC service, as defined by the owner of the service. The grpc_service_name can only be ASCII.
- Port int
- The TCP port number to which the health check prober sends packets. Valid values are 1 through 65535.
- PortName string
- Not supported.
- PortSpecification Pulumi.Google Native. Compute. Alpha. GRPCHealth Check Port Specification 
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- GrpcService stringName 
- The gRPC service name for the health check. This field is optional. The value of grpc_service_name has the following meanings by convention: - Empty service_name means the overall status of all services at the backend. - Non-empty service_name means the health of that gRPC service, as defined by the owner of the service. The grpc_service_name can only be ASCII.
- Port int
- The TCP port number to which the health check prober sends packets. Valid values are 1 through 65535.
- PortName string
- Not supported.
- PortSpecification GRPCHealthCheck Port Specification 
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- grpcService StringName 
- The gRPC service name for the health check. This field is optional. The value of grpc_service_name has the following meanings by convention: - Empty service_name means the overall status of all services at the backend. - Non-empty service_name means the health of that gRPC service, as defined by the owner of the service. The grpc_service_name can only be ASCII.
- port Integer
- The TCP port number to which the health check prober sends packets. Valid values are 1 through 65535.
- portName String
- Not supported.
- portSpecification GRPCHealthCheck Port Specification 
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- grpcService stringName 
- The gRPC service name for the health check. This field is optional. The value of grpc_service_name has the following meanings by convention: - Empty service_name means the overall status of all services at the backend. - Non-empty service_name means the health of that gRPC service, as defined by the owner of the service. The grpc_service_name can only be ASCII.
- port number
- The TCP port number to which the health check prober sends packets. Valid values are 1 through 65535.
- portName string
- Not supported.
- portSpecification GRPCHealthCheck Port Specification 
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- grpc_service_ strname 
- The gRPC service name for the health check. This field is optional. The value of grpc_service_name has the following meanings by convention: - Empty service_name means the overall status of all services at the backend. - Non-empty service_name means the health of that gRPC service, as defined by the owner of the service. The grpc_service_name can only be ASCII.
- port int
- The TCP port number to which the health check prober sends packets. Valid values are 1 through 65535.
- port_name str
- Not supported.
- port_specification GRPCHealthCheck Port Specification 
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- grpcService StringName 
- The gRPC service name for the health check. This field is optional. The value of grpc_service_name has the following meanings by convention: - Empty service_name means the overall status of all services at the backend. - Non-empty service_name means the health of that gRPC service, as defined by the owner of the service. The grpc_service_name can only be ASCII.
- port Number
- The TCP port number to which the health check prober sends packets. Valid values are 1 through 65535.
- portName String
- Not supported.
- portSpecification "USE_FIXED_PORT" | "USE_NAMED_PORT" | "USE_SERVING_PORT"
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
GRPCHealthCheckPortSpecification, GRPCHealthCheckPortSpecificationArgs        
- UseFixed Port 
- USE_FIXED_PORTThe port number in the health check's port is used for health checking. Applies to network endpoint group and instance group backends.
- UseNamed Port 
- USE_NAMED_PORTNot supported.
- UseServing Port 
- USE_SERVING_PORTFor network endpoint group backends, the health check uses the port number specified on each endpoint in the network endpoint group. For instance group backends, the health check uses the port number specified for the backend service's named port defined in the instance group's named ports.
- GRPCHealthCheck Port Specification Use Fixed Port 
- USE_FIXED_PORTThe port number in the health check's port is used for health checking. Applies to network endpoint group and instance group backends.
- GRPCHealthCheck Port Specification Use Named Port 
- USE_NAMED_PORTNot supported.
- GRPCHealthCheck Port Specification Use Serving Port 
- USE_SERVING_PORTFor network endpoint group backends, the health check uses the port number specified on each endpoint in the network endpoint group. For instance group backends, the health check uses the port number specified for the backend service's named port defined in the instance group's named ports.
- UseFixed Port 
- USE_FIXED_PORTThe port number in the health check's port is used for health checking. Applies to network endpoint group and instance group backends.
- UseNamed Port 
- USE_NAMED_PORTNot supported.
- UseServing Port 
- USE_SERVING_PORTFor network endpoint group backends, the health check uses the port number specified on each endpoint in the network endpoint group. For instance group backends, the health check uses the port number specified for the backend service's named port defined in the instance group's named ports.
- UseFixed Port 
- USE_FIXED_PORTThe port number in the health check's port is used for health checking. Applies to network endpoint group and instance group backends.
- UseNamed Port 
- USE_NAMED_PORTNot supported.
- UseServing Port 
- USE_SERVING_PORTFor network endpoint group backends, the health check uses the port number specified on each endpoint in the network endpoint group. For instance group backends, the health check uses the port number specified for the backend service's named port defined in the instance group's named ports.
- USE_FIXED_PORT
- USE_FIXED_PORTThe port number in the health check's port is used for health checking. Applies to network endpoint group and instance group backends.
- USE_NAMED_PORT
- USE_NAMED_PORTNot supported.
- USE_SERVING_PORT
- USE_SERVING_PORTFor network endpoint group backends, the health check uses the port number specified on each endpoint in the network endpoint group. For instance group backends, the health check uses the port number specified for the backend service's named port defined in the instance group's named ports.
- "USE_FIXED_PORT"
- USE_FIXED_PORTThe port number in the health check's port is used for health checking. Applies to network endpoint group and instance group backends.
- "USE_NAMED_PORT"
- USE_NAMED_PORTNot supported.
- "USE_SERVING_PORT"
- USE_SERVING_PORTFor network endpoint group backends, the health check uses the port number specified on each endpoint in the network endpoint group. For instance group backends, the health check uses the port number specified for the backend service's named port defined in the instance group's named ports.
GRPCHealthCheckResponse, GRPCHealthCheckResponseArgs      
- GrpcService stringName 
- The gRPC service name for the health check. This field is optional. The value of grpc_service_name has the following meanings by convention: - Empty service_name means the overall status of all services at the backend. - Non-empty service_name means the health of that gRPC service, as defined by the owner of the service. The grpc_service_name can only be ASCII.
- Port int
- The TCP port number to which the health check prober sends packets. Valid values are 1 through 65535.
- PortName string
- Not supported.
- PortSpecification string
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- GrpcService stringName 
- The gRPC service name for the health check. This field is optional. The value of grpc_service_name has the following meanings by convention: - Empty service_name means the overall status of all services at the backend. - Non-empty service_name means the health of that gRPC service, as defined by the owner of the service. The grpc_service_name can only be ASCII.
- Port int
- The TCP port number to which the health check prober sends packets. Valid values are 1 through 65535.
- PortName string
- Not supported.
- PortSpecification string
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- grpcService StringName 
- The gRPC service name for the health check. This field is optional. The value of grpc_service_name has the following meanings by convention: - Empty service_name means the overall status of all services at the backend. - Non-empty service_name means the health of that gRPC service, as defined by the owner of the service. The grpc_service_name can only be ASCII.
- port Integer
- The TCP port number to which the health check prober sends packets. Valid values are 1 through 65535.
- portName String
- Not supported.
- portSpecification String
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- grpcService stringName 
- The gRPC service name for the health check. This field is optional. The value of grpc_service_name has the following meanings by convention: - Empty service_name means the overall status of all services at the backend. - Non-empty service_name means the health of that gRPC service, as defined by the owner of the service. The grpc_service_name can only be ASCII.
- port number
- The TCP port number to which the health check prober sends packets. Valid values are 1 through 65535.
- portName string
- Not supported.
- portSpecification string
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- grpc_service_ strname 
- The gRPC service name for the health check. This field is optional. The value of grpc_service_name has the following meanings by convention: - Empty service_name means the overall status of all services at the backend. - Non-empty service_name means the health of that gRPC service, as defined by the owner of the service. The grpc_service_name can only be ASCII.
- port int
- The TCP port number to which the health check prober sends packets. Valid values are 1 through 65535.
- port_name str
- Not supported.
- port_specification str
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- grpcService StringName 
- The gRPC service name for the health check. This field is optional. The value of grpc_service_name has the following meanings by convention: - Empty service_name means the overall status of all services at the backend. - Non-empty service_name means the health of that gRPC service, as defined by the owner of the service. The grpc_service_name can only be ASCII.
- port Number
- The TCP port number to which the health check prober sends packets. Valid values are 1 through 65535.
- portName String
- Not supported.
- portSpecification String
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
HTTP2HealthCheck, HTTP2HealthCheckArgs    
- Host string
- The value of the host header in the HTTP/2 health check request. If left empty (default value), the host header is set to the destination IP address to which health check packets are sent. The destination IP address depends on the type of load balancer. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#hc-packet-dest
- Port int
- The TCP port number to which the health check prober sends packets. The default value is 443. Valid values are 1 through 65535.
- PortName string
- Not supported.
- PortSpecification Pulumi.Google Native. Compute. Alpha. HTTP2Health Check Port Specification 
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- ProxyHeader Pulumi.Google Native. Compute. Alpha. HTTP2Health Check Proxy Header 
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- RequestPath string
- The request path of the HTTP/2 health check request. The default value is /.
- Response string
- Creates a content-based HTTP/2 health check. In addition to the required HTTP 200 (OK) status code, you can configure the health check to pass only when the backend sends this specific ASCII response string within the first 1024 bytes of the HTTP response body. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-http
- WeightReport Pulumi.Mode Google Native. Compute. Alpha. HTTP2Health Check Weight Report Mode 
- Weight report mode. used for weighted Load Balancing.
- Host string
- The value of the host header in the HTTP/2 health check request. If left empty (default value), the host header is set to the destination IP address to which health check packets are sent. The destination IP address depends on the type of load balancer. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#hc-packet-dest
- Port int
- The TCP port number to which the health check prober sends packets. The default value is 443. Valid values are 1 through 65535.
- PortName string
- Not supported.
- PortSpecification HTTP2HealthCheck Port Specification 
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- ProxyHeader HTTP2HealthCheck Proxy Header 
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- RequestPath string
- The request path of the HTTP/2 health check request. The default value is /.
- Response string
- Creates a content-based HTTP/2 health check. In addition to the required HTTP 200 (OK) status code, you can configure the health check to pass only when the backend sends this specific ASCII response string within the first 1024 bytes of the HTTP response body. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-http
- WeightReport HTTP2HealthMode Check Weight Report Mode 
- Weight report mode. used for weighted Load Balancing.
- host String
- The value of the host header in the HTTP/2 health check request. If left empty (default value), the host header is set to the destination IP address to which health check packets are sent. The destination IP address depends on the type of load balancer. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#hc-packet-dest
- port Integer
- The TCP port number to which the health check prober sends packets. The default value is 443. Valid values are 1 through 65535.
- portName String
- Not supported.
- portSpecification HTTP2HealthCheck Port Specification 
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- proxyHeader HTTP2HealthCheck Proxy Header 
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- requestPath String
- The request path of the HTTP/2 health check request. The default value is /.
- response String
- Creates a content-based HTTP/2 health check. In addition to the required HTTP 200 (OK) status code, you can configure the health check to pass only when the backend sends this specific ASCII response string within the first 1024 bytes of the HTTP response body. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-http
- weightReport HTTP2HealthMode Check Weight Report Mode 
- Weight report mode. used for weighted Load Balancing.
- host string
- The value of the host header in the HTTP/2 health check request. If left empty (default value), the host header is set to the destination IP address to which health check packets are sent. The destination IP address depends on the type of load balancer. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#hc-packet-dest
- port number
- The TCP port number to which the health check prober sends packets. The default value is 443. Valid values are 1 through 65535.
- portName string
- Not supported.
- portSpecification HTTP2HealthCheck Port Specification 
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- proxyHeader HTTP2HealthCheck Proxy Header 
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- requestPath string
- The request path of the HTTP/2 health check request. The default value is /.
- response string
- Creates a content-based HTTP/2 health check. In addition to the required HTTP 200 (OK) status code, you can configure the health check to pass only when the backend sends this specific ASCII response string within the first 1024 bytes of the HTTP response body. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-http
- weightReport HTTP2HealthMode Check Weight Report Mode 
- Weight report mode. used for weighted Load Balancing.
- host str
- The value of the host header in the HTTP/2 health check request. If left empty (default value), the host header is set to the destination IP address to which health check packets are sent. The destination IP address depends on the type of load balancer. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#hc-packet-dest
- port int
- The TCP port number to which the health check prober sends packets. The default value is 443. Valid values are 1 through 65535.
- port_name str
- Not supported.
- port_specification HTTP2HealthCheck Port Specification 
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- proxy_header HTTP2HealthCheck Proxy Header 
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- request_path str
- The request path of the HTTP/2 health check request. The default value is /.
- response str
- Creates a content-based HTTP/2 health check. In addition to the required HTTP 200 (OK) status code, you can configure the health check to pass only when the backend sends this specific ASCII response string within the first 1024 bytes of the HTTP response body. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-http
- weight_report_ HTTP2Healthmode Check Weight Report Mode 
- Weight report mode. used for weighted Load Balancing.
- host String
- The value of the host header in the HTTP/2 health check request. If left empty (default value), the host header is set to the destination IP address to which health check packets are sent. The destination IP address depends on the type of load balancer. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#hc-packet-dest
- port Number
- The TCP port number to which the health check prober sends packets. The default value is 443. Valid values are 1 through 65535.
- portName String
- Not supported.
- portSpecification "USE_FIXED_PORT" | "USE_NAMED_PORT" | "USE_SERVING_PORT"
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- proxyHeader "NONE" | "PROXY_V1"
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- requestPath String
- The request path of the HTTP/2 health check request. The default value is /.
- response String
- Creates a content-based HTTP/2 health check. In addition to the required HTTP 200 (OK) status code, you can configure the health check to pass only when the backend sends this specific ASCII response string within the first 1024 bytes of the HTTP response body. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-http
- weightReport "DISABLE" | "DRY_RUN" | "ENABLE"Mode 
- Weight report mode. used for weighted Load Balancing.
HTTP2HealthCheckPortSpecification, HTTP2HealthCheckPortSpecificationArgs        
- UseFixed Port 
- USE_FIXED_PORTThe port number in the health check's port is used for health checking. Applies to network endpoint group and instance group backends.
- UseNamed Port 
- USE_NAMED_PORTNot supported.
- UseServing Port 
- USE_SERVING_PORTFor network endpoint group backends, the health check uses the port number specified on each endpoint in the network endpoint group. For instance group backends, the health check uses the port number specified for the backend service's named port defined in the instance group's named ports.
- HTTP2HealthCheck Port Specification Use Fixed Port 
- USE_FIXED_PORTThe port number in the health check's port is used for health checking. Applies to network endpoint group and instance group backends.
- HTTP2HealthCheck Port Specification Use Named Port 
- USE_NAMED_PORTNot supported.
- HTTP2HealthCheck Port Specification Use Serving Port 
- USE_SERVING_PORTFor network endpoint group backends, the health check uses the port number specified on each endpoint in the network endpoint group. For instance group backends, the health check uses the port number specified for the backend service's named port defined in the instance group's named ports.
- UseFixed Port 
- USE_FIXED_PORTThe port number in the health check's port is used for health checking. Applies to network endpoint group and instance group backends.
- UseNamed Port 
- USE_NAMED_PORTNot supported.
- UseServing Port 
- USE_SERVING_PORTFor network endpoint group backends, the health check uses the port number specified on each endpoint in the network endpoint group. For instance group backends, the health check uses the port number specified for the backend service's named port defined in the instance group's named ports.
- UseFixed Port 
- USE_FIXED_PORTThe port number in the health check's port is used for health checking. Applies to network endpoint group and instance group backends.
- UseNamed Port 
- USE_NAMED_PORTNot supported.
- UseServing Port 
- USE_SERVING_PORTFor network endpoint group backends, the health check uses the port number specified on each endpoint in the network endpoint group. For instance group backends, the health check uses the port number specified for the backend service's named port defined in the instance group's named ports.
- USE_FIXED_PORT
- USE_FIXED_PORTThe port number in the health check's port is used for health checking. Applies to network endpoint group and instance group backends.
- USE_NAMED_PORT
- USE_NAMED_PORTNot supported.
- USE_SERVING_PORT
- USE_SERVING_PORTFor network endpoint group backends, the health check uses the port number specified on each endpoint in the network endpoint group. For instance group backends, the health check uses the port number specified for the backend service's named port defined in the instance group's named ports.
- "USE_FIXED_PORT"
- USE_FIXED_PORTThe port number in the health check's port is used for health checking. Applies to network endpoint group and instance group backends.
- "USE_NAMED_PORT"
- USE_NAMED_PORTNot supported.
- "USE_SERVING_PORT"
- USE_SERVING_PORTFor network endpoint group backends, the health check uses the port number specified on each endpoint in the network endpoint group. For instance group backends, the health check uses the port number specified for the backend service's named port defined in the instance group's named ports.
HTTP2HealthCheckProxyHeader, HTTP2HealthCheckProxyHeaderArgs        
- None
- NONE
- ProxyV1 
- PROXY_V1
- HTTP2HealthCheck Proxy Header None 
- NONE
- HTTP2HealthCheck Proxy Header Proxy V1 
- PROXY_V1
- None
- NONE
- ProxyV1 
- PROXY_V1
- None
- NONE
- ProxyV1 
- PROXY_V1
- NONE
- NONE
- PROXY_V1
- PROXY_V1
- "NONE"
- NONE
- "PROXY_V1"
- PROXY_V1
HTTP2HealthCheckResponse, HTTP2HealthCheckResponseArgs      
- Host string
- The value of the host header in the HTTP/2 health check request. If left empty (default value), the host header is set to the destination IP address to which health check packets are sent. The destination IP address depends on the type of load balancer. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#hc-packet-dest
- Port int
- The TCP port number to which the health check prober sends packets. The default value is 443. Valid values are 1 through 65535.
- PortName string
- Not supported.
- PortSpecification string
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- ProxyHeader string
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- RequestPath string
- The request path of the HTTP/2 health check request. The default value is /.
- Response string
- Creates a content-based HTTP/2 health check. In addition to the required HTTP 200 (OK) status code, you can configure the health check to pass only when the backend sends this specific ASCII response string within the first 1024 bytes of the HTTP response body. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-http
- WeightReport stringMode 
- Weight report mode. used for weighted Load Balancing.
- Host string
- The value of the host header in the HTTP/2 health check request. If left empty (default value), the host header is set to the destination IP address to which health check packets are sent. The destination IP address depends on the type of load balancer. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#hc-packet-dest
- Port int
- The TCP port number to which the health check prober sends packets. The default value is 443. Valid values are 1 through 65535.
- PortName string
- Not supported.
- PortSpecification string
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- ProxyHeader string
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- RequestPath string
- The request path of the HTTP/2 health check request. The default value is /.
- Response string
- Creates a content-based HTTP/2 health check. In addition to the required HTTP 200 (OK) status code, you can configure the health check to pass only when the backend sends this specific ASCII response string within the first 1024 bytes of the HTTP response body. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-http
- WeightReport stringMode 
- Weight report mode. used for weighted Load Balancing.
- host String
- The value of the host header in the HTTP/2 health check request. If left empty (default value), the host header is set to the destination IP address to which health check packets are sent. The destination IP address depends on the type of load balancer. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#hc-packet-dest
- port Integer
- The TCP port number to which the health check prober sends packets. The default value is 443. Valid values are 1 through 65535.
- portName String
- Not supported.
- portSpecification String
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- proxyHeader String
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- requestPath String
- The request path of the HTTP/2 health check request. The default value is /.
- response String
- Creates a content-based HTTP/2 health check. In addition to the required HTTP 200 (OK) status code, you can configure the health check to pass only when the backend sends this specific ASCII response string within the first 1024 bytes of the HTTP response body. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-http
- weightReport StringMode 
- Weight report mode. used for weighted Load Balancing.
- host string
- The value of the host header in the HTTP/2 health check request. If left empty (default value), the host header is set to the destination IP address to which health check packets are sent. The destination IP address depends on the type of load balancer. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#hc-packet-dest
- port number
- The TCP port number to which the health check prober sends packets. The default value is 443. Valid values are 1 through 65535.
- portName string
- Not supported.
- portSpecification string
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- proxyHeader string
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- requestPath string
- The request path of the HTTP/2 health check request. The default value is /.
- response string
- Creates a content-based HTTP/2 health check. In addition to the required HTTP 200 (OK) status code, you can configure the health check to pass only when the backend sends this specific ASCII response string within the first 1024 bytes of the HTTP response body. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-http
- weightReport stringMode 
- Weight report mode. used for weighted Load Balancing.
- host str
- The value of the host header in the HTTP/2 health check request. If left empty (default value), the host header is set to the destination IP address to which health check packets are sent. The destination IP address depends on the type of load balancer. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#hc-packet-dest
- port int
- The TCP port number to which the health check prober sends packets. The default value is 443. Valid values are 1 through 65535.
- port_name str
- Not supported.
- port_specification str
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- proxy_header str
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- request_path str
- The request path of the HTTP/2 health check request. The default value is /.
- response str
- Creates a content-based HTTP/2 health check. In addition to the required HTTP 200 (OK) status code, you can configure the health check to pass only when the backend sends this specific ASCII response string within the first 1024 bytes of the HTTP response body. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-http
- weight_report_ strmode 
- Weight report mode. used for weighted Load Balancing.
- host String
- The value of the host header in the HTTP/2 health check request. If left empty (default value), the host header is set to the destination IP address to which health check packets are sent. The destination IP address depends on the type of load balancer. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#hc-packet-dest
- port Number
- The TCP port number to which the health check prober sends packets. The default value is 443. Valid values are 1 through 65535.
- portName String
- Not supported.
- portSpecification String
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- proxyHeader String
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- requestPath String
- The request path of the HTTP/2 health check request. The default value is /.
- response String
- Creates a content-based HTTP/2 health check. In addition to the required HTTP 200 (OK) status code, you can configure the health check to pass only when the backend sends this specific ASCII response string within the first 1024 bytes of the HTTP response body. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-http
- weightReport StringMode 
- Weight report mode. used for weighted Load Balancing.
HTTP2HealthCheckWeightReportMode, HTTP2HealthCheckWeightReportModeArgs          
- Disable
- DISABLEHealth Checker will not parse the header field.
- DryRun 
- DRY_RUNHealth Checker will parse and report the weight in the header field, but load balancing will not be based on the weights and will use equal weights.
- Enable
- ENABLEHealth Checker will try to parse and report the weight in the header field, and load balancing will be based on the weights as long as all backends have a valid weight or only a subset of backends has the UNAVAILABLE_WEIGHT WeightError. The latter case is to continue the weighted load balancing while some backends are in TIMEOUT or UNKNOWN health status.
- HTTP2HealthCheck Weight Report Mode Disable 
- DISABLEHealth Checker will not parse the header field.
- HTTP2HealthCheck Weight Report Mode Dry Run 
- DRY_RUNHealth Checker will parse and report the weight in the header field, but load balancing will not be based on the weights and will use equal weights.
- HTTP2HealthCheck Weight Report Mode Enable 
- ENABLEHealth Checker will try to parse and report the weight in the header field, and load balancing will be based on the weights as long as all backends have a valid weight or only a subset of backends has the UNAVAILABLE_WEIGHT WeightError. The latter case is to continue the weighted load balancing while some backends are in TIMEOUT or UNKNOWN health status.
- Disable
- DISABLEHealth Checker will not parse the header field.
- DryRun 
- DRY_RUNHealth Checker will parse and report the weight in the header field, but load balancing will not be based on the weights and will use equal weights.
- Enable
- ENABLEHealth Checker will try to parse and report the weight in the header field, and load balancing will be based on the weights as long as all backends have a valid weight or only a subset of backends has the UNAVAILABLE_WEIGHT WeightError. The latter case is to continue the weighted load balancing while some backends are in TIMEOUT or UNKNOWN health status.
- Disable
- DISABLEHealth Checker will not parse the header field.
- DryRun 
- DRY_RUNHealth Checker will parse and report the weight in the header field, but load balancing will not be based on the weights and will use equal weights.
- Enable
- ENABLEHealth Checker will try to parse and report the weight in the header field, and load balancing will be based on the weights as long as all backends have a valid weight or only a subset of backends has the UNAVAILABLE_WEIGHT WeightError. The latter case is to continue the weighted load balancing while some backends are in TIMEOUT or UNKNOWN health status.
- DISABLE
- DISABLEHealth Checker will not parse the header field.
- DRY_RUN
- DRY_RUNHealth Checker will parse and report the weight in the header field, but load balancing will not be based on the weights and will use equal weights.
- ENABLE
- ENABLEHealth Checker will try to parse and report the weight in the header field, and load balancing will be based on the weights as long as all backends have a valid weight or only a subset of backends has the UNAVAILABLE_WEIGHT WeightError. The latter case is to continue the weighted load balancing while some backends are in TIMEOUT or UNKNOWN health status.
- "DISABLE"
- DISABLEHealth Checker will not parse the header field.
- "DRY_RUN"
- DRY_RUNHealth Checker will parse and report the weight in the header field, but load balancing will not be based on the weights and will use equal weights.
- "ENABLE"
- ENABLEHealth Checker will try to parse and report the weight in the header field, and load balancing will be based on the weights as long as all backends have a valid weight or only a subset of backends has the UNAVAILABLE_WEIGHT WeightError. The latter case is to continue the weighted load balancing while some backends are in TIMEOUT or UNKNOWN health status.
HTTPHealthCheck, HTTPHealthCheckArgs    
- Host string
- The value of the host header in the HTTP health check request. If left empty (default value), the host header is set to the destination IP address to which health check packets are sent. The destination IP address depends on the type of load balancer. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#hc-packet-dest
- Port int
- The TCP port number to which the health check prober sends packets. The default value is 80. Valid values are 1 through 65535.
- PortName string
- Not supported.
- PortSpecification Pulumi.Google Native. Compute. Alpha. HTTPHealth Check Port Specification 
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Also supported in legacy HTTP health checks for target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- ProxyHeader Pulumi.Google Native. Compute. Alpha. HTTPHealth Check Proxy Header 
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- RequestPath string
- The request path of the HTTP health check request. The default value is /.
- Response string
- Creates a content-based HTTP health check. In addition to the required HTTP 200 (OK) status code, you can configure the health check to pass only when the backend sends this specific ASCII response string within the first 1024 bytes of the HTTP response body. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-http
- WeightReport Pulumi.Mode Google Native. Compute. Alpha. HTTPHealth Check Weight Report Mode 
- Weight report mode. used for weighted Load Balancing.
- Host string
- The value of the host header in the HTTP health check request. If left empty (default value), the host header is set to the destination IP address to which health check packets are sent. The destination IP address depends on the type of load balancer. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#hc-packet-dest
- Port int
- The TCP port number to which the health check prober sends packets. The default value is 80. Valid values are 1 through 65535.
- PortName string
- Not supported.
- PortSpecification HTTPHealthCheck Port Specification 
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Also supported in legacy HTTP health checks for target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- ProxyHeader HTTPHealthCheck Proxy Header 
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- RequestPath string
- The request path of the HTTP health check request. The default value is /.
- Response string
- Creates a content-based HTTP health check. In addition to the required HTTP 200 (OK) status code, you can configure the health check to pass only when the backend sends this specific ASCII response string within the first 1024 bytes of the HTTP response body. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-http
- WeightReport HTTPHealthMode Check Weight Report Mode 
- Weight report mode. used for weighted Load Balancing.
- host String
- The value of the host header in the HTTP health check request. If left empty (default value), the host header is set to the destination IP address to which health check packets are sent. The destination IP address depends on the type of load balancer. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#hc-packet-dest
- port Integer
- The TCP port number to which the health check prober sends packets. The default value is 80. Valid values are 1 through 65535.
- portName String
- Not supported.
- portSpecification HTTPHealthCheck Port Specification 
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Also supported in legacy HTTP health checks for target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- proxyHeader HTTPHealthCheck Proxy Header 
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- requestPath String
- The request path of the HTTP health check request. The default value is /.
- response String
- Creates a content-based HTTP health check. In addition to the required HTTP 200 (OK) status code, you can configure the health check to pass only when the backend sends this specific ASCII response string within the first 1024 bytes of the HTTP response body. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-http
- weightReport HTTPHealthMode Check Weight Report Mode 
- Weight report mode. used for weighted Load Balancing.
- host string
- The value of the host header in the HTTP health check request. If left empty (default value), the host header is set to the destination IP address to which health check packets are sent. The destination IP address depends on the type of load balancer. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#hc-packet-dest
- port number
- The TCP port number to which the health check prober sends packets. The default value is 80. Valid values are 1 through 65535.
- portName string
- Not supported.
- portSpecification HTTPHealthCheck Port Specification 
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Also supported in legacy HTTP health checks for target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- proxyHeader HTTPHealthCheck Proxy Header 
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- requestPath string
- The request path of the HTTP health check request. The default value is /.
- response string
- Creates a content-based HTTP health check. In addition to the required HTTP 200 (OK) status code, you can configure the health check to pass only when the backend sends this specific ASCII response string within the first 1024 bytes of the HTTP response body. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-http
- weightReport HTTPHealthMode Check Weight Report Mode 
- Weight report mode. used for weighted Load Balancing.
- host str
- The value of the host header in the HTTP health check request. If left empty (default value), the host header is set to the destination IP address to which health check packets are sent. The destination IP address depends on the type of load balancer. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#hc-packet-dest
- port int
- The TCP port number to which the health check prober sends packets. The default value is 80. Valid values are 1 through 65535.
- port_name str
- Not supported.
- port_specification HTTPHealthCheck Port Specification 
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Also supported in legacy HTTP health checks for target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- proxy_header HTTPHealthCheck Proxy Header 
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- request_path str
- The request path of the HTTP health check request. The default value is /.
- response str
- Creates a content-based HTTP health check. In addition to the required HTTP 200 (OK) status code, you can configure the health check to pass only when the backend sends this specific ASCII response string within the first 1024 bytes of the HTTP response body. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-http
- weight_report_ HTTPHealthmode Check Weight Report Mode 
- Weight report mode. used for weighted Load Balancing.
- host String
- The value of the host header in the HTTP health check request. If left empty (default value), the host header is set to the destination IP address to which health check packets are sent. The destination IP address depends on the type of load balancer. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#hc-packet-dest
- port Number
- The TCP port number to which the health check prober sends packets. The default value is 80. Valid values are 1 through 65535.
- portName String
- Not supported.
- portSpecification "USE_FIXED_PORT" | "USE_NAMED_PORT" | "USE_SERVING_PORT"
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Also supported in legacy HTTP health checks for target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- proxyHeader "NONE" | "PROXY_V1"
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- requestPath String
- The request path of the HTTP health check request. The default value is /.
- response String
- Creates a content-based HTTP health check. In addition to the required HTTP 200 (OK) status code, you can configure the health check to pass only when the backend sends this specific ASCII response string within the first 1024 bytes of the HTTP response body. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-http
- weightReport "DISABLE" | "DRY_RUN" | "ENABLE"Mode 
- Weight report mode. used for weighted Load Balancing.
HTTPHealthCheckPortSpecification, HTTPHealthCheckPortSpecificationArgs        
- UseFixed Port 
- USE_FIXED_PORTThe port number in the health check's port is used for health checking. Applies to network endpoint group and instance group backends.
- UseNamed Port 
- USE_NAMED_PORTNot supported.
- UseServing Port 
- USE_SERVING_PORTFor network endpoint group backends, the health check uses the port number specified on each endpoint in the network endpoint group. For instance group backends, the health check uses the port number specified for the backend service's named port defined in the instance group's named ports.
- HTTPHealthCheck Port Specification Use Fixed Port 
- USE_FIXED_PORTThe port number in the health check's port is used for health checking. Applies to network endpoint group and instance group backends.
- HTTPHealthCheck Port Specification Use Named Port 
- USE_NAMED_PORTNot supported.
- HTTPHealthCheck Port Specification Use Serving Port 
- USE_SERVING_PORTFor network endpoint group backends, the health check uses the port number specified on each endpoint in the network endpoint group. For instance group backends, the health check uses the port number specified for the backend service's named port defined in the instance group's named ports.
- UseFixed Port 
- USE_FIXED_PORTThe port number in the health check's port is used for health checking. Applies to network endpoint group and instance group backends.
- UseNamed Port 
- USE_NAMED_PORTNot supported.
- UseServing Port 
- USE_SERVING_PORTFor network endpoint group backends, the health check uses the port number specified on each endpoint in the network endpoint group. For instance group backends, the health check uses the port number specified for the backend service's named port defined in the instance group's named ports.
- UseFixed Port 
- USE_FIXED_PORTThe port number in the health check's port is used for health checking. Applies to network endpoint group and instance group backends.
- UseNamed Port 
- USE_NAMED_PORTNot supported.
- UseServing Port 
- USE_SERVING_PORTFor network endpoint group backends, the health check uses the port number specified on each endpoint in the network endpoint group. For instance group backends, the health check uses the port number specified for the backend service's named port defined in the instance group's named ports.
- USE_FIXED_PORT
- USE_FIXED_PORTThe port number in the health check's port is used for health checking. Applies to network endpoint group and instance group backends.
- USE_NAMED_PORT
- USE_NAMED_PORTNot supported.
- USE_SERVING_PORT
- USE_SERVING_PORTFor network endpoint group backends, the health check uses the port number specified on each endpoint in the network endpoint group. For instance group backends, the health check uses the port number specified for the backend service's named port defined in the instance group's named ports.
- "USE_FIXED_PORT"
- USE_FIXED_PORTThe port number in the health check's port is used for health checking. Applies to network endpoint group and instance group backends.
- "USE_NAMED_PORT"
- USE_NAMED_PORTNot supported.
- "USE_SERVING_PORT"
- USE_SERVING_PORTFor network endpoint group backends, the health check uses the port number specified on each endpoint in the network endpoint group. For instance group backends, the health check uses the port number specified for the backend service's named port defined in the instance group's named ports.
HTTPHealthCheckProxyHeader, HTTPHealthCheckProxyHeaderArgs        
- None
- NONE
- ProxyV1 
- PROXY_V1
- HTTPHealthCheck Proxy Header None 
- NONE
- HTTPHealthCheck Proxy Header Proxy V1 
- PROXY_V1
- None
- NONE
- ProxyV1 
- PROXY_V1
- None
- NONE
- ProxyV1 
- PROXY_V1
- NONE
- NONE
- PROXY_V1
- PROXY_V1
- "NONE"
- NONE
- "PROXY_V1"
- PROXY_V1
HTTPHealthCheckResponse, HTTPHealthCheckResponseArgs      
- Host string
- The value of the host header in the HTTP health check request. If left empty (default value), the host header is set to the destination IP address to which health check packets are sent. The destination IP address depends on the type of load balancer. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#hc-packet-dest
- Port int
- The TCP port number to which the health check prober sends packets. The default value is 80. Valid values are 1 through 65535.
- PortName string
- Not supported.
- PortSpecification string
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Also supported in legacy HTTP health checks for target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- ProxyHeader string
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- RequestPath string
- The request path of the HTTP health check request. The default value is /.
- Response string
- Creates a content-based HTTP health check. In addition to the required HTTP 200 (OK) status code, you can configure the health check to pass only when the backend sends this specific ASCII response string within the first 1024 bytes of the HTTP response body. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-http
- WeightReport stringMode 
- Weight report mode. used for weighted Load Balancing.
- Host string
- The value of the host header in the HTTP health check request. If left empty (default value), the host header is set to the destination IP address to which health check packets are sent. The destination IP address depends on the type of load balancer. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#hc-packet-dest
- Port int
- The TCP port number to which the health check prober sends packets. The default value is 80. Valid values are 1 through 65535.
- PortName string
- Not supported.
- PortSpecification string
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Also supported in legacy HTTP health checks for target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- ProxyHeader string
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- RequestPath string
- The request path of the HTTP health check request. The default value is /.
- Response string
- Creates a content-based HTTP health check. In addition to the required HTTP 200 (OK) status code, you can configure the health check to pass only when the backend sends this specific ASCII response string within the first 1024 bytes of the HTTP response body. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-http
- WeightReport stringMode 
- Weight report mode. used for weighted Load Balancing.
- host String
- The value of the host header in the HTTP health check request. If left empty (default value), the host header is set to the destination IP address to which health check packets are sent. The destination IP address depends on the type of load balancer. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#hc-packet-dest
- port Integer
- The TCP port number to which the health check prober sends packets. The default value is 80. Valid values are 1 through 65535.
- portName String
- Not supported.
- portSpecification String
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Also supported in legacy HTTP health checks for target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- proxyHeader String
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- requestPath String
- The request path of the HTTP health check request. The default value is /.
- response String
- Creates a content-based HTTP health check. In addition to the required HTTP 200 (OK) status code, you can configure the health check to pass only when the backend sends this specific ASCII response string within the first 1024 bytes of the HTTP response body. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-http
- weightReport StringMode 
- Weight report mode. used for weighted Load Balancing.
- host string
- The value of the host header in the HTTP health check request. If left empty (default value), the host header is set to the destination IP address to which health check packets are sent. The destination IP address depends on the type of load balancer. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#hc-packet-dest
- port number
- The TCP port number to which the health check prober sends packets. The default value is 80. Valid values are 1 through 65535.
- portName string
- Not supported.
- portSpecification string
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Also supported in legacy HTTP health checks for target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- proxyHeader string
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- requestPath string
- The request path of the HTTP health check request. The default value is /.
- response string
- Creates a content-based HTTP health check. In addition to the required HTTP 200 (OK) status code, you can configure the health check to pass only when the backend sends this specific ASCII response string within the first 1024 bytes of the HTTP response body. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-http
- weightReport stringMode 
- Weight report mode. used for weighted Load Balancing.
- host str
- The value of the host header in the HTTP health check request. If left empty (default value), the host header is set to the destination IP address to which health check packets are sent. The destination IP address depends on the type of load balancer. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#hc-packet-dest
- port int
- The TCP port number to which the health check prober sends packets. The default value is 80. Valid values are 1 through 65535.
- port_name str
- Not supported.
- port_specification str
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Also supported in legacy HTTP health checks for target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- proxy_header str
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- request_path str
- The request path of the HTTP health check request. The default value is /.
- response str
- Creates a content-based HTTP health check. In addition to the required HTTP 200 (OK) status code, you can configure the health check to pass only when the backend sends this specific ASCII response string within the first 1024 bytes of the HTTP response body. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-http
- weight_report_ strmode 
- Weight report mode. used for weighted Load Balancing.
- host String
- The value of the host header in the HTTP health check request. If left empty (default value), the host header is set to the destination IP address to which health check packets are sent. The destination IP address depends on the type of load balancer. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#hc-packet-dest
- port Number
- The TCP port number to which the health check prober sends packets. The default value is 80. Valid values are 1 through 65535.
- portName String
- Not supported.
- portSpecification String
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Also supported in legacy HTTP health checks for target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- proxyHeader String
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- requestPath String
- The request path of the HTTP health check request. The default value is /.
- response String
- Creates a content-based HTTP health check. In addition to the required HTTP 200 (OK) status code, you can configure the health check to pass only when the backend sends this specific ASCII response string within the first 1024 bytes of the HTTP response body. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-http
- weightReport StringMode 
- Weight report mode. used for weighted Load Balancing.
HTTPHealthCheckWeightReportMode, HTTPHealthCheckWeightReportModeArgs          
- Disable
- DISABLEHealth Checker will not parse the header field.
- DryRun 
- DRY_RUNHealth Checker will parse and report the weight in the header field, but load balancing will not be based on the weights and will use equal weights.
- Enable
- ENABLEHealth Checker will try to parse and report the weight in the header field, and load balancing will be based on the weights as long as all backends have a valid weight or only a subset of backends has the UNAVAILABLE_WEIGHT WeightError. The latter case is to continue the weighted load balancing while some backends are in TIMEOUT or UNKNOWN health status.
- HTTPHealthCheck Weight Report Mode Disable 
- DISABLEHealth Checker will not parse the header field.
- HTTPHealthCheck Weight Report Mode Dry Run 
- DRY_RUNHealth Checker will parse and report the weight in the header field, but load balancing will not be based on the weights and will use equal weights.
- HTTPHealthCheck Weight Report Mode Enable 
- ENABLEHealth Checker will try to parse and report the weight in the header field, and load balancing will be based on the weights as long as all backends have a valid weight or only a subset of backends has the UNAVAILABLE_WEIGHT WeightError. The latter case is to continue the weighted load balancing while some backends are in TIMEOUT or UNKNOWN health status.
- Disable
- DISABLEHealth Checker will not parse the header field.
- DryRun 
- DRY_RUNHealth Checker will parse and report the weight in the header field, but load balancing will not be based on the weights and will use equal weights.
- Enable
- ENABLEHealth Checker will try to parse and report the weight in the header field, and load balancing will be based on the weights as long as all backends have a valid weight or only a subset of backends has the UNAVAILABLE_WEIGHT WeightError. The latter case is to continue the weighted load balancing while some backends are in TIMEOUT or UNKNOWN health status.
- Disable
- DISABLEHealth Checker will not parse the header field.
- DryRun 
- DRY_RUNHealth Checker will parse and report the weight in the header field, but load balancing will not be based on the weights and will use equal weights.
- Enable
- ENABLEHealth Checker will try to parse and report the weight in the header field, and load balancing will be based on the weights as long as all backends have a valid weight or only a subset of backends has the UNAVAILABLE_WEIGHT WeightError. The latter case is to continue the weighted load balancing while some backends are in TIMEOUT or UNKNOWN health status.
- DISABLE
- DISABLEHealth Checker will not parse the header field.
- DRY_RUN
- DRY_RUNHealth Checker will parse and report the weight in the header field, but load balancing will not be based on the weights and will use equal weights.
- ENABLE
- ENABLEHealth Checker will try to parse and report the weight in the header field, and load balancing will be based on the weights as long as all backends have a valid weight or only a subset of backends has the UNAVAILABLE_WEIGHT WeightError. The latter case is to continue the weighted load balancing while some backends are in TIMEOUT or UNKNOWN health status.
- "DISABLE"
- DISABLEHealth Checker will not parse the header field.
- "DRY_RUN"
- DRY_RUNHealth Checker will parse and report the weight in the header field, but load balancing will not be based on the weights and will use equal weights.
- "ENABLE"
- ENABLEHealth Checker will try to parse and report the weight in the header field, and load balancing will be based on the weights as long as all backends have a valid weight or only a subset of backends has the UNAVAILABLE_WEIGHT WeightError. The latter case is to continue the weighted load balancing while some backends are in TIMEOUT or UNKNOWN health status.
HTTPSHealthCheck, HTTPSHealthCheckArgs    
- Host string
- The value of the host header in the HTTPS health check request. If left empty (default value), the host header is set to the destination IP address to which health check packets are sent. The destination IP address depends on the type of load balancer. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#hc-packet-dest
- Port int
- The TCP port number to which the health check prober sends packets. The default value is 443. Valid values are 1 through 65535.
- PortName string
- Not supported.
- PortSpecification Pulumi.Google Native. Compute. Alpha. HTTPSHealth Check Port Specification 
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- ProxyHeader Pulumi.Google Native. Compute. Alpha. HTTPSHealth Check Proxy Header 
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- RequestPath string
- The request path of the HTTPS health check request. The default value is /.
- Response string
- Creates a content-based HTTPS health check. In addition to the required HTTP 200 (OK) status code, you can configure the health check to pass only when the backend sends this specific ASCII response string within the first 1024 bytes of the HTTP response body. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-http
- WeightReport Pulumi.Mode Google Native. Compute. Alpha. HTTPSHealth Check Weight Report Mode 
- Weight report mode. used for weighted Load Balancing.
- Host string
- The value of the host header in the HTTPS health check request. If left empty (default value), the host header is set to the destination IP address to which health check packets are sent. The destination IP address depends on the type of load balancer. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#hc-packet-dest
- Port int
- The TCP port number to which the health check prober sends packets. The default value is 443. Valid values are 1 through 65535.
- PortName string
- Not supported.
- PortSpecification HTTPSHealthCheck Port Specification 
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- ProxyHeader HTTPSHealthCheck Proxy Header 
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- RequestPath string
- The request path of the HTTPS health check request. The default value is /.
- Response string
- Creates a content-based HTTPS health check. In addition to the required HTTP 200 (OK) status code, you can configure the health check to pass only when the backend sends this specific ASCII response string within the first 1024 bytes of the HTTP response body. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-http
- WeightReport HTTPSHealthMode Check Weight Report Mode 
- Weight report mode. used for weighted Load Balancing.
- host String
- The value of the host header in the HTTPS health check request. If left empty (default value), the host header is set to the destination IP address to which health check packets are sent. The destination IP address depends on the type of load balancer. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#hc-packet-dest
- port Integer
- The TCP port number to which the health check prober sends packets. The default value is 443. Valid values are 1 through 65535.
- portName String
- Not supported.
- portSpecification HTTPSHealthCheck Port Specification 
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- proxyHeader HTTPSHealthCheck Proxy Header 
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- requestPath String
- The request path of the HTTPS health check request. The default value is /.
- response String
- Creates a content-based HTTPS health check. In addition to the required HTTP 200 (OK) status code, you can configure the health check to pass only when the backend sends this specific ASCII response string within the first 1024 bytes of the HTTP response body. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-http
- weightReport HTTPSHealthMode Check Weight Report Mode 
- Weight report mode. used for weighted Load Balancing.
- host string
- The value of the host header in the HTTPS health check request. If left empty (default value), the host header is set to the destination IP address to which health check packets are sent. The destination IP address depends on the type of load balancer. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#hc-packet-dest
- port number
- The TCP port number to which the health check prober sends packets. The default value is 443. Valid values are 1 through 65535.
- portName string
- Not supported.
- portSpecification HTTPSHealthCheck Port Specification 
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- proxyHeader HTTPSHealthCheck Proxy Header 
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- requestPath string
- The request path of the HTTPS health check request. The default value is /.
- response string
- Creates a content-based HTTPS health check. In addition to the required HTTP 200 (OK) status code, you can configure the health check to pass only when the backend sends this specific ASCII response string within the first 1024 bytes of the HTTP response body. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-http
- weightReport HTTPSHealthMode Check Weight Report Mode 
- Weight report mode. used for weighted Load Balancing.
- host str
- The value of the host header in the HTTPS health check request. If left empty (default value), the host header is set to the destination IP address to which health check packets are sent. The destination IP address depends on the type of load balancer. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#hc-packet-dest
- port int
- The TCP port number to which the health check prober sends packets. The default value is 443. Valid values are 1 through 65535.
- port_name str
- Not supported.
- port_specification HTTPSHealthCheck Port Specification 
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- proxy_header HTTPSHealthCheck Proxy Header 
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- request_path str
- The request path of the HTTPS health check request. The default value is /.
- response str
- Creates a content-based HTTPS health check. In addition to the required HTTP 200 (OK) status code, you can configure the health check to pass only when the backend sends this specific ASCII response string within the first 1024 bytes of the HTTP response body. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-http
- weight_report_ HTTPSHealthmode Check Weight Report Mode 
- Weight report mode. used for weighted Load Balancing.
- host String
- The value of the host header in the HTTPS health check request. If left empty (default value), the host header is set to the destination IP address to which health check packets are sent. The destination IP address depends on the type of load balancer. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#hc-packet-dest
- port Number
- The TCP port number to which the health check prober sends packets. The default value is 443. Valid values are 1 through 65535.
- portName String
- Not supported.
- portSpecification "USE_FIXED_PORT" | "USE_NAMED_PORT" | "USE_SERVING_PORT"
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- proxyHeader "NONE" | "PROXY_V1"
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- requestPath String
- The request path of the HTTPS health check request. The default value is /.
- response String
- Creates a content-based HTTPS health check. In addition to the required HTTP 200 (OK) status code, you can configure the health check to pass only when the backend sends this specific ASCII response string within the first 1024 bytes of the HTTP response body. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-http
- weightReport "DISABLE" | "DRY_RUN" | "ENABLE"Mode 
- Weight report mode. used for weighted Load Balancing.
HTTPSHealthCheckPortSpecification, HTTPSHealthCheckPortSpecificationArgs        
- UseFixed Port 
- USE_FIXED_PORTThe port number in the health check's port is used for health checking. Applies to network endpoint group and instance group backends.
- UseNamed Port 
- USE_NAMED_PORTNot supported.
- UseServing Port 
- USE_SERVING_PORTFor network endpoint group backends, the health check uses the port number specified on each endpoint in the network endpoint group. For instance group backends, the health check uses the port number specified for the backend service's named port defined in the instance group's named ports.
- HTTPSHealthCheck Port Specification Use Fixed Port 
- USE_FIXED_PORTThe port number in the health check's port is used for health checking. Applies to network endpoint group and instance group backends.
- HTTPSHealthCheck Port Specification Use Named Port 
- USE_NAMED_PORTNot supported.
- HTTPSHealthCheck Port Specification Use Serving Port 
- USE_SERVING_PORTFor network endpoint group backends, the health check uses the port number specified on each endpoint in the network endpoint group. For instance group backends, the health check uses the port number specified for the backend service's named port defined in the instance group's named ports.
- UseFixed Port 
- USE_FIXED_PORTThe port number in the health check's port is used for health checking. Applies to network endpoint group and instance group backends.
- UseNamed Port 
- USE_NAMED_PORTNot supported.
- UseServing Port 
- USE_SERVING_PORTFor network endpoint group backends, the health check uses the port number specified on each endpoint in the network endpoint group. For instance group backends, the health check uses the port number specified for the backend service's named port defined in the instance group's named ports.
- UseFixed Port 
- USE_FIXED_PORTThe port number in the health check's port is used for health checking. Applies to network endpoint group and instance group backends.
- UseNamed Port 
- USE_NAMED_PORTNot supported.
- UseServing Port 
- USE_SERVING_PORTFor network endpoint group backends, the health check uses the port number specified on each endpoint in the network endpoint group. For instance group backends, the health check uses the port number specified for the backend service's named port defined in the instance group's named ports.
- USE_FIXED_PORT
- USE_FIXED_PORTThe port number in the health check's port is used for health checking. Applies to network endpoint group and instance group backends.
- USE_NAMED_PORT
- USE_NAMED_PORTNot supported.
- USE_SERVING_PORT
- USE_SERVING_PORTFor network endpoint group backends, the health check uses the port number specified on each endpoint in the network endpoint group. For instance group backends, the health check uses the port number specified for the backend service's named port defined in the instance group's named ports.
- "USE_FIXED_PORT"
- USE_FIXED_PORTThe port number in the health check's port is used for health checking. Applies to network endpoint group and instance group backends.
- "USE_NAMED_PORT"
- USE_NAMED_PORTNot supported.
- "USE_SERVING_PORT"
- USE_SERVING_PORTFor network endpoint group backends, the health check uses the port number specified on each endpoint in the network endpoint group. For instance group backends, the health check uses the port number specified for the backend service's named port defined in the instance group's named ports.
HTTPSHealthCheckProxyHeader, HTTPSHealthCheckProxyHeaderArgs        
- None
- NONE
- ProxyV1 
- PROXY_V1
- HTTPSHealthCheck Proxy Header None 
- NONE
- HTTPSHealthCheck Proxy Header Proxy V1 
- PROXY_V1
- None
- NONE
- ProxyV1 
- PROXY_V1
- None
- NONE
- ProxyV1 
- PROXY_V1
- NONE
- NONE
- PROXY_V1
- PROXY_V1
- "NONE"
- NONE
- "PROXY_V1"
- PROXY_V1
HTTPSHealthCheckResponse, HTTPSHealthCheckResponseArgs      
- Host string
- The value of the host header in the HTTPS health check request. If left empty (default value), the host header is set to the destination IP address to which health check packets are sent. The destination IP address depends on the type of load balancer. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#hc-packet-dest
- Port int
- The TCP port number to which the health check prober sends packets. The default value is 443. Valid values are 1 through 65535.
- PortName string
- Not supported.
- PortSpecification string
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- ProxyHeader string
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- RequestPath string
- The request path of the HTTPS health check request. The default value is /.
- Response string
- Creates a content-based HTTPS health check. In addition to the required HTTP 200 (OK) status code, you can configure the health check to pass only when the backend sends this specific ASCII response string within the first 1024 bytes of the HTTP response body. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-http
- WeightReport stringMode 
- Weight report mode. used for weighted Load Balancing.
- Host string
- The value of the host header in the HTTPS health check request. If left empty (default value), the host header is set to the destination IP address to which health check packets are sent. The destination IP address depends on the type of load balancer. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#hc-packet-dest
- Port int
- The TCP port number to which the health check prober sends packets. The default value is 443. Valid values are 1 through 65535.
- PortName string
- Not supported.
- PortSpecification string
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- ProxyHeader string
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- RequestPath string
- The request path of the HTTPS health check request. The default value is /.
- Response string
- Creates a content-based HTTPS health check. In addition to the required HTTP 200 (OK) status code, you can configure the health check to pass only when the backend sends this specific ASCII response string within the first 1024 bytes of the HTTP response body. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-http
- WeightReport stringMode 
- Weight report mode. used for weighted Load Balancing.
- host String
- The value of the host header in the HTTPS health check request. If left empty (default value), the host header is set to the destination IP address to which health check packets are sent. The destination IP address depends on the type of load balancer. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#hc-packet-dest
- port Integer
- The TCP port number to which the health check prober sends packets. The default value is 443. Valid values are 1 through 65535.
- portName String
- Not supported.
- portSpecification String
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- proxyHeader String
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- requestPath String
- The request path of the HTTPS health check request. The default value is /.
- response String
- Creates a content-based HTTPS health check. In addition to the required HTTP 200 (OK) status code, you can configure the health check to pass only when the backend sends this specific ASCII response string within the first 1024 bytes of the HTTP response body. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-http
- weightReport StringMode 
- Weight report mode. used for weighted Load Balancing.
- host string
- The value of the host header in the HTTPS health check request. If left empty (default value), the host header is set to the destination IP address to which health check packets are sent. The destination IP address depends on the type of load balancer. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#hc-packet-dest
- port number
- The TCP port number to which the health check prober sends packets. The default value is 443. Valid values are 1 through 65535.
- portName string
- Not supported.
- portSpecification string
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- proxyHeader string
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- requestPath string
- The request path of the HTTPS health check request. The default value is /.
- response string
- Creates a content-based HTTPS health check. In addition to the required HTTP 200 (OK) status code, you can configure the health check to pass only when the backend sends this specific ASCII response string within the first 1024 bytes of the HTTP response body. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-http
- weightReport stringMode 
- Weight report mode. used for weighted Load Balancing.
- host str
- The value of the host header in the HTTPS health check request. If left empty (default value), the host header is set to the destination IP address to which health check packets are sent. The destination IP address depends on the type of load balancer. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#hc-packet-dest
- port int
- The TCP port number to which the health check prober sends packets. The default value is 443. Valid values are 1 through 65535.
- port_name str
- Not supported.
- port_specification str
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- proxy_header str
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- request_path str
- The request path of the HTTPS health check request. The default value is /.
- response str
- Creates a content-based HTTPS health check. In addition to the required HTTP 200 (OK) status code, you can configure the health check to pass only when the backend sends this specific ASCII response string within the first 1024 bytes of the HTTP response body. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-http
- weight_report_ strmode 
- Weight report mode. used for weighted Load Balancing.
- host String
- The value of the host header in the HTTPS health check request. If left empty (default value), the host header is set to the destination IP address to which health check packets are sent. The destination IP address depends on the type of load balancer. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#hc-packet-dest
- port Number
- The TCP port number to which the health check prober sends packets. The default value is 443. Valid values are 1 through 65535.
- portName String
- Not supported.
- portSpecification String
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- proxyHeader String
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- requestPath String
- The request path of the HTTPS health check request. The default value is /.
- response String
- Creates a content-based HTTPS health check. In addition to the required HTTP 200 (OK) status code, you can configure the health check to pass only when the backend sends this specific ASCII response string within the first 1024 bytes of the HTTP response body. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-http
- weightReport StringMode 
- Weight report mode. used for weighted Load Balancing.
HTTPSHealthCheckWeightReportMode, HTTPSHealthCheckWeightReportModeArgs          
- Disable
- DISABLEHealth Checker will not parse the header field.
- DryRun 
- DRY_RUNHealth Checker will parse and report the weight in the header field, but load balancing will not be based on the weights and will use equal weights.
- Enable
- ENABLEHealth Checker will try to parse and report the weight in the header field, and load balancing will be based on the weights as long as all backends have a valid weight or only a subset of backends has the UNAVAILABLE_WEIGHT WeightError. The latter case is to continue the weighted load balancing while some backends are in TIMEOUT or UNKNOWN health status.
- HTTPSHealthCheck Weight Report Mode Disable 
- DISABLEHealth Checker will not parse the header field.
- HTTPSHealthCheck Weight Report Mode Dry Run 
- DRY_RUNHealth Checker will parse and report the weight in the header field, but load balancing will not be based on the weights and will use equal weights.
- HTTPSHealthCheck Weight Report Mode Enable 
- ENABLEHealth Checker will try to parse and report the weight in the header field, and load balancing will be based on the weights as long as all backends have a valid weight or only a subset of backends has the UNAVAILABLE_WEIGHT WeightError. The latter case is to continue the weighted load balancing while some backends are in TIMEOUT or UNKNOWN health status.
- Disable
- DISABLEHealth Checker will not parse the header field.
- DryRun 
- DRY_RUNHealth Checker will parse and report the weight in the header field, but load balancing will not be based on the weights and will use equal weights.
- Enable
- ENABLEHealth Checker will try to parse and report the weight in the header field, and load balancing will be based on the weights as long as all backends have a valid weight or only a subset of backends has the UNAVAILABLE_WEIGHT WeightError. The latter case is to continue the weighted load balancing while some backends are in TIMEOUT or UNKNOWN health status.
- Disable
- DISABLEHealth Checker will not parse the header field.
- DryRun 
- DRY_RUNHealth Checker will parse and report the weight in the header field, but load balancing will not be based on the weights and will use equal weights.
- Enable
- ENABLEHealth Checker will try to parse and report the weight in the header field, and load balancing will be based on the weights as long as all backends have a valid weight or only a subset of backends has the UNAVAILABLE_WEIGHT WeightError. The latter case is to continue the weighted load balancing while some backends are in TIMEOUT or UNKNOWN health status.
- DISABLE
- DISABLEHealth Checker will not parse the header field.
- DRY_RUN
- DRY_RUNHealth Checker will parse and report the weight in the header field, but load balancing will not be based on the weights and will use equal weights.
- ENABLE
- ENABLEHealth Checker will try to parse and report the weight in the header field, and load balancing will be based on the weights as long as all backends have a valid weight or only a subset of backends has the UNAVAILABLE_WEIGHT WeightError. The latter case is to continue the weighted load balancing while some backends are in TIMEOUT or UNKNOWN health status.
- "DISABLE"
- DISABLEHealth Checker will not parse the header field.
- "DRY_RUN"
- DRY_RUNHealth Checker will parse and report the weight in the header field, but load balancing will not be based on the weights and will use equal weights.
- "ENABLE"
- ENABLEHealth Checker will try to parse and report the weight in the header field, and load balancing will be based on the weights as long as all backends have a valid weight or only a subset of backends has the UNAVAILABLE_WEIGHT WeightError. The latter case is to continue the weighted load balancing while some backends are in TIMEOUT or UNKNOWN health status.
HealthCheckLogConfig, HealthCheckLogConfigArgs        
- Enable bool
- Indicates whether or not to export logs. This is false by default, which means no health check logging will be done.
- Enable bool
- Indicates whether or not to export logs. This is false by default, which means no health check logging will be done.
- enable Boolean
- Indicates whether or not to export logs. This is false by default, which means no health check logging will be done.
- enable boolean
- Indicates whether or not to export logs. This is false by default, which means no health check logging will be done.
- enable bool
- Indicates whether or not to export logs. This is false by default, which means no health check logging will be done.
- enable Boolean
- Indicates whether or not to export logs. This is false by default, which means no health check logging will be done.
HealthCheckLogConfigResponse, HealthCheckLogConfigResponseArgs          
- Enable bool
- Indicates whether or not to export logs. This is false by default, which means no health check logging will be done.
- Enable bool
- Indicates whether or not to export logs. This is false by default, which means no health check logging will be done.
- enable Boolean
- Indicates whether or not to export logs. This is false by default, which means no health check logging will be done.
- enable boolean
- Indicates whether or not to export logs. This is false by default, which means no health check logging will be done.
- enable bool
- Indicates whether or not to export logs. This is false by default, which means no health check logging will be done.
- enable Boolean
- Indicates whether or not to export logs. This is false by default, which means no health check logging will be done.
RegionHealthCheckType, RegionHealthCheckTypeArgs        
- Grpc
- GRPC
- Http
- HTTP
- Http2
- HTTP2
- Https
- HTTPS
- Invalid
- INVALID
- Ssl
- SSL
- Tcp
- TCP
- Udp
- UDP
- RegionHealth Check Type Grpc 
- GRPC
- RegionHealth Check Type Http 
- HTTP
- RegionHealth Check Type Http2 
- HTTP2
- RegionHealth Check Type Https 
- HTTPS
- RegionHealth Check Type Invalid 
- INVALID
- RegionHealth Check Type Ssl 
- SSL
- RegionHealth Check Type Tcp 
- TCP
- RegionHealth Check Type Udp 
- UDP
- Grpc
- GRPC
- Http
- HTTP
- Http2
- HTTP2
- Https
- HTTPS
- Invalid
- INVALID
- Ssl
- SSL
- Tcp
- TCP
- Udp
- UDP
- Grpc
- GRPC
- Http
- HTTP
- Http2
- HTTP2
- Https
- HTTPS
- Invalid
- INVALID
- Ssl
- SSL
- Tcp
- TCP
- Udp
- UDP
- GRPC
- GRPC
- HTTP
- HTTP
- HTTP2
- HTTP2
- HTTPS
- HTTPS
- INVALID
- INVALID
- SSL
- SSL
- TCP
- TCP
- UDP
- UDP
- "GRPC"
- GRPC
- "HTTP"
- HTTP
- "HTTP2"
- HTTP2
- "HTTPS"
- HTTPS
- "INVALID"
- INVALID
- "SSL"
- SSL
- "TCP"
- TCP
- "UDP"
- UDP
SSLHealthCheck, SSLHealthCheckArgs    
- Port int
- The TCP port number to which the health check prober sends packets. The default value is 443. Valid values are 1 through 65535.
- PortName string
- Not supported.
- PortSpecification Pulumi.Google Native. Compute. Alpha. SSLHealth Check Port Specification 
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- ProxyHeader Pulumi.Google Native. Compute. Alpha. SSLHealth Check Proxy Header 
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- Request string
- Instructs the health check prober to send this exact ASCII string, up to 1024 bytes in length, after establishing the TCP connection and SSL handshake.
- Response string
- Creates a content-based SSL health check. In addition to establishing a TCP connection and the TLS handshake, you can configure the health check to pass only when the backend sends this exact response ASCII string, up to 1024 bytes in length. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-ssl-tcp
- Port int
- The TCP port number to which the health check prober sends packets. The default value is 443. Valid values are 1 through 65535.
- PortName string
- Not supported.
- PortSpecification SSLHealthCheck Port Specification 
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- ProxyHeader SSLHealthCheck Proxy Header 
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- Request string
- Instructs the health check prober to send this exact ASCII string, up to 1024 bytes in length, after establishing the TCP connection and SSL handshake.
- Response string
- Creates a content-based SSL health check. In addition to establishing a TCP connection and the TLS handshake, you can configure the health check to pass only when the backend sends this exact response ASCII string, up to 1024 bytes in length. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-ssl-tcp
- port Integer
- The TCP port number to which the health check prober sends packets. The default value is 443. Valid values are 1 through 65535.
- portName String
- Not supported.
- portSpecification SSLHealthCheck Port Specification 
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- proxyHeader SSLHealthCheck Proxy Header 
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- request String
- Instructs the health check prober to send this exact ASCII string, up to 1024 bytes in length, after establishing the TCP connection and SSL handshake.
- response String
- Creates a content-based SSL health check. In addition to establishing a TCP connection and the TLS handshake, you can configure the health check to pass only when the backend sends this exact response ASCII string, up to 1024 bytes in length. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-ssl-tcp
- port number
- The TCP port number to which the health check prober sends packets. The default value is 443. Valid values are 1 through 65535.
- portName string
- Not supported.
- portSpecification SSLHealthCheck Port Specification 
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- proxyHeader SSLHealthCheck Proxy Header 
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- request string
- Instructs the health check prober to send this exact ASCII string, up to 1024 bytes in length, after establishing the TCP connection and SSL handshake.
- response string
- Creates a content-based SSL health check. In addition to establishing a TCP connection and the TLS handshake, you can configure the health check to pass only when the backend sends this exact response ASCII string, up to 1024 bytes in length. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-ssl-tcp
- port int
- The TCP port number to which the health check prober sends packets. The default value is 443. Valid values are 1 through 65535.
- port_name str
- Not supported.
- port_specification SSLHealthCheck Port Specification 
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- proxy_header SSLHealthCheck Proxy Header 
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- request str
- Instructs the health check prober to send this exact ASCII string, up to 1024 bytes in length, after establishing the TCP connection and SSL handshake.
- response str
- Creates a content-based SSL health check. In addition to establishing a TCP connection and the TLS handshake, you can configure the health check to pass only when the backend sends this exact response ASCII string, up to 1024 bytes in length. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-ssl-tcp
- port Number
- The TCP port number to which the health check prober sends packets. The default value is 443. Valid values are 1 through 65535.
- portName String
- Not supported.
- portSpecification "USE_FIXED_PORT" | "USE_NAMED_PORT" | "USE_SERVING_PORT"
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- proxyHeader "NONE" | "PROXY_V1"
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- request String
- Instructs the health check prober to send this exact ASCII string, up to 1024 bytes in length, after establishing the TCP connection and SSL handshake.
- response String
- Creates a content-based SSL health check. In addition to establishing a TCP connection and the TLS handshake, you can configure the health check to pass only when the backend sends this exact response ASCII string, up to 1024 bytes in length. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-ssl-tcp
SSLHealthCheckPortSpecification, SSLHealthCheckPortSpecificationArgs        
- UseFixed Port 
- USE_FIXED_PORTThe port number in the health check's port is used for health checking. Applies to network endpoint group and instance group backends.
- UseNamed Port 
- USE_NAMED_PORTNot supported.
- UseServing Port 
- USE_SERVING_PORTFor network endpoint group backends, the health check uses the port number specified on each endpoint in the network endpoint group. For instance group backends, the health check uses the port number specified for the backend service's named port defined in the instance group's named ports.
- SSLHealthCheck Port Specification Use Fixed Port 
- USE_FIXED_PORTThe port number in the health check's port is used for health checking. Applies to network endpoint group and instance group backends.
- SSLHealthCheck Port Specification Use Named Port 
- USE_NAMED_PORTNot supported.
- SSLHealthCheck Port Specification Use Serving Port 
- USE_SERVING_PORTFor network endpoint group backends, the health check uses the port number specified on each endpoint in the network endpoint group. For instance group backends, the health check uses the port number specified for the backend service's named port defined in the instance group's named ports.
- UseFixed Port 
- USE_FIXED_PORTThe port number in the health check's port is used for health checking. Applies to network endpoint group and instance group backends.
- UseNamed Port 
- USE_NAMED_PORTNot supported.
- UseServing Port 
- USE_SERVING_PORTFor network endpoint group backends, the health check uses the port number specified on each endpoint in the network endpoint group. For instance group backends, the health check uses the port number specified for the backend service's named port defined in the instance group's named ports.
- UseFixed Port 
- USE_FIXED_PORTThe port number in the health check's port is used for health checking. Applies to network endpoint group and instance group backends.
- UseNamed Port 
- USE_NAMED_PORTNot supported.
- UseServing Port 
- USE_SERVING_PORTFor network endpoint group backends, the health check uses the port number specified on each endpoint in the network endpoint group. For instance group backends, the health check uses the port number specified for the backend service's named port defined in the instance group's named ports.
- USE_FIXED_PORT
- USE_FIXED_PORTThe port number in the health check's port is used for health checking. Applies to network endpoint group and instance group backends.
- USE_NAMED_PORT
- USE_NAMED_PORTNot supported.
- USE_SERVING_PORT
- USE_SERVING_PORTFor network endpoint group backends, the health check uses the port number specified on each endpoint in the network endpoint group. For instance group backends, the health check uses the port number specified for the backend service's named port defined in the instance group's named ports.
- "USE_FIXED_PORT"
- USE_FIXED_PORTThe port number in the health check's port is used for health checking. Applies to network endpoint group and instance group backends.
- "USE_NAMED_PORT"
- USE_NAMED_PORTNot supported.
- "USE_SERVING_PORT"
- USE_SERVING_PORTFor network endpoint group backends, the health check uses the port number specified on each endpoint in the network endpoint group. For instance group backends, the health check uses the port number specified for the backend service's named port defined in the instance group's named ports.
SSLHealthCheckProxyHeader, SSLHealthCheckProxyHeaderArgs        
- None
- NONE
- ProxyV1 
- PROXY_V1
- SSLHealthCheck Proxy Header None 
- NONE
- SSLHealthCheck Proxy Header Proxy V1 
- PROXY_V1
- None
- NONE
- ProxyV1 
- PROXY_V1
- None
- NONE
- ProxyV1 
- PROXY_V1
- NONE
- NONE
- PROXY_V1
- PROXY_V1
- "NONE"
- NONE
- "PROXY_V1"
- PROXY_V1
SSLHealthCheckResponse, SSLHealthCheckResponseArgs      
- Port int
- The TCP port number to which the health check prober sends packets. The default value is 443. Valid values are 1 through 65535.
- PortName string
- Not supported.
- PortSpecification string
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- ProxyHeader string
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- Request string
- Instructs the health check prober to send this exact ASCII string, up to 1024 bytes in length, after establishing the TCP connection and SSL handshake.
- Response string
- Creates a content-based SSL health check. In addition to establishing a TCP connection and the TLS handshake, you can configure the health check to pass only when the backend sends this exact response ASCII string, up to 1024 bytes in length. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-ssl-tcp
- Port int
- The TCP port number to which the health check prober sends packets. The default value is 443. Valid values are 1 through 65535.
- PortName string
- Not supported.
- PortSpecification string
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- ProxyHeader string
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- Request string
- Instructs the health check prober to send this exact ASCII string, up to 1024 bytes in length, after establishing the TCP connection and SSL handshake.
- Response string
- Creates a content-based SSL health check. In addition to establishing a TCP connection and the TLS handshake, you can configure the health check to pass only when the backend sends this exact response ASCII string, up to 1024 bytes in length. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-ssl-tcp
- port Integer
- The TCP port number to which the health check prober sends packets. The default value is 443. Valid values are 1 through 65535.
- portName String
- Not supported.
- portSpecification String
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- proxyHeader String
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- request String
- Instructs the health check prober to send this exact ASCII string, up to 1024 bytes in length, after establishing the TCP connection and SSL handshake.
- response String
- Creates a content-based SSL health check. In addition to establishing a TCP connection and the TLS handshake, you can configure the health check to pass only when the backend sends this exact response ASCII string, up to 1024 bytes in length. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-ssl-tcp
- port number
- The TCP port number to which the health check prober sends packets. The default value is 443. Valid values are 1 through 65535.
- portName string
- Not supported.
- portSpecification string
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- proxyHeader string
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- request string
- Instructs the health check prober to send this exact ASCII string, up to 1024 bytes in length, after establishing the TCP connection and SSL handshake.
- response string
- Creates a content-based SSL health check. In addition to establishing a TCP connection and the TLS handshake, you can configure the health check to pass only when the backend sends this exact response ASCII string, up to 1024 bytes in length. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-ssl-tcp
- port int
- The TCP port number to which the health check prober sends packets. The default value is 443. Valid values are 1 through 65535.
- port_name str
- Not supported.
- port_specification str
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- proxy_header str
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- request str
- Instructs the health check prober to send this exact ASCII string, up to 1024 bytes in length, after establishing the TCP connection and SSL handshake.
- response str
- Creates a content-based SSL health check. In addition to establishing a TCP connection and the TLS handshake, you can configure the health check to pass only when the backend sends this exact response ASCII string, up to 1024 bytes in length. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-ssl-tcp
- port Number
- The TCP port number to which the health check prober sends packets. The default value is 443. Valid values are 1 through 65535.
- portName String
- Not supported.
- portSpecification String
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- proxyHeader String
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- request String
- Instructs the health check prober to send this exact ASCII string, up to 1024 bytes in length, after establishing the TCP connection and SSL handshake.
- response String
- Creates a content-based SSL health check. In addition to establishing a TCP connection and the TLS handshake, you can configure the health check to pass only when the backend sends this exact response ASCII string, up to 1024 bytes in length. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-ssl-tcp
TCPHealthCheck, TCPHealthCheckArgs    
- Port int
- The TCP port number to which the health check prober sends packets. The default value is 80. Valid values are 1 through 65535.
- PortName string
- Not supported.
- PortSpecification Pulumi.Google Native. Compute. Alpha. TCPHealth Check Port Specification 
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- ProxyHeader Pulumi.Google Native. Compute. Alpha. TCPHealth Check Proxy Header 
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- Request string
- Instructs the health check prober to send this exact ASCII string, up to 1024 bytes in length, after establishing the TCP connection.
- Response string
- Creates a content-based TCP health check. In addition to establishing a TCP connection, you can configure the health check to pass only when the backend sends this exact response ASCII string, up to 1024 bytes in length. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-ssl-tcp
- Port int
- The TCP port number to which the health check prober sends packets. The default value is 80. Valid values are 1 through 65535.
- PortName string
- Not supported.
- PortSpecification TCPHealthCheck Port Specification 
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- ProxyHeader TCPHealthCheck Proxy Header 
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- Request string
- Instructs the health check prober to send this exact ASCII string, up to 1024 bytes in length, after establishing the TCP connection.
- Response string
- Creates a content-based TCP health check. In addition to establishing a TCP connection, you can configure the health check to pass only when the backend sends this exact response ASCII string, up to 1024 bytes in length. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-ssl-tcp
- port Integer
- The TCP port number to which the health check prober sends packets. The default value is 80. Valid values are 1 through 65535.
- portName String
- Not supported.
- portSpecification TCPHealthCheck Port Specification 
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- proxyHeader TCPHealthCheck Proxy Header 
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- request String
- Instructs the health check prober to send this exact ASCII string, up to 1024 bytes in length, after establishing the TCP connection.
- response String
- Creates a content-based TCP health check. In addition to establishing a TCP connection, you can configure the health check to pass only when the backend sends this exact response ASCII string, up to 1024 bytes in length. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-ssl-tcp
- port number
- The TCP port number to which the health check prober sends packets. The default value is 80. Valid values are 1 through 65535.
- portName string
- Not supported.
- portSpecification TCPHealthCheck Port Specification 
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- proxyHeader TCPHealthCheck Proxy Header 
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- request string
- Instructs the health check prober to send this exact ASCII string, up to 1024 bytes in length, after establishing the TCP connection.
- response string
- Creates a content-based TCP health check. In addition to establishing a TCP connection, you can configure the health check to pass only when the backend sends this exact response ASCII string, up to 1024 bytes in length. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-ssl-tcp
- port int
- The TCP port number to which the health check prober sends packets. The default value is 80. Valid values are 1 through 65535.
- port_name str
- Not supported.
- port_specification TCPHealthCheck Port Specification 
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- proxy_header TCPHealthCheck Proxy Header 
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- request str
- Instructs the health check prober to send this exact ASCII string, up to 1024 bytes in length, after establishing the TCP connection.
- response str
- Creates a content-based TCP health check. In addition to establishing a TCP connection, you can configure the health check to pass only when the backend sends this exact response ASCII string, up to 1024 bytes in length. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-ssl-tcp
- port Number
- The TCP port number to which the health check prober sends packets. The default value is 80. Valid values are 1 through 65535.
- portName String
- Not supported.
- portSpecification "USE_FIXED_PORT" | "USE_NAMED_PORT" | "USE_SERVING_PORT"
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- proxyHeader "NONE" | "PROXY_V1"
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- request String
- Instructs the health check prober to send this exact ASCII string, up to 1024 bytes in length, after establishing the TCP connection.
- response String
- Creates a content-based TCP health check. In addition to establishing a TCP connection, you can configure the health check to pass only when the backend sends this exact response ASCII string, up to 1024 bytes in length. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-ssl-tcp
TCPHealthCheckPortSpecification, TCPHealthCheckPortSpecificationArgs        
- UseFixed Port 
- USE_FIXED_PORTThe port number in the health check's port is used for health checking. Applies to network endpoint group and instance group backends.
- UseNamed Port 
- USE_NAMED_PORTNot supported.
- UseServing Port 
- USE_SERVING_PORTFor network endpoint group backends, the health check uses the port number specified on each endpoint in the network endpoint group. For instance group backends, the health check uses the port number specified for the backend service's named port defined in the instance group's named ports.
- TCPHealthCheck Port Specification Use Fixed Port 
- USE_FIXED_PORTThe port number in the health check's port is used for health checking. Applies to network endpoint group and instance group backends.
- TCPHealthCheck Port Specification Use Named Port 
- USE_NAMED_PORTNot supported.
- TCPHealthCheck Port Specification Use Serving Port 
- USE_SERVING_PORTFor network endpoint group backends, the health check uses the port number specified on each endpoint in the network endpoint group. For instance group backends, the health check uses the port number specified for the backend service's named port defined in the instance group's named ports.
- UseFixed Port 
- USE_FIXED_PORTThe port number in the health check's port is used for health checking. Applies to network endpoint group and instance group backends.
- UseNamed Port 
- USE_NAMED_PORTNot supported.
- UseServing Port 
- USE_SERVING_PORTFor network endpoint group backends, the health check uses the port number specified on each endpoint in the network endpoint group. For instance group backends, the health check uses the port number specified for the backend service's named port defined in the instance group's named ports.
- UseFixed Port 
- USE_FIXED_PORTThe port number in the health check's port is used for health checking. Applies to network endpoint group and instance group backends.
- UseNamed Port 
- USE_NAMED_PORTNot supported.
- UseServing Port 
- USE_SERVING_PORTFor network endpoint group backends, the health check uses the port number specified on each endpoint in the network endpoint group. For instance group backends, the health check uses the port number specified for the backend service's named port defined in the instance group's named ports.
- USE_FIXED_PORT
- USE_FIXED_PORTThe port number in the health check's port is used for health checking. Applies to network endpoint group and instance group backends.
- USE_NAMED_PORT
- USE_NAMED_PORTNot supported.
- USE_SERVING_PORT
- USE_SERVING_PORTFor network endpoint group backends, the health check uses the port number specified on each endpoint in the network endpoint group. For instance group backends, the health check uses the port number specified for the backend service's named port defined in the instance group's named ports.
- "USE_FIXED_PORT"
- USE_FIXED_PORTThe port number in the health check's port is used for health checking. Applies to network endpoint group and instance group backends.
- "USE_NAMED_PORT"
- USE_NAMED_PORTNot supported.
- "USE_SERVING_PORT"
- USE_SERVING_PORTFor network endpoint group backends, the health check uses the port number specified on each endpoint in the network endpoint group. For instance group backends, the health check uses the port number specified for the backend service's named port defined in the instance group's named ports.
TCPHealthCheckProxyHeader, TCPHealthCheckProxyHeaderArgs        
- None
- NONE
- ProxyV1 
- PROXY_V1
- TCPHealthCheck Proxy Header None 
- NONE
- TCPHealthCheck Proxy Header Proxy V1 
- PROXY_V1
- None
- NONE
- ProxyV1 
- PROXY_V1
- None
- NONE
- ProxyV1 
- PROXY_V1
- NONE
- NONE
- PROXY_V1
- PROXY_V1
- "NONE"
- NONE
- "PROXY_V1"
- PROXY_V1
TCPHealthCheckResponse, TCPHealthCheckResponseArgs      
- Port int
- The TCP port number to which the health check prober sends packets. The default value is 80. Valid values are 1 through 65535.
- PortName string
- Not supported.
- PortSpecification string
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- ProxyHeader string
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- Request string
- Instructs the health check prober to send this exact ASCII string, up to 1024 bytes in length, after establishing the TCP connection.
- Response string
- Creates a content-based TCP health check. In addition to establishing a TCP connection, you can configure the health check to pass only when the backend sends this exact response ASCII string, up to 1024 bytes in length. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-ssl-tcp
- Port int
- The TCP port number to which the health check prober sends packets. The default value is 80. Valid values are 1 through 65535.
- PortName string
- Not supported.
- PortSpecification string
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- ProxyHeader string
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- Request string
- Instructs the health check prober to send this exact ASCII string, up to 1024 bytes in length, after establishing the TCP connection.
- Response string
- Creates a content-based TCP health check. In addition to establishing a TCP connection, you can configure the health check to pass only when the backend sends this exact response ASCII string, up to 1024 bytes in length. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-ssl-tcp
- port Integer
- The TCP port number to which the health check prober sends packets. The default value is 80. Valid values are 1 through 65535.
- portName String
- Not supported.
- portSpecification String
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- proxyHeader String
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- request String
- Instructs the health check prober to send this exact ASCII string, up to 1024 bytes in length, after establishing the TCP connection.
- response String
- Creates a content-based TCP health check. In addition to establishing a TCP connection, you can configure the health check to pass only when the backend sends this exact response ASCII string, up to 1024 bytes in length. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-ssl-tcp
- port number
- The TCP port number to which the health check prober sends packets. The default value is 80. Valid values are 1 through 65535.
- portName string
- Not supported.
- portSpecification string
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- proxyHeader string
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- request string
- Instructs the health check prober to send this exact ASCII string, up to 1024 bytes in length, after establishing the TCP connection.
- response string
- Creates a content-based TCP health check. In addition to establishing a TCP connection, you can configure the health check to pass only when the backend sends this exact response ASCII string, up to 1024 bytes in length. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-ssl-tcp
- port int
- The TCP port number to which the health check prober sends packets. The default value is 80. Valid values are 1 through 65535.
- port_name str
- Not supported.
- port_specification str
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- proxy_header str
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- request str
- Instructs the health check prober to send this exact ASCII string, up to 1024 bytes in length, after establishing the TCP connection.
- response str
- Creates a content-based TCP health check. In addition to establishing a TCP connection, you can configure the health check to pass only when the backend sends this exact response ASCII string, up to 1024 bytes in length. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-ssl-tcp
- port Number
- The TCP port number to which the health check prober sends packets. The default value is 80. Valid values are 1 through 65535.
- portName String
- Not supported.
- portSpecification String
- Specifies how a port is selected for health checking. Can be one of the following values: USE_FIXED_PORT: Specifies a port number explicitly using the port field in the health check. Supported by backend services for pass-through load balancers and backend services for proxy load balancers. Not supported by target pools. The health check supports all backends supported by the backend service provided the backend can be health checked. For example, GCE_VM_IP network endpoint groups, GCE_VM_IP_PORT network endpoint groups, and instance group backends. USE_NAMED_PORT: Not supported. USE_SERVING_PORT: Provides an indirect method of specifying the health check port by referring to the backend service. Only supported by backend services for proxy load balancers. Not supported by target pools. Not supported by backend services for pass-through load balancers. Supports all backends that can be health checked; for example, GCE_VM_IP_PORT network endpoint groups and instance group backends. For GCE_VM_IP_PORT network endpoint group backends, the health check uses the port number specified for each endpoint in the network endpoint group. For instance group backends, the health check uses the port number determined by looking up the backend service's named port in the instance group's list of named ports.
- proxyHeader String
- Specifies the type of proxy header to append before sending data to the backend, either NONE or PROXY_V1. The default is NONE.
- request String
- Instructs the health check prober to send this exact ASCII string, up to 1024 bytes in length, after establishing the TCP connection.
- response String
- Creates a content-based TCP health check. In addition to establishing a TCP connection, you can configure the health check to pass only when the backend sends this exact response ASCII string, up to 1024 bytes in length. For details, see: https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-ssl-tcp
UDPHealthCheck, UDPHealthCheckArgs    
- Port int
- The UDP port number to which the health check prober sends packets. Valid values are 1 through 65535.
- PortName string
- Not supported.
- Request string
- Raw data of request to send in payload of UDP packet. It is an error if this is empty. The request data can only be ASCII.
- Response string
- The bytes to match against the beginning of the response data. It is an error if this is empty. The response data can only be ASCII.
- Port int
- The UDP port number to which the health check prober sends packets. Valid values are 1 through 65535.
- PortName string
- Not supported.
- Request string
- Raw data of request to send in payload of UDP packet. It is an error if this is empty. The request data can only be ASCII.
- Response string
- The bytes to match against the beginning of the response data. It is an error if this is empty. The response data can only be ASCII.
- port Integer
- The UDP port number to which the health check prober sends packets. Valid values are 1 through 65535.
- portName String
- Not supported.
- request String
- Raw data of request to send in payload of UDP packet. It is an error if this is empty. The request data can only be ASCII.
- response String
- The bytes to match against the beginning of the response data. It is an error if this is empty. The response data can only be ASCII.
- port number
- The UDP port number to which the health check prober sends packets. Valid values are 1 through 65535.
- portName string
- Not supported.
- request string
- Raw data of request to send in payload of UDP packet. It is an error if this is empty. The request data can only be ASCII.
- response string
- The bytes to match against the beginning of the response data. It is an error if this is empty. The response data can only be ASCII.
- port int
- The UDP port number to which the health check prober sends packets. Valid values are 1 through 65535.
- port_name str
- Not supported.
- request str
- Raw data of request to send in payload of UDP packet. It is an error if this is empty. The request data can only be ASCII.
- response str
- The bytes to match against the beginning of the response data. It is an error if this is empty. The response data can only be ASCII.
- port Number
- The UDP port number to which the health check prober sends packets. Valid values are 1 through 65535.
- portName String
- Not supported.
- request String
- Raw data of request to send in payload of UDP packet. It is an error if this is empty. The request data can only be ASCII.
- response String
- The bytes to match against the beginning of the response data. It is an error if this is empty. The response data can only be ASCII.
UDPHealthCheckResponse, UDPHealthCheckResponseArgs      
- Port int
- The UDP port number to which the health check prober sends packets. Valid values are 1 through 65535.
- PortName string
- Not supported.
- Request string
- Raw data of request to send in payload of UDP packet. It is an error if this is empty. The request data can only be ASCII.
- Response string
- The bytes to match against the beginning of the response data. It is an error if this is empty. The response data can only be ASCII.
- Port int
- The UDP port number to which the health check prober sends packets. Valid values are 1 through 65535.
- PortName string
- Not supported.
- Request string
- Raw data of request to send in payload of UDP packet. It is an error if this is empty. The request data can only be ASCII.
- Response string
- The bytes to match against the beginning of the response data. It is an error if this is empty. The response data can only be ASCII.
- port Integer
- The UDP port number to which the health check prober sends packets. Valid values are 1 through 65535.
- portName String
- Not supported.
- request String
- Raw data of request to send in payload of UDP packet. It is an error if this is empty. The request data can only be ASCII.
- response String
- The bytes to match against the beginning of the response data. It is an error if this is empty. The response data can only be ASCII.
- port number
- The UDP port number to which the health check prober sends packets. Valid values are 1 through 65535.
- portName string
- Not supported.
- request string
- Raw data of request to send in payload of UDP packet. It is an error if this is empty. The request data can only be ASCII.
- response string
- The bytes to match against the beginning of the response data. It is an error if this is empty. The response data can only be ASCII.
- port int
- The UDP port number to which the health check prober sends packets. Valid values are 1 through 65535.
- port_name str
- Not supported.
- request str
- Raw data of request to send in payload of UDP packet. It is an error if this is empty. The request data can only be ASCII.
- response str
- The bytes to match against the beginning of the response data. It is an error if this is empty. The response data can only be ASCII.
- port Number
- The UDP port number to which the health check prober sends packets. Valid values are 1 through 65535.
- portName String
- Not supported.
- request String
- Raw data of request to send in payload of UDP packet. It is an error if this is empty. The request data can only be ASCII.
- response String
- The bytes to match against the beginning of the response data. It is an error if this is empty. The response data can only be ASCII.
Package Details
- Repository
- Google Cloud Native pulumi/pulumi-google-native
- License
- Apache-2.0
Google Cloud Native is in preview. Google Cloud Classic is fully supported.