Artifact Registry에 액세스해야 하는 Google Cloud 서비스가 Binary Authorization, Artifact Analysis, 런타임 환경(예: Google Kubernetes Engine 및 Cloud Run)을 포함한 서비스 경계 내에 있는지 확인합니다. 각 서비스에 대한 자세한 내용은 지원 서비스 목록을 참조하세요.
Artifact Registry를 서비스 경계에 추가하는 방법에 대한 일반적인 안내는 서비스 경계 만들기를 참조하세요.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2024-12-21(UTC)"],[[["\u003cp\u003eVPC Service Controls enhances security by allowing you to configure perimeters around Google Cloud-managed services and manage data movement across these boundaries.\u003c/p\u003e\n"],["\u003cp\u003eWhen using Artifact Registry within a service perimeter, you can access container images inside the perimeter as well as Google Cloud-provided images, but cached Docker Hub images on \u003ccode\u003emirror.gcr.io\u003c/code\u003e require an added egress rule.\u003c/p\u003e\n"],["\u003cp\u003eTo enable \u003ccode\u003emirror.gcr.io\u003c/code\u003e access within a service perimeter, you need to add a specific egress rule that allows the \u003ccode\u003eartifactregistry.googleapis.com/DockerRead\u003c/code\u003e method to access the specified project.\u003c/p\u003e\n"],["\u003cp\u003eArtifact Registry can be accessed using default Google APIs and services domains' IP addresses, or special IPs like \u003ccode\u003e199.36.153.4/30\u003c/code\u003e (\u003ccode\u003erestricted.googleapis.com\u003c/code\u003e) and \u003ccode\u003e199.36.153.8/30\u003c/code\u003e (\u003ccode\u003eprivate.googleapis.com\u003c/code\u003e).\u003c/p\u003e\n"],["\u003cp\u003eEnsure that other Google Cloud services requiring access to Artifact Registry, such as Binary Authorization and Google Kubernetes Engine, are also within the service perimeter.\u003c/p\u003e\n"]]],[],null,[]]
