Reference documentation and code samples for the Compute Engine v1 API enum SSLHealthCheck.Types.PortSpecification.
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 passthrough 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 passthrough 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.
A value indicating that the enum field is not set.
UseFixedPort
The port number in the health check's port is used for health checking. Applies to network endpoint group and instance group backends.
UseNamedPort
Not supported.
UseServingPort
For 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.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-08 UTC."],[[["\u003cp\u003eThis document provides reference information for the \u003ccode\u003eSSLHealthCheck.Types.PortSpecification\u003c/code\u003e enum within the Google Compute Engine v1 API, specifically across various versions of the .NET library, starting from version 1.0.0 up to the latest version 3.6.0.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003ePortSpecification\u003c/code\u003e enum dictates how a port is selected for health checking, offering options such as \u003ccode\u003eUSE_FIXED_PORT\u003c/code\u003e, which specifies a port number explicitly, \u003ccode\u003eUSE_NAMED_PORT\u003c/code\u003e which is noted as not being supported, and \u003ccode\u003eUSE_SERVING_PORT\u003c/code\u003e, which indirectly specifies the port via the backend service.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eUSE_FIXED_PORT\u003c/code\u003e option is applicable to both network endpoint groups and instance group backends, whereas the \u003ccode\u003eUSE_SERVING_PORT\u003c/code\u003e option is exclusively for backend services for proxy load balancers and details how it determines the port number for different types of backends.\u003c/p\u003e\n"],["\u003cp\u003eThe documentation includes a field \u003ccode\u003eUndefinedPortSpecification\u003c/code\u003e to be used when the enum field is not set.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003ePortSpecification\u003c/code\u003e documentation is located within the \u003ccode\u003eGoogle.Cloud.Compute.V1\u003c/code\u003e namespace and the \u003ccode\u003eGoogle.Cloud.Compute.V1.dll\u003c/code\u003e assembly.\u003c/p\u003e\n"]]],[],null,[]]
