내부 부하 분산기를 만들 때 서비스 디렉터리에 내부 부하 분산기 서비스를 자동으로 등록하도록 선택할 수 있습니다. 이렇게 하면 HTTP, gRPC 또는 DNS를 통해 서비스 디렉터리를 사용하여 내부 부하 분산기 서비스 주소를 확인하고 여기에 직접 연결하도록 클라이언트 애플리케이션을 사용 설정합니다.
서비스 디렉터리에 내부 부하 분산기를 등록하면 다음을 수행할 수 있습니다.
.internal 도메인에서 내부적으로 생성된 DNS 이름을 통해서만 내부 부하 분산기에 액세스하는 DNS와 달리 내부 부하 분산기의 네트워크 위치를 제공할 커스텀 DNS 이름을 선택합니다.
동일한 DNS 도메인 이름에서 여러 내부 부하 분산기를 제공합니다. 그렇지 않은 경우 현재 자동 생성된 DNS 레코드로는 불가능합니다.
내부 부하 분산기를 서비스 디렉터리에 직접 자동으로 등록하여 Google Cloud의 모든 서비스에 대한 단일 저장소를 제공합니다.
서비스 디렉터리 API에서 명령어 하나로 독립형 서비스, 엔드포인트, 내부 부하 분산기 엔드포인트를 확인합니다.
내부 부하 분산기 엔드포인트와 다른 백엔드 서비스를 모두 포함하려면 네임스페이스 또는 서비스 수준의 서비스 디렉터리 리소스에 액세스 제어와 같은 관리 작업을 적용합니다.
SD_SERVICE_NAME: 엔드포인트를 등록할 서비스 디렉터리 서비스의 정규화된 이름. 이 서비스는 만들려는 전달 규칙과 동일한 프로젝트 및 리전에 있어야 합니다.
예:
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(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)."]]
