如果您是 IT 管理員和作業人員,希望透過提供及維護自動化稽核或強制執行功能,確保雲端平台中執行的所有資源符合機構法規遵循規定,並設定快訊及監控 IT 系統的效能和安全漏洞,歡迎參閱本頁內容。如要進一步瞭解我們在 Google Cloud 內容中提及的常見角色和範例工作,請參閱「常見的 GKE 使用者角色和工作」。
[[["容易理解","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-09-01 (世界標準時間)。"],[],[],null,["This page explains how to use Policy Controller dashboards to view your policy\ncoverage and cluster violations.\n\nThis page is for IT administrators and Operators who want to ensure\nthat all resources running within the cloud platform meet organizational\ncompliance requirements by providing and maintaining automation to audit or\nenforce, and who set up alerting and monitor IT systems for performance and\nvulnerabilities. To learn more about common roles and example tasks that we\nreference in Google Cloud content, see\n[Common GKE user roles and tasks](/kubernetes-engine/enterprise/docs/concepts/roles-tasks).\n| **Caution:** For Google Distributed Cloud (VMware or bare metal), GKE on AWS, GKE on Azure, and GKE attached clusters, the Policy Controller dashboard requires Kubernetes cluster versions 1.26 or later and the following product versions:\n|\n| - **GKE on AWS**: 1.26.2-gke.1001 or later\n| - **GKE on Azure**: 1.26.2-gke.1001 or later\n| - **GKE attached clusters**: 1.25.0-gke.3 or later\n\nUse the Google Cloud console to view a dashboard that contains information about\nyour policy coverage. The dashboard shows information such as the following:\n\n- The number of clusters in a fleet (including unregistered clusters) that have Policy Controller installed.\n- The number of clusters with Policy Controller installed that contain policy violations.\n- The number of constraints applied to your clusters per enforcement action.\n\nIf you are using [Policy Controller bundles](/kubernetes-engine/enterprise/policy-controller/docs/concepts/policy-controller-bundles),\nyou can see an overview of your compliance based on the standards in one or\nmore bundles. This overview is aggregated at a fleet level and also includes\nyour unregistered clusters ([Preview](/products#product-launch-stages)).\n\nBefore you begin\n\n1. Make sure that your clusters are registered to a [fleet](/anthos/multicluster-management/fleets)\n and that your clusters have Policy Controller installed.\n\n2. To get the permissions that you need to use the Policy Controller dashboard, ask your administrator to grant you the following IAM roles:\n\n - GKE Hub Viewer (`roles/gkehub.viewer`) on the project containing your fleet\n - Monitoring Viewer (`roles/monitoring.viewer`) on each project with a cluster in your fleet\n\n For more information about granting roles, see [Manage access](/iam/docs/granting-changing-revoking-access).\n\nView Policy Controller status\n\nYou can view information about your policy coverage in the Google Cloud console.\n\n1. In the Google Cloud console, go to the **Policy** page under the **Posture Management** section.\n\n \u003cbr /\u003e\n\n [Go to Policy](https://console.cloud.google.com/kubernetes/policy_controller)\n\n On the **Dashboard** tab, see an overview of your Policy Controller\n coverage with the following information:\n - **Policy Controller coverage** shows the number of clusters with and without Policy Controller installed.\n - **Clusters in violation** shows the number of clusters without any violations and the number of clusters with violations. The violations are based on which [constraints](/kubernetes-engine/enterprise/policy-controller/docs/how-to/creating-policy-controller-constraints) are applied to the cluster.\n - **Enforcement** action shows the type of action specified in each constraint. For more information about enforcement actions, see [Auditing using constraints](/kubernetes-engine/enterprise/policy-controller/docs/how-to/auditing-constraints).\n - **Compliance by standards** an overview of your compliance based on the standards in one or more Policy Controller bundles. If you are not using any bundles, the status in this section shows as \"100% not applied\".\n2. To view more detailed information about policy violations in your cluster,\n go to the **Violations** tab:\n\n 1. In the **View by** section, select one of the following options:\n\n - **Constraint**: view a flat list of all constraints with violations in your cluster.\n - **Namespace**: view constraints with violations, organized by the namespace that contains the resource with a violation.\n - **Resource kind**: view constraints with violations, organized by the resource with a violation.\n 2. From any view, select the constraint name that you want to view.\n\n The **Details** tab shows information about the violation, including the\n recommended action to resolve it.\n\n The **Affected Resources** tab shows information about which resources\n are being evaluated by the constraint and have policy violations.\n\nView policy findings in Security Command Center\n\nAfter Policy Controller is installed, you can view policy violations in Security Command Center.\nThis lets you view your security posture for your Google Cloud resources and your\nKubernetes resources in the same place. You must have the\n[Security Command Center activated in your organization](/security-command-center/docs/activate-scc-overview)\n[at the Standard or Premium tier](/security-command-center/docs/service-tiers).\n| **Note:** Security Command Center shows only violations related to the following Policy Controller bundles: [`pci-dss-v3.2.1`](/kubernetes-engine/enterprise/policy-controller/docs/how-to/using-pci-dss-v3) and [`cis-k8s-v1.5.1`](/kubernetes-engine/enterprise/policy-controller/docs/how-to/using-cis-k8s-benchmark).\n\nIn Security Command Center, policy violations show as `Misconfiguration` findings. The\ncategory and next steps for each finding are the same as the constraint description\nand remediation steps.\n\nFor more information about using Policy Controller in Security Command Center, see\n[Policy Controller vulnerability findings](/security-command-center/docs/concepts-security-sources#policy-controller)."]]