内部ロードバランサを作成する際に、内部ロードバランサ サービスを Service Directory に自動的に登録するかどうかを選択できます。これにより、クライアント アプリケーションは HTTP、gRPC、または DNS 経由で Service Directory を使用して、内部ロードバランサ サービスのアドレスを解決し、解決したアドレスに直接接続できます。
内部ロードバランサを Service Directory に登録すると、次のことが可能になります。
.internal ドメインで内部的に生成された DNS 名を介してのみ内部ロードバランサにアクセスする DNS ではなく、内部ロードバランサのネットワーク ロケーションを提供するカスタム DNS 名を選択します。
同じ DNS ドメイン名から複数の内部ロードバランサを提供します。これは、現在の自動生成 DNS レコードでは不可能です。
内部ロードバランサを Service Directory に直接かつ自動的に登録することで、 Google Cloudのすべてのサービスに単一のリポジトリを提供します。
Service Directory API の単一コマンドによって、スタンドアロン サービス、エンドポイント、内部ロードバランサのエンドポイントを確認します。
名前空間またはサービスレベルで Service Directory リソースにアクセス制御などの管理アクションを適用し、内部ロードバランサ エンドポイントと他のバックエンド サービスの両方を含めます。
[[["わかりやすい","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 UTC。"],[],[],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)."]]
