[[["容易理解","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-04 (世界標準時間)。"],[],[],null,["# GKE node service account insights\n\nThis page describes the Network Analyzer insights for\nGoogle Kubernetes Engine (GKE) node service account insights. For information about\nall the insight types, see\n[Insight groups and types](/network-intelligence-center/docs/network-analyzer/insight-groups-types).\n\nTo view these insights in the gcloud CLI or the Recommender API,\nuse the following insight type:\n\n- `google.networkanalyzer.container.serviceAccountInsight`\n\nYou need the following permissions:\n\n- `recommender.networkAnalyzerGkeServiceAccountInsights.list`\n- `recommender.networkAnalyzerGkeServiceAccountInsights.get`\n\nFor more information about using the Recommender API for\nNetwork Analyzer insights, see\n[Use the Recommender CLI and API](/network-intelligence-center/docs/network-analyzer/use-cli-recommender-api).\n\nGKE node service account is disabled\n------------------------------------\n\nThis insight indicates that one or more pools in the cluster use a\ndisabled GKE node service account, which could lead to failed\nbootstrap and registration of any nodes in the cluster created when the\nservice account is disabled.\n\nThis insight includes the following information:\n\n- **Service account:** a special kind of account typically used by an application or compute workload, such as a Compute Engine instance, rather than a person. It is identified by its email address, which is unique to the account. This information is available in [Recommender API](/network-intelligence-center/docs/network-analyzer/use-cli-recommender-api).\n- **GKE cluster:** the name of the GKE cluster\n- **Node pools:** a list of node pools using the disabled service account\n\n### Related topics\n\nFor more information, see\n[Enable Compute Engine default service account](/kubernetes-engine/docs/troubleshooting/service-accounts#enable-compute-engine-service-account)\nand [Disabling a service account](/iam/docs/service-accounts-disable-enable#disabling).\n\n### Recommendations\n\n[Enable the node service account](/iam/docs/creating-managing-service-accounts#enabling).\nIf there are unregistered nodes in the affected node pools, the nodes will\nrestart and properly register to the cluster. It might take some time\nfor all nodes to restart. For a fast resolution, we recommend that you\n[resize](/kubernetes-engine/docs/how-to/resizing-a-cluster) the node pool to\nzero nodes and back to X nodes or create a new node pool that uses the\nsame node service account.\n\nGKE node pool uses the Compute Engine default service account\n-------------------------------------------------------------\n\nA node pool in your GKE cluster uses the Compute Engine\ndefault service account as its node service account. This account requires more\npermissions than are required to run your Google Kubernetes Engine cluster.\n\nThis insight includes the following information:\n\n- **GKE cluster:** a name of the GKE cluster\n- **Node pools:** a list of node pools using the default service account\n\n### Related topics\n\nFor more information, see\n[Use least privilege service accounts](/kubernetes-engine/docs/how-to/hardening-your-cluster#use_least_privilege_sa).\n\n### Recommendations\n\nInstead of the Compute Engine default service account, create and\nuse a less privileged service account for your nodes.\n\nGKE node pool has misconfigured access scopes\n---------------------------------------------\n\nA node pool in your GKE cluster has manually specified\naccess scopes, but the specified scopes are insufficient to register a node.\n\nIf your workloads use\n[Application Default Credentials (ADC)](/docs/authentication/application-default-credentials),\n[access scopes](/kubernetes-engine/docs/how-to/access-scopes) are the legacy\nmethod for granting permissions for your nodes\nand for the workloads that are running on your nodes.\nFor GKE nodes, always use at least the default scopes or\nthey won't be able to register.\n\nThis insight includes the following information:\n\n- **GKE cluster:** the name of the GKE cluster\n- **Node pools:** a list of node pools with misconfigured access scopes\n\n### Related topics\n\nFor more information, see\n[Access scopes in GKE](/kubernetes-engine/docs/how-to/access-scopes).\n\n### Recommendations\n\nReplace the node pool with one with sufficient access scopes. To create a\nnode pool with sufficient access scopes, do one of the following:\n\n- Create the new node pool without specifying access scopes. In the\n Google Cloud CLI, don't include the flag `--scopes` when calling\n `gcloud container node-pools create`.\n\n To authorize workloads running on your nodes, use\n Identity and Access Management (IAM) permissions or Kubernetes\n [role-based access control (RBAC)](/kubernetes-engine/docs/how-to/role-based-access-control).\n This is to grant access to specific IAM service accounts or\n Kubernetes service accounts. For more information, see\n [Configuring a custom service account for workloads](/kubernetes-engine/docs/how-to/access-scopes#service_account).\n- In the new node pool list of manually specified access scopes,\n add the following scopes.\n\n - `https://www.googleapis.com/auth/devstorage.read_only`\n - `https://www.googleapis.com/auth/service.management.readonly`\n - `https://www.googleapis.com/auth/servicecontrol`\n - `https://www.googleapis.com/auth/trace.append`\n - `https://www.googleapis.com/auth/logging.write`\n - `https://www.googleapis.com/auth/monitoring.write`"]]