This product or feature is subject to the "Pre-GA Offerings Terms" in the General Service Terms section of theService Specific Terms. Pre-GA products and features are available "as is" and might have limited support. For more information, see thelaunch stage descriptions.

You can choose to automatically register your internal load balancer servicewith Service Directory when you create an internal load balancer. This enables clientapplications to use Service Directory through HTTP, gRPC, or DNS to resolvethe address of the internal load balancer service and connect to it directly.

Registering your internal load balancer with Service Directory lets you do thefollowing:

• Choose custom DNS names to serve the network locations of yourinternal load balancers as opposed to DNS accessing your internal loadbalancer only through an internally generated DNS name in the.internal domain.
• Serve multiple internal load balancers from the same DNS domain name,which is otherwise not possible with the current auto-generated DNS records.
• Register internal load balancers directly and automatically inService Directory providing a single repository for all your servicesin Google Cloud.
• See standalone services, endpoints, and your internal loadbalancer endpoints with a single command in the Service Directory API.
• Apply administrative actions like access control to Service Directoryresources at the namespace or service level to encompass both your internalload balancer endpoints as well as other backend services.

This feature is subject to the "Pre-GA Offerings Terms" in the General Service Terms section of theService Specific Terms. Pre-GA features are available "as is" and might have limited support. For more information, see thelaunch stage descriptions.

To register a regional internal Application Load Balancer, run thegcloud compute forwarding-rulescreate command andset theservice-directory-registration flag:

gcloud beta compute forwarding-rules createFORWARDING_RULE_NAME \    --region=REGION \    --load-balancing-scheme=INTERNAL_MANAGED \    --network=NETWORK_NAME \    --address=RESERVED_IP_ADDRESS \    --target-https-proxy=PROXY_NAME \    --target-https-proxy-region=PROXY_REGION \    --ports=PORT_NUMBER \    --service-directory-registration=SD_SERVICE_NAME

Replace the following:

• FORWARDING_RULE_NAME: a name for the forwarding rulethat you want to create
• REGION: the region to create the forwarding rule in
• NETWORK_NAME: the network that this forwarding ruleapplies to
• RESERVED_IP_ADDRESS: the IP address that the forwardingrule serves
• PROXY_NAME: the target proxy that receives the traffic
• PROXY_REGION: the region of the proxy to operate on
• PORT_NUMBER: a list of comma-separated ports
• SD_SERVICE_NAME: the fully qualified name of theService Directory service where you want to register the endpoint. Thisservice must be in the same project and region as the forwarding rule beingcreated. For example: projects/PROJECT/locations/REGION/namespaces/NAMESPACE_NAME/services/SERVICE_NAME.

What's next

• To learn more about Service Directory, seeService Directory overview.
• To learn about limitations of Service Directory integration withregional internal Application Load Balancer and how to verify the endpoint, seeRegister an internal load balancer.