[[["容易理解","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 (世界標準時間)。"],[],[],null,["# Cluster lifecycle\n\n[Autopilot](/kubernetes-engine/docs/concepts/autopilot-overview) [Standard](/kubernetes-engine/docs/concepts/choose-cluster-mode)\n\n*** ** * ** ***\n\nThis page provides an overview of the lifecycle of a Google Kubernetes Engine (GKE)\ncluster, including which tasks you can perform yourself and which are managed by\nGoogle Cloud, with links to more detailed guides to get you started.\n\nBefore you read this page, you should be familiar with the following, as well as\n[basic Kubernetes\nconcepts](/kubernetes-engine/docs/learn/get-started-with-kubernetes):\n\n- [GKE overview](/kubernetes-engine/docs/concepts/kubernetes-engine-overview)\n- [GKE modes of operation](/kubernetes-engine/docs/concepts/choose-cluster-mode)\n\nCreating clusters\n-----------------\n\nAs you saw if you completed one of our\n[quickstarts](/kubernetes-engine/docs/quickstarts/create-cluster), creating a\nKubernetes cluster with GKE can be very simple, particularly if\nyou choose to use the Google Cloud console and use all the provided default\noptions. In real life, cluster creation can be a little more complex,\nparticularly when it comes to choosing cluster options to suit your\norganizational and technical needs. You might need to make decisions in\nconsultation with networking, security, or other colleagues before you create\nyour cluster, as some cluster options can't be changed after they're configured\nwithout recreating the cluster.\n\nYou can create clusters using the Google Cloud console, gcloud CLI,\nor the Terraform provider for GKE.\n\n- For more details about cluster configuration options (including options that you can't change after cluster creation), see the [Cluster configuration\n overview](/kubernetes-engine/docs/concepts/types-of-clusters).\n- To learn how to create an Autopilot cluster (recommended), see [Create an Autopilot\n cluster](/kubernetes-engine/docs/how-to/creating-an-autopilot-cluster).\n- To learn how to create a Standard cluster, see [Create a\n Standard\n cluster](/kubernetes-engine/docs/how-to/creating-a-cluster).\n- For some thoughts about whether you need to create multiple clusters, see [Multi-cluster use\n cases](/kubernetes-engine/fleet-management/docs/multi-cluster-use-cases).\n\nWorking with clusters\n---------------------\n\nIf you are a cluster administrator, much of your work will involve working with\nrunning clusters. Tasks might include monitoring and troubleshooting cluster\nstate, or for larger organizations (particularly those using\nGKE's [enterprise tier](/kubernetes-engine/docs/concepts/gke-editions)), managing multiple clusters together as\npart of a [fleet](/kubernetes-engine/fleet-management/docs). If you are\nSecurity specialists or Networking specialists, you might have more\nspecialized tasks such as applying security policies or configuring networking\ninfrastructure. If you are a developer using GKE, you might not\nneed to create or manage clusters, but you might need to deploy workloads to\nclusters, or troubleshoot issues with your workloads.\n\nTools that you might use include the following:\n\n- Google Cloud tools for creating, managing, and viewing clusters and their state, including the Google Cloud console and gcloud CLI.\n- The Kubernetes command-line tool `kubectl` for *cluster-internal* tasks such as deploying workloads or applying Kubernetes role-based access control (RBAC) policies.\n- [Terraform](/kubernetes-engine/docs/terraform) to declaratively provision clusters and workloads.\n\nBecause GKE is a managed service, you don't need to worry about\nthe underlying infrastructure, such as the virtual machines that run your\ncluster nodes, or the state of Kubernetes control plane components:\nGKE manages this for you.\n\nYou can read more about working with clusters and the tools and workflows that\nyou use for this in our [Cluster administration\noverview](/kubernetes-engine/docs/how-to/cluster-admin-overview). To learn more\nabout cluster architecture and the GKE control plane, see [GKE cluster\narchitecture](/kubernetes-engine/docs/concepts/cluster-architecture).\n\nUpgrading clusters\n------------------\n\nA cluster *upgrade* updates the version of the GKE system\nsoftware running on the cluster's control plane and nodes. By default,\nGKE automatically upgrades your clusters to ensure that they\nreceive security updates, fixes to known issues, and new features, and that they\nrun a supported version of Kubernetes.\n\nFor greater control over the upgrade process, GKE provides\n[release channels](/kubernetes-engine/docs/concepts/release-channels). Release\nchannels let you pick versions for your clusters with your chosen balance\nbetween feature availability and stability. [Maintenance windows and exclusions](/kubernetes-engine/docs/concepts/maintenance-windows-and-exclusions)\nlet you choose when you'd like upgrades and other cluster maintenance to occur.\n\nAll clusters\nare enrolled in the Regular release channel by default. You can find out much more about getting the most from release\nchannels with minimal disruption to your workloads in [Best practices for\nupgrading clusters](/kubernetes-engine/docs/best-practices/upgrading-clusters).\n\nYou can also initiate cluster upgrades yourself. To learn more, see [Manually\nupgrading a cluster or node\npool](/kubernetes-engine/docs/how-to/upgrading-a-cluster).\n\nUpdating clusters\n-----------------\n\nAs mentioned in the previous section on creating clusters, there are a\nnumber of changes that you can make to a cluster's configuration after it's been\ncreated. Updates that you *can* make to a cluster include:\n\n- Resize a Standard cluster (Autopilot clusters are resized automatically based on your workload's needs).\n- Add a cluster to a [fleet](/kubernetes-engine/fleet-management/docs).\n- Change the cluster's [release\n channel](/kubernetes-engine/docs/concepts/release-channels).\n- Update zones for Standard clusters.\n- Update the cluster's [maintenance\n policy](/kubernetes-engine/docs/concepts/maintenance-windows-and-exclusions).\n- Update a subset of networking options.\n- Enable and disable cluster features, including backups, logging, monitoring, and more.\n\nFor more details about what you can and can't change after cluster creation, see\n[Cluster configuration\noverview](/kubernetes-engine/docs/concepts/types-of-clusters).\n\nResizing clusters\n-----------------\n\nAutopilot clusters are sized automatically based on your Pod\nspecifications, so resizing your cluster isn't something you need to worry\nabout. For example, if you change the number of replicas of your Pod, or the\nresources it requests, the cluster will be sized up or down appropriately.\n\nIf you use Standard mode, you can manually resize your cluster to increase or decrease the number of\nnodes it has. For example, if you want to stop your cluster from consuming\nresources without deleting it, you can scale the nodes down to zero. To learn\nmore about resizing, see [Resizing a\ncluster](/kubernetes-engine/docs/how-to/resizing-a-cluster). You can\nalso choose to use [cluster autoscaling](/kubernetes-engine/docs/concepts/cluster-autoscaler), letting GKE\nautomatically resize your cluster's node pools based on the demands of your workloads,\nand [node auto-provisioning](/kubernetes-engine/docs/concepts/node-auto-provisioning), where GKE automatically creates\nand deletes node pools for you.\n\nIf you would like a more efficient way to optimize your clusters, you can also\nuse [Vertical Pod Autoscaling\n(VPA)](/kubernetes-engine/docs/concepts/verticalpodautoscaler). The autoscaler\ncan recommend values for CPU and memory requests and limits, or it can\nautomatically update the values.\n\nDeleting clusters\n-----------------\n\nWhen needed, you can delete a cluster. To learn more, see [Deleting a\ncluster](/kubernetes-engine/docs/how-to/deleting-a-cluster).\n\nAdding clusters to a fleet\n--------------------------\n\nIf your organization uses multiple clusters, you can simplify multi-cluster\nmanagement by adding the clusters to a *fleet* : a logical grouping of Kubernetes\nclusters. Creating a fleet helps your organization uplevel management from\nindividual clusters to entire groups of clusters, and lets you use fleet-enabled\nfeatures such as\n[Multi Cluster Ingress](/kubernetes-engine/docs/concepts/multi-cluster-ingress), [Config Sync](/anthos-config-management/docs/config-sync-overview), and [Policy Controller](/anthos-config-management/docs/concepts/policy-controller).\n\nYou can add GKE clusters to a fleet by using the\nGoogle Cloud console, gcloud CLI, or declaratively using Terraform\nor Config Connector.\n\nYou can learn more about how fleets work in [Fleet\nmanagement](/kubernetes-engine/docs/fleets-overview), and about creating fleets\nin [Create fleets to simplify multi-cluster\nmanagement](/kubernetes-engine/docs/how-to/creating-fleets).\n\nWhat's next\n-----------\n\n- Learn more about managing clusters in our [Cluster administration\n overview](/kubernetes-engine/docs/how-to/cluster-admin-overview).\n- Learn more about [cluster configuration\n options](/kubernetes-engine/docs/concepts/types-of-clusters).\n- Learn about [Deploying\n workloads](/kubernetes-engine/docs/get-started/deploy-workloads)."]]