클러스터 크기를 조정하기 전에 IP 주소가 충분한지 확인합니다. 확인 방법은 클러스터에서 DHCP 서버를 사용하는지 또는 고정 IP 주소를 사용하는지에 따라 다릅니다.
DHCP
클러스터에서 DHCP를 사용하는 경우 DHCP 서버가 충분한 IP 주소를 제공할 수 있는지 확인합니다. 크기 조절 후 클러스터에 있을 노드 수보다 하나 이상의 IP 주소를 제공할 수 있어야 합니다.
고정 IP
고정 IP 주소가 충분한지 확인하는 방법은 클러스터가 GKE On-Prem API에 등록되어 있는지 여부에 따라 다릅니다. 다음 중 하나에 해당하는 경우 사용자 클러스터가 GKE On-Prem API에 등록된 것입니다.
Google Cloud 콘솔, Google Cloud CLI(gcloud CLI) 또는 GKE On-Prem API에 클러스터를 자동으로 등록하는 Terraform을 사용하여 클러스터를 만든 경우입니다. 이러한 표준 애플리케이션을 모두 합쳐서 GKE On-Prem API 클라이언트라고 부릅니다.
GKE On-Prem API가 사용자 클러스터를 관리하는 경우 콘솔을 사용하여 IP 수를 계산하고 필요한 경우 IP를 더 추가합니다.
GKE On-Prem API로 사용자 클러스터를 관리하지 않는 경우 먼저 gkectl update cluster를 실행하여 클러스터에 IP 주소가 충분히 할당되었는지 확인합니다. 그렇지 않은 경우 오류 메시지에서 필요한 추가 IP 주소의 수를 확인할 수 있습니다.
고정 IP 추가
GKE On-Prem API로 클러스터를 관리하는 경우 콘솔을 사용하여 IP 주소를 추가합니다. 아니면 관리자 워크스테이션에서 명령줄을 사용합니다.
[[["이해하기 쉬움","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(UTC)"],[],[],null,["Resizing a user cluster means adding or removing nodes. Adding nodes\nrequires that IP addresses are available for the new nodes. You resize a user\ncluster by changing the number of replicas in the node pool.\n\nFor information on maximum and minimum limits for user clusters, see\n[Scalability limits](/kubernetes-engine/distributed-cloud/vmware/docs/concepts/scalability#limits).\n\nFor information on managing node pools, see\n[creating and managing node pools](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/managing-node-pools).\n\nVerify that enough IP addresses are available\n\nIf you intend to have N nodes after the resizing, then you must have N + 1 IP\naddresses available.\n\nBefore resizing a cluster, verify that you have enough IP addresses. How you do\nthe verification depends on whether the cluster uses a DHCP server or static IP\naddresses. \n\nDHCP\n\nIf the cluster uses DHCP, check that the DHCP server can provide enough IP\naddresses. It must be able to provide at least one more IP address than the\nnumber of nodes that will be in the cluster after the resizing.\n\nStatic IPs\n\nHow you verify that you have enough static IP addresses depends on whether the\ncluster is enrolled in the GKE On-Prem API. A user cluster is enrolled in\nthe GKE On-Prem API if one of the following is true:\n\n- The cluster was created by using the Google Cloud console, the Google Cloud CLI\n (gcloud CLI), or Terraform, which automatically enrolls the\n cluster in the GKE On-Prem API. Collectively, these standard applications are\n referred to as GKE On-Prem API clients.\n\n- The command `gkectl enroll cluster` was run on a user cluster, which\n [configures it to be managed by the GKE On-Prem API](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/enroll-cluster).\n\nIf the GKE On-Prem API is managing a user cluster, use the\nconsole to count the number of IPs and add more IPs if needed.\nIf the user cluster isn't managed by the GKE On-Prem API, you can run\n`gkectl update cluster` first, which verifies whether you've allocated enough\nIP addresses in the cluster. If not, you can find the number of extra IP\naddresses needed in the error message.\n\nAdd static IPs\n\nIf the cluster is managed by the GKE On-Prem API, use the\nconsole to add more IP addresses. Otherwise, use the command\nline on your admin workstation. \n\nConsole\n\n1. In the console, go to the **Google Kubernetes Engine clusters overview**\n page.\n\n [Go to GKE clusters](https://console.cloud.google.com/kubernetes/list/overview)\n2. Select the Google Cloud project that the user cluster is in.\n\n3. In the cluster list, click the name of the cluster, and then click\n **More details** in the **Details** panel.\n\n4. In the **Networking** section, click edit **Edit**.\n\n5. In the **Add additional static IP addresses** dialog box, click\n **Add IP Address** . Enter the IP address and optionally, a hostname.\n Repeat as needed. When finished, click **Done**.\n\nCommand line\n\n1. Open the user cluster's [IP block file](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/ip-block-file)\n for editing.\n\n2. Verify that all of the IP addresses you intend to use for the user cluster\n are included in the IP block file. The IP block file should have at least\n one more IP address than the number of nodes that will be in the cluster\n after the resizing.\n\n3. To view the addresses reserved for a user cluster:\n\n ```bash\n kubectl get cluster --kubeconfig ADMIN_CLUSTER_KUBECONFIG \\\n --namespace USER_CLUSTER_NAME USER_CLUSTER_NAME --output yaml\n ```\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003eADMIN_CLUSTER_KUBECONFIG\u003c/var\u003e: the path of the admin cluster kubeconfig file\n - \u003cvar translate=\"no\"\u003eUSER_CLUSTER_NAME\u003c/var\u003e: the name of the user cluster\n4. Add as many additional static IP addresses to the corresponding block as required, and then\n run `gkectl update cluster`.\n\nHere is an example of an IP block file that has four IP addresses and the\ncorresponding hostnames:\n\n```\nhostconfig:\ndns: 172.16.255.1\ntod: 216.239.35.0\nblocks:\n- netmask: 255.255.248.0\n gateway: 21.0.135.254\n ips:\n - ip: 21.0.133.41\n hostname: user-node-1\n - ip: 21.0.133.50\n hostname: user-node-2\n - ip: 21.0.133.56\n hostname: user-node-3\n - ip: 21.0.133.47\n hostname: user-node-4\n```\n\nResize the cluster \n\nConsole\n\n1. In the console, go to the **Google Kubernetes Engine clusters overview**\n page.\n\n [Go to GKE clusters](https://console.cloud.google.com/kubernetes/list/overview)\n2. Select the Google Cloud project that the user cluster is in.\n\n3. In the cluster list, click the name of the cluster, and then click\n **More details** in the **Details** panel.\n\n4. Click the **Nodes** tab.\n\n5. Click the name of the node pool that you want to resize.\n\n6. Click edit **Resize**.\n\n7. In the **Nodes** field, enter the number of nodes that you want in\n the node pool, and then click **Done**.\n\n8. Click arrow_back to go back to the\n previous page.\n\n9. The console displays **Cluster status: changes in\n progress** . Click **Show Details** to view the **Resource status\n condition** and **Status messages**.\n\nCommand line\n\nIn the\n[user cluster configuration file](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/user-cluster-configuration-file-latest#nodepool-replicas-field),\nupdate the value of the `replicas` field in one or more of the `nodePools`\nelements.\n\nResize the cluster:\n\n```\ngkectl update cluster --kubeconfig ADMIN_CLUSTER_KUBECONFIG --config USER_CLUSTER_CONFIG\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eADMIN_CLUSTER_KUBECONFIG\u003c/var\u003e: the path of the admin cluster kubeconfig file\n\n- \u003cvar translate=\"no\"\u003eUSER_CLUSTER_CONFIG\u003c/var\u003e: the path of the user cluster configuration file\n\nVerify that the resizing succeeded:\n\n- If [advanced cluster](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/admin-cluster-configuration-file-latest#enable-advanced-cluster-field) isn't enabled:\n\n ```bash\n kubectl --kubeconfig USER_CLUSTER_KUBECONFIG get nodes\n\n kubectl --kubeconfig USER_CLUSTER_KUBECONFIG describe machinedeployments NODE_POOL_NAME | grep Replicas\n ```\n- If [advanced cluster](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/admin-cluster-configuration-file-latest#enable-advanced-cluster-field) is enabled\n\n ```bash\n kubectl --kubeconfig USER_CLUSTER_KUBECONFIG get nodes\n\n kubectl --kubeconfig ADMIN_CLUSTER_KUBECONFIG describe nodepoolclaim -n USER_CLUSTER_NAMESPACE NODE_POOL_NAME | grep \"Node Count\"\n ```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eADMIN_CLUSTER_KUBECONFIG\u003c/var\u003e: the path of the admin cluster\n kubeconfig file\n\n- \u003cvar translate=\"no\"\u003eUSER_CLUSTER_KUBECONFIG\u003c/var\u003e: the path of the user cluster\n kubeconfig file\n\n- \u003cvar translate=\"no\"\u003eNODE_POOL_NAME\u003c/var\u003e: the name of the node pool that you\n resized.\n\n- \u003cvar translate=\"no\"\u003eUSER_CLUSTER_NAMESPACE\u003c/var\u003e: the namespace of the user cluster that you\n resized.\n\nTroubleshooting\n\nSee\n[Troubleshooting cluster creation and upgrade](/kubernetes-engine/distributed-cloud/vmware/docs/troubleshooting/create-upgrade)."]]
