[[["이해하기 쉬움","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-03-12(UTC)"],[[["This guide explains how to migrate client-to-Apigee routing from a managed instance group (MIG) to a Private Service Connect (PSC) based configuration."],["The migration is relevant for those currently using a Global external HTTPS Load Balancer (Classic) with a managed instance group (MIG) for routing traffic to Apigee and want to switch to using PSC."],["Migration involves configuring northbound routing to Apigee endpoints using the Apigee CLI, creating NEGs for multi-region use cases, testing the new load balancer, and switching DNS entries to the new load balancer endpoint."],["Because the global external HTTPS load balancer does not support PSC NEG backends, a new global external HTTPS load balancer needs to be created and have the traffic switched to it."]]],[]]