위의 단계를 따르면 신뢰할 수 있고 확인된 이미지만 GKE 클러스터에서 Kubernetes 컨테이너를 만드는 데 사용됩니다. 이렇게 하면 애플리케이션의 안전한 환경을 유지할 수 있습니다.
정책 구성
Binary Authorization만 사용 설정한다고 해서 클러스터가 자동으로 보호되는 것은 아닙니다.
기본적으로 정책이 구성되지 않은 경우 모든 컨테이너 이미지의 배포가 허용됩니다. 즉, 클러스터를 효과적으로 보호하려면 허용되는 이미지를 지정하는 정책을 정의하고 시행해야 합니다. Binary Authorization 정책을 구성하는 방법을 알아보려면 Google Cloud CLI를 사용하여 정책 구성을 참고하세요.
[[["이해하기 쉬움","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-07-31(UTC)"],[],[],null,["| **Note:** Starting with Kubernetes version 1.28, manual policy binding to authorize the service account for Binary Authorization is no longer necessary. The required permissions are now automatically granted to this service account. You can therefore disregard step 2 in the following instructions.\n\nTo enable Binary Authorization for GKE attached clusters, perform the following steps:\n\n1. Enable the Binary Authorization API in your project:\n\n gcloud services enable binaryauthorization.googleapis.com \\\n --project=\u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e\n\n Replace \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e with the ID of your\n Google Cloud project.\n2. Grant the `binaryauthorization.policyEvaluator` role to the Kubernetes\n service account associated with the Binary Authorization agent:\n\n gcloud projects add-iam-policy-binding \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e \\\n --member=serviceAccount:\u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e.svc.id.goog[gke-system/binauthz-agent] \\\n --role=\"roles/binaryauthorization.policyEvaluator\"\n\n3. Enable Binary Authorization when registering or updating a cluster.\n\n Register a cluster\n\n To enable Binary Authorization when registering a cluster, use the\n [`gcloud container attached clusters register` command](/sdk/gcloud/reference/container/attached/clusters/register). Follow the instructions in\n [attach your AKS cluster](/kubernetes-engine/multi-cloud/docs/attached/aks/how-to/attach-cluster),\n and include the optional argument\n `--binauthz-evaluation-mode=PROJECT_SINGLETON_POLICY_ENFORCE`: \n\n gcloud container attached clusters register \u003cvar translate=\"no\"\u003eCLUSTER_NAME\u003c/var\u003e \\\n ...\n --binauthz-evaluation-mode=PROJECT_SINGLETON_POLICY_ENFORCE\n\n Replace \u003cvar translate=\"no\"\u003eCLUSTER_NAME\u003c/var\u003e with the name of\n your cluster.\n\n Update a cluster\n\n To enable Binary Authorization when updating a cluster, use the\n [`gcloud container attached clusters update` command](/sdk/gcloud/reference/container/attached/clusters/update). Follow the instructions in\n [update your AKS cluster](/kubernetes-engine/multi-cloud/docs/attached/aks/how-to/update-cluster),\n and include the optional argument\n `--binauthz-evaluation-mode=PROJECT_SINGLETON_POLICY_ENFORCE`: \n\n gcloud container attached clusters update \u003cvar translate=\"no\"\u003eCLUSTER_NAME\u003c/var\u003e \\\n ...\n --binauthz-evaluation-mode=PROJECT_SINGLETON_POLICY_ENFORCE\n\n Replace \u003cvar translate=\"no\"\u003eCLUSTER_NAME\u003c/var\u003e with the name of\n your cluster.\n\nBy following these steps, you ensure that only trusted and verified images\nare used to create Kubernetes containers in your GKE clusters. This helps\nto maintain a secure environment for your applications.\n\nConfigure policies\n\nEnabling Binary Authorization alone doesn't automatically protect your cluster.\nBy default, it allows all container images to be deployed if no policy is\nconfigured. This means that to effectively secure your cluster, you need to\ndefine and enforce a policy that specifies which images are allowed. To\nlearn how to configure a Binary Authorization policy, see\n[Configure a policy using the Google Cloud CLI](/binary-authorization/docs/configuring-policy-cli)."]]