SD_SERVICE_NAME:您要註冊端點的 Service Directory 服務完整名稱。這項服務必須與要建立的轉送規則位於相同專案和區域。例如:
projects/PROJECT/locations/REGION/namespaces/NAMESPACE_NAME/services/SERVICE_NAME。
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-09-04 (世界標準時間)。"],[],[],null,["# Regional internal Application Load Balancer and Service Directory overview\n\n| **Preview**\n|\n|\n| This feature is subject to the \"Pre-GA Offerings Terms\" in the General Service Terms section\n| of the [Service Specific Terms](/terms/service-terms#1).\n|\n| Pre-GA features are available \"as is\" and might have limited support.\n|\n| For more information, see the\n| [launch stage descriptions](/products#product-launch-stages).\n\nYou can choose to automatically register your internal load balancer service\nwith Service Directory when you create an internal load balancer. This enables client\napplications to use Service Directory through HTTP, gRPC, or DNS to resolve\nthe address of the internal load balancer service and connect to it directly.\n\nRegistering your internal load balancer with Service Directory lets you do the\nfollowing:\n\n- Choose custom DNS names to serve the network locations of your internal load balancers as opposed to DNS accessing your internal load balancer only through an internally generated DNS name in the `.internal` domain.\n- Serve multiple internal load balancers from the same DNS domain name, which is otherwise not possible with the current auto-generated DNS records.\n- Register internal load balancers directly and automatically in Service Directory providing a single repository for all your services in Google Cloud.\n- See standalone services, endpoints, and your internal load balancer endpoints with a single command in the Service Directory API.\n- Apply administrative actions like access control to Service Directory resources at the namespace or service level to encompass both your internal load balancer endpoints as well as other backend services.\n\n| **Note:** Cross-region internal Application Load Balancers don't support Service Directory registrations.\n\nRegister a regional internal Application Load Balancer with Service Directory\n-----------------------------------------------------------------------------\n\n|\n| **Preview**\n|\n|\n| This feature is subject to the \"Pre-GA Offerings Terms\" in the General Service Terms section\n| of the [Service Specific Terms](/terms/service-terms#1).\n|\n| Pre-GA features are available \"as is\" and might have limited support.\n|\n| For more information, see the\n| [launch stage descriptions](/products#product-launch-stages).\n\nTo register a regional internal Application Load Balancer, run the [`gcloud compute forwarding-rules\ncreate` command](/sdk/gcloud/reference/compute/forwarding-rules/create) and\nset the `service-directory-registration` flag: \n\n```\ngcloud beta compute forwarding-rules create FORWARDING_RULE_NAME \\\n --region=REGION \\\n --load-balancing-scheme=INTERNAL_MANAGED \\\n --network=NETWORK_NAME \\\n --address=RESERVED_IP_ADDRESS \\\n --target-https-proxy=PROXY_NAME \\\n --target-https-proxy-region=PROXY_REGION \\\n --ports=PORT_NUMBER \\\n --service-directory-registration=SD_SERVICE_NAME\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eFORWARDING_RULE_NAME\u003c/var\u003e: a name for the forwarding rule that you want to create\n- \u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e: the region to create the forwarding rule in\n- \u003cvar translate=\"no\"\u003eNETWORK_NAME\u003c/var\u003e: the network that this forwarding rule applies to\n- \u003cvar translate=\"no\"\u003eRESERVED_IP_ADDRESS\u003c/var\u003e: the IP address that the forwarding rule serves\n- \u003cvar translate=\"no\"\u003ePROXY_NAME\u003c/var\u003e: the target proxy that receives the traffic\n- \u003cvar translate=\"no\"\u003ePROXY_REGION\u003c/var\u003e: the region of the proxy to operate on\n- \u003cvar translate=\"no\"\u003ePORT_NUMBER\u003c/var\u003e: a list of comma-separated ports\n- \u003cvar translate=\"no\"\u003eSD_SERVICE_NAME\u003c/var\u003e: the fully qualified name of the Service Directory service where you want to register the endpoint. This service must be in the same project and region as the forwarding rule being created. For example: projects/\u003cvar translate=\"no\"\u003ePROJECT\u003c/var\u003e/locations/\u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e/namespaces/\u003cvar translate=\"no\"\u003eNAMESPACE_NAME\u003c/var\u003e/services/\u003cvar translate=\"no\"\u003eSERVICE_NAME\u003c/var\u003e.\n\nWhat's next\n-----------\n\n- To learn more about Service Directory, see [Service Directory overview](/service-directory/docs/overview).\n- To learn about limitations of Service Directory integration with regional internal Application Load Balancer and how to verify the endpoint, see [Register an internal load balancer](/service-directory/docs/configuring-ilb-in-sd)."]]