[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-08-22。"],[],[],null,["# Network endpoint groups overview\n\nA network endpoint group (NEG) is a configuration object that specifies a group\nof backend endpoints or services. With NEGs,\nGoogle Cloud load balancers can serve virtual machine (VM) instance group-based\nworkloads, serverless workloads, and containerized workloads. NEGs let you distribute traffic to your\nload balancer's backends at a more granular level (for example, [load balancing\ntraffic at the Pod\nlevel](/kubernetes-engine/docs/concepts/container-native-load-balancing#benefits)\ninstead of at the VM-level for GKE workloads).\n\nYou can configure NEGs as [backends](/load-balancing/docs/features#backends) for\nyour load balancers. Certain NEG types can also be used with Cloud Service Mesh.\nUse the following tables to decide which type of NEG you need for your\ndeployment.\n\n- [Zonal NEG](#zonal-neg)\n- [Internet NEG](#internet-neg)\n- [Serverless NEG](#serverless-neg)\n- [Hybrid connectivity NEG](#hybrid-neg)\n- [Private Service Connect NEG](#psc-neg)\n- [Port mapping NEG](#port-mapping-neg)\n\nZonal NEG\n---------\n\nInternet NEG\n------------\n\nServerless NEG\n--------------\n\nHybrid connectivity NEG\n-----------------------\n\nPrivate Service Connect NEG\n---------------------------\n\nPort mapping NEG\n----------------"]]