[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-09-04。"],[],[],null,["# Increase network bandwidth for clusters and nodes\n\n[Standard](/kubernetes-engine/docs/concepts/choose-cluster-mode)\n\n*** ** * ** ***\n\nThis page shows you how to increase network bandwidth limit for\nGoogle Kubernetes Engine (GKE) clusters and cluster nodes by using [Tier 1 bandwidth](/compute/docs/networking/configure-vm-with-high-bandwidth-configuration#bandwidth-tiers).\n\nPricing\n-------\n\n[Higher bandwidth pricing](/compute/all-pricing#high_bandwidth_configuration)\napplies when you enable Tier 1 bandwidth.\n\nBefore you begin\n----------------\n\nBefore you start, make sure that you have performed the following tasks:\n\n- Enable the Google Kubernetes Engine API.\n[Enable Google Kubernetes Engine API](https://console.cloud.google.com/flows/enableapi?apiid=container.googleapis.com)\n- If you want to use the Google Cloud CLI for this task, [install](/sdk/docs/install) and then [initialize](/sdk/docs/initializing) the gcloud CLI. If you previously installed the gcloud CLI, get the latest version by running `gcloud components update`. **Note:** For existing gcloud CLI installations, make sure to set the `compute/region` [property](/sdk/docs/properties#setting_properties). If you use primarily zonal clusters, set the `compute/zone` instead. By setting a default location, you can avoid errors in the gcloud CLI like the following: `One of [--zone, --region] must be supplied: Please specify location`. You might need to specify the location in certain commands if the location of your cluster differs from the default that you set.\n\n### Limitations\n\n- [Compute Engine VM Tier_1 networking](/compute/docs/networking/configure-vm-with-high-bandwidth-configuration#limitations) limitations apply.\n- When you enable Tier 1 bandwidth, GKE enables [Google Virtual NIC (gVNIC)](/compute/docs/networking/using-gvnic), and GKE manages gVNIC as long as the node pool has Tier 1 bandwidth enabled.\n\n### Requirements\n\n- GKE nodes must use a Container-Optimized OS [node image](/kubernetes-engine/docs/concepts/node-images#cos).\n\nEnable Tier 1 bandwidth on a cluster\n------------------------------------\n\nYou can create a cluster that has Tier 1 bandwidth enabled, or you can update a\ncluster to use Tier 1 bandwidth.\n\nA Tier 1 bandwidth enabled cluster has node pool Tier 1 bandwidth enabled by\ndefault. If you set the node pool bandwidth to `TIER_UNSPECIFIED`, the node pool\nsettings override the cluster bandwidth settings.\n\n### Create a cluster with Tier 1 bandwidth enabled\n\nCreate a cluster that uses Tier 1 bandwidth: \n\n gcloud container clusters create \u003cvar translate=\"no\"\u003eCLUSTER_NAME\u003c/var\u003e \\\n --network-performance-configs=total-egress-bandwidth-tier=TIER_1\n\nReplace the \u003cvar translate=\"no\"\u003eCLUSTER_NAME\u003c/var\u003e with the name of the cluster.\n\n### Update a cluster to enable Tier 1 bandwidth\n\nUpdate a cluster to use Tier 1 bandwidth: \n\n gcloud container clusters update \u003cvar translate=\"no\"\u003eCLUSTER_NAME\u003c/var\u003e \\\n --network-performance-configs=total-egress-bandwidth-tier=TIER_1\n\nReplace the \u003cvar translate=\"no\"\u003eCLUSTER_NAME\u003c/var\u003e with the name of the existing\ncluster.\n| **Note:** When you update a cluster to use Tier 1 bandwidth, only the default value of the new node pool changes. The default value of existing node pools remains unchanged.\n\nEnable Tier 1 bandwidth on a node pool\n--------------------------------------\n\nYou can create a node pool that has Tier 1 bandwidth enabled, or you can update\na node pool to use Tier 1 bandwidth.\n\nA Tier 1 bandwidth enabled cluster has node pool Tier 1 bandwidth enabled by\ndefault. However, the node pool API overrides your cluster-level configuration\nfor Tier 1.\n\n### Create a node pool with Tier 1 bandwidth enabled\n\nCreate a node pool that uses Tier 1 bandwidth: \n\n gcloud container node-pools create \u003cvar translate=\"no\"\u003eNODEPOOL_NAME\u003c/var\u003e \\\n --cluster=\u003cvar translate=\"no\"\u003eCLUSTER_NAME\u003c/var\u003e \\\n --network-performance-configs=total-egress-bandwidth-tier=TIER_1\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eNODEPOOL_NAME\u003c/var\u003e: the name of the new node pool.\n- \u003cvar translate=\"no\"\u003eCLUSTER_NAME\u003c/var\u003e: the name of the existing cluster.\n\n### Update a node pool to enable Tier 1 bandwidth\n\nUpdate a node pool to use Tier 1 bandwidth: \n\n gcloud container node-pools update \u003cvar translate=\"no\"\u003eNODEPOOL_NAME\u003c/var\u003e \\\n --cluster=\u003cvar translate=\"no\"\u003eCLUSTER_NAME\u003c/var\u003e \\\n --network-performance-configs=total-egress-bandwidth-tier=TIER_1\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eNODEPOOL_NAME\u003c/var\u003e: the name of the node pool that you want to update.\n- \u003cvar translate=\"no\"\u003eCLUSTER_NAME\u003c/var\u003e: the name of the existing cluster.\n\nDisable Tier 1 bandwidth on a cluster or a node pool\n----------------------------------------------------\n\nYou can disable Tier 1 bandwidth at the cluster level or node pool level. When you\ndisable Tier 1 bandwidth at the cluster level, node pool Tier 1 bandwidth is set\nto `TIER_UNSPECIFIED`. Disabling Tier 1 bandwidth at cluster level does not disable\nexisting node pool configuration.\n\nUpdate the cluster to use default bandwidth: \n\n gcloud container clusters update \u003cvar translate=\"no\"\u003eCLUSTER_NAME\u003c/var\u003e \\\n --cluster=\u003cvar translate=\"no\"\u003eCLUSTER_NAME\u003c/var\u003e \\\n --network-performance-configs=total-egress-bandwidth-tier=TIER_UNSPECIFIED\n\nUpdate the node pool to use default bandwidth: \n\n gcloud container node-pools update \u003cvar translate=\"no\"\u003eNODEPOOL_NAME\u003c/var\u003e \\\n --cluster=\u003cvar translate=\"no\"\u003eCLUSTER_NAME\u003c/var\u003e \\\n --network-performance-configs=total-egress-bandwidth-tier=TIER_UNSPECIFIED\n\nWhat's next\n-----------\n\n- Use [network policy logging](/kubernetes-engine/docs/how-to/network-policy-logging) to record when connections to Pods are allowed or denied by your cluster's [network policies](https://kubernetes.io/docs/concepts/services-networking/network-policies/).\n- Learn how to [set the network tier](/network-tiers/docs/set-network-tier).\n- Know more about the highest [maximum transmission unit (MTU)](/compute/docs/networking/benchmarking-higher-bandwidth-vms#setup-benchmark-vms) setting."]]