이 페이지에서는 특정 네임스페이스를 기준으로 클러스터 리소스에 대한 보기 액세스를 제한하는 방법과 제한된 액세스 권한이 있는 사용자가 Google Cloud 콘솔에서 이러한 리소스를 볼 수 있는 방법을 설명합니다. 이 시나리오는 멀티 테넌트 Google Kubernetes Engine(GKE) 클러스터를 실행하는 조직에서 일반적입니다.
이 페이지는 사용자에게 특정 네임스페이스의 클러스터 리소스에 대한 제한된 액세스 권한을 제공하려는 보안 전문가 및 운영자를 위해 작성되었습니다.
Google Cloud 콘텐츠에서 참조하는 일반적인 역할 및 예시 태스크에 대해 자세히 알아보려면 일반 GKE Enterprise 사용자 역할 및 태스크를 참조하세요.
[[["이해하기 쉬움","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-06-19(UTC)"],[],[],null,["# Enable access and view cluster resources by namespace\n\n[Autopilot](/kubernetes-engine/docs/concepts/autopilot-overview) [Standard](/kubernetes-engine/docs/concepts/choose-cluster-mode)\n\n*** ** * ** ***\n\nThis page explains how to restrict view\naccess to cluster resources based on specific namespaces, and how users with\nrestricted access can view these resources on the Google Cloud console. This scenario is common for\norganizations that run [multi-tenant](/kubernetes-engine/docs/concepts/multitenancy-overview)\nGoogle Kubernetes Engine (GKE) clusters.\n\nThis page is for\nSecurity specialists and Operators who want to provide users\nwith restricted access to cluster resources for specific namespaces.\nTo learn more about\ncommon roles and example tasks that we reference in Google Cloud content, see\n[Common GKE user roles and tasks](/kubernetes-engine/enterprise/docs/concepts/roles-tasks).\n\nBefore reading this page, ensure that you're familiar with the following namespace concepts:\n\n- [Organizing Kubernetes with Namespaces](https://cloud.google.com/blog/products/containers-kubernetes/kubernetes-best-practices-organizing-with-namespaces)\n- [Enterprise multi-tenancy best practices](/kubernetes-engine/docs/best-practices/enterprise-multitenancy#create-namespaces)\n\nEnable namespace-restricted access to cluster resources\n-------------------------------------------------------\n\nYou can use tenant permissions to restrict user interactions with the cluster on\nthe Google Cloud console. You grant users the\n[`roles/container.clusterViewer`](/kubernetes-engine/docs/how-to/iam#predefined)\nIAM permission as well as\n[role-based access control (RBAC) permissions](/kubernetes-engine/docs/how-to/role-based-access-control)\nto view resources in specific namespaces.\n| **Note:** By default, the Google Cloud console expects users to have view access to all namespaces in all clusters (that is, users have the `roles/container.viewer` IAM permission). If the user only has access to specific namespaces, they should follow the steps described in [View namespace-restricted resources in\n| the Google Cloud console](#viewing-resources).\n\nTo learn more about using namespaces, see\n[Organizing Kubernetes with Namespaces](https://cloud.google.com/blog/products/containers-kubernetes/kubernetes-best-practices-organizing-with-namespaces)\nand [Enterprise multi-tenancy best practices](/kubernetes-engine/docs/best-practices/enterprise-multitenancy#create-namespaces).\n\nView namespace-restricted resources in the Google Cloud console\n---------------------------------------------------------------\n\nIf you have limited IAM or RBAC permissions and want to view\nnamespace-restricted resources on the Google Cloud console, follow these steps:\n\n1. Go to the **Workloads** page in the Google Cloud console.\n\n [Go to Workloads](https://console.cloud.google.com/kubernetes/workload/overview)\n2. Click the **Namespace** drop-down list.\n\n3. Click add **Add filter**.\n\n4. Enter the namespace you want to access, then click **Save**.\n\n5. Click **OK**.\n\nThe list will be filtered to show the selected namespace.\n\nShare saved views\n-----------------\n\nYou can also save the filtered list as a named *saved view*. The saved view\nwill persist across sessions, and can be shared with other users.\n\nTo share a saved view, follow these steps:\n\n1. Select the saved view from the **Saved view** drop-down list.\n2. Next to the **Saved view** drop-down list, click more_vert, then click **Share**.\n3. Click content_copy to copy the URL in the **Share view** dialog. You can share this URL with other users who need access to the same cluster and namespaces."]]
