Google Cloud 콘솔, gcloud CLI, API, Terraform, 구성 커넥터를 사용하여 애플리케이션 부하 분산기를 설정하고 독립형 NEG를 사용자 관리 백엔드 서비스에 연결합니다.
다음 표에는 부하 분산기를 GKE 클러스터의 Fleet에 연결할 수 있는 다양한 방법이 나와 있습니다. 다음 표에 나열되지 않은 부하 분산기 기능 비교 페이지의 모든 기능은 부하 분산용 Kubernetes 기반 API를 사용하는 대신 독립형 NEG가 있는 사용자 관리 부하 분산기와 함께 작동해야 합니다.
[[["이해하기 쉬움","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-08-08(UTC)"],[],[],null,["# Choose your multi-cluster load balancing API for GKE\n\n[Autopilot](/kubernetes-engine/docs/concepts/autopilot-overview) [Standard](/kubernetes-engine/docs/concepts/choose-cluster-mode)\n\n*** ** * ** ***\n\nThis page helps you choose the most suitable API for\ndeploying load balancers to distribute traffic across a fleet of\nGoogle Kubernetes Engine (GKE) clusters.\n\nYou can attach a load balancer to your fleet of GKE clusters in\nthe following ways:\n\n1. Use the Multi Cluster Ingress APIs\n such as the [Multi Cluster Ingress](/kubernetes-engine/docs/concepts/multi-cluster-ingress#multiclusteringress_resource)\n and\n [MultiClusterService](/kubernetes-engine/docs/concepts/multi-cluster-ingress#multiclusterservice_resources)\n resources.\n\n2. Use the Gateway APIs\n ([GatewayClass](/kubernetes-engine/docs/concepts/gateway-api#gatewayclass),\n [Gateway](/kubernetes-engine/docs/concepts/gateway-api#gateway),\n [HTTPRoute](/kubernetes-engine/docs/concepts/gateway-api#httproute),\n [Policy](/kubernetes-engine/docs/concepts/gateway-api#policy),\n [ServiceExport](/kubernetes-engine/docs/how-to/deploying-multi-cluster-gateways#mcs),\n and\n [ServiceImport](/kubernetes-engine/docs/how-to/deploying-multi-cluster-gateways#mcs)\n resources).\n\n3. Set up the [Application Load Balancer](/load-balancing/docs/application-load-balancer)\n using Google Cloud console, gcloud CLI, API, Terraform, Config Connector and attach\n [Standalone NEGs](/kubernetes-engine/docs/how-to/standalone-neg) to the\n user-managed backend services.\n\nThe following table lists the different ways in which you can attach a\nload balancer to your fleet of GKE clusters. Any features listed\nin the [Load balancer feature comparison](/load-balancing/docs/features) page\nthat aren't listed in the following table should work with a\nuser-managed load balancer with Standalone NEGs, instead of relying on\nthe Kubernetes-native API for load balancing.\n\nWhat's next\n-----------\n\n- [Set up multi-cluster Ingress](/kubernetes-engine/docs/how-to/multi-cluster-ingress-setup).\n- [Deploying Ingress across clusters](/kubernetes-engine/docs/how-to/multi-cluster-ingress).\n- [Enable multi-cluster Gateway](/kubernetes-engine/docs/how-to/enabling-multi-cluster-gateways).\n- [Deploy multi-cluster Gateways](/kubernetes-engine/docs/how-to/deploying-multi-cluster-gateways).\n- [Container-native load balancing through standalone zonal NEGs](/kubernetes-engine/docs/how-to/standalone-neg)."]]
