Google Distributed Cloud 구현에서 관리자 클러스터의 제어 영역 VM에는 두 개의 연결된 디스크가 있습니다.
부팅 디스크에는 VM용 운영체제가 있습니다.
데이터 디스크에는 관리자 클러스터의 상태를 저장하는 사용자 인증 정보와 etcd 데이터베이스가 있습니다. 즉, 데이터 디스크는 관리자 클러스터의 모든 Kubernetes 객체를 저장합니다.
이 페이지에서는 제어 영역 VM이 손실되거나 부팅 디스크가 손상된 경우 복구하는 방법을 보여줍니다. 예를 들면 다음과 같습니다.
스팸 저널 로그로 인해 부팅 디스크가 읽기 전용이 됩니다.
Docker 오버레이 파일 시스템이 손상됩니다.
이 페이지에서는 데이터 디스크 복구에 대해서는 다루지 않습니다. 데이터 디스크를 복구하는 방법은 관리자 클러스터 복원을 참조하세요.
제어 영역 VM 복구
관리자 클러스터의 제어 영역 VM을 복구하기 위한 단계는 보유하고 있는 관리자 클러스터가 고가용성(HA) 관리자 클러스터인지 아닌지에 따라 약간 달라집니다.
HA
HA 관리자 클러스터에는 3개의 컨트롤 플레인 VM이 있습니다. 클러스터 컨트롤 플레인을 가져오려면 VM이 최소 2개 이상 있어야 합니다. 3개의 VM이 실패한 경우 실패한 VM을 한 번에 하나씩 복구합니다. 두 번째 VM이 복구되고 실행되면 클러스터 컨트롤 플레인이 다시 작동해야 합니다.
ADMIN_CLUSTER_KUBECONFIG를 관리자 클러스터의 kubeconfig 파일 경로로 바꿉니다.
이 명령어 출력은 다음과 비슷합니다.
Please select the control plane VM template to be used for re-creating the admin cluster's control plane VM.
[1] VM template: /atl-qual-vc07/vm/gke-admin-57f8g-fx9f4c729448z2v8-2-tmpl
GKE on-prem version: 1.16.0-gke.550
Creation time: 2023-07-25 01:52:51.815518 +0000 UTC
CPU: 4 CPU(s)
Memory: 16384 MB
Data disk: [vsanDatastore] 37a73d64-b823-47cd-2e0c-00620b9189a0/gke-admin-57f8g/default/gke-admin-57f8g-2-data.vmdk
[2] VM template: /atl-qual-vc07/vm/gke-admin-57f8g-fx9f4c729448z2v8-0-tmpl
GKE on-prem version: 1.16.0-gke.550
Creation time: 2023-07-25 01:52:54.228252 +0000 UTC
CPU: 4 CPU(s)
Memory: 16384 MB
Data disk: [vsanDatastore] 37a73d64-b823-47cd-2e0c-00620b9189a0/gke-admin-57f8g/default/gke-admin-57f8g-0-data.vmdk
[3] VM template: /atl-qual-vc07/vm/gke-admin-57f8g-fx9f4c729448z2v8-1-tmpl
GKE on-prem version: 1.16.0-gke.550
Creation time: 2023-07-25 01:52:54.210705 +0000 UTC
CPU: 4 CPU(s)
Memory: 16384 MB
Data disk: [vsanDatastore] 37a73d64-b823-47cd-2e0c-00620b9189a0/gke-admin-57f8g/default/gke-admin-57f8g-1-data.vmdk
Please enter your numeric choice:
복구할 VM의 번호를 입력합니다. 출력에 VM이 표시되지 않으면 Google Cloud 지원팀에 문의하세요.
복구해야 하는 VM이 3개 있는 경우 gkectl repair
admin-master는 첫 번째 VM을 복구한 후 다음과 유사한 오류 메시지를 출력합니다.
If you are repairing admin control plane VM for HA admin cluster,
it's possible that the API server is still down after repairing one
of the VMs. Try continue fixing other control plane VMs listed to
recover the quorum of control plane.
ADMIN_CLUSTER_KUBECONFIG를 관리자 클러스터의 kubeconfig 파일 경로로 바꿉니다.
관리자 클러스터의 제어 영역 VM은 VM을 다시 생성하는 데 필요한 모든 정보가 들어 있는 VM 템플릿에 클론됩니다. gkectl repair admin-master 명령어는 VM 템플릿을 사용하여 새 VM을 만듭니다. 그런 다음 새 부팅 디스크와 기존 데이터 디스크를 연결합니다.
클러스터 노드가 DHCP 서버에서 주소를 가져올 경우 새 VM은 원본 VM과 다른 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,["In a Google Distributed Cloud implementation, the control-plane VM for an\nadmin cluster has two attached disks:\n\n- The boot disk has the operating system for the VM.\n\n- The data disk has credentials and the etcd database, which stores the state of\n the admin cluster. That is, the data disk stores all of the Kubernetes objects\n for the admin cluster.\n\nThis page shows you how to recover when the control-plane VM is lost or the boot\ndisk is compromised. For example:\n\n- The boot disk becomes read-only due to spam journal logs.\n- The Docker overlay filesystem gets corrupted.\n\nThis page does not cover recovery of the data disk. For instructions on how to\nrecover the data disk, see\n[Restoring an admin cluster](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/back-up-and-restore-an-admin-cluster-with-gkectl).\n\nRepair the control-plane VM **Warning:** Don't run `gkectl repair admin-master` after a failed admin upgrade attempt. Instead, [resume the admin upgrade](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/upgrading#about_resume_admin).\n\nThe steps that you do to repair the admin cluster's control-plane VM differ\nslightly depending on whether you have a high-availability (HA) admin cluster\nor a non-HA admin cluster. \n\nHA\n\nAn HA admin cluster has three control plane VMs. You must have at least two VMs\nto bring up the cluster control plane. If three VMs have failed, repair\nthe failed VMs one at a time. After the second VM is repaired and running,\nthe cluster control plane should come back up.\n\n1. Run the following command:\n\n ```\n gkectl repair admin-master --config ADMIN_CLUSTER_CONFIG --kubeconfig ADMIN_CLUSTER_KUBECONFIG\n ```\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003eADMIN_CLUSTER_CONFIG\u003c/var\u003e with the path of your admin cluster\n configuration file.\n\n - \u003cvar translate=\"no\"\u003eADMIN_CLUSTER_KUBECONFIG\u003c/var\u003e with the path of your admin cluster's\n kubeconfig file.\n\n The output of the command is similar to the following: \n\n ```\n Please select the control plane VM template to be used for re-creating the admin cluster's control plane VM.\n [1] VM template: /atl-qual-vc07/vm/gke-admin-57f8g-fx9f4c729448z2v8-2-tmpl\n GKE on-prem version: 1.16.0-gke.550\n Creation time: 2023-07-25 01:52:51.815518 +0000 UTC\n CPU: 4 CPU(s)\n Memory: 16384 MB\n Data disk: [vsanDatastore] 37a73d64-b823-47cd-2e0c-00620b9189a0/gke-admin-57f8g/default/gke-admin-57f8g-2-data.vmdk\n\n [2] VM template: /atl-qual-vc07/vm/gke-admin-57f8g-fx9f4c729448z2v8-0-tmpl\n GKE on-prem version: 1.16.0-gke.550\n Creation time: 2023-07-25 01:52:54.228252 +0000 UTC\n CPU: 4 CPU(s)\n Memory: 16384 MB\n Data disk: [vsanDatastore] 37a73d64-b823-47cd-2e0c-00620b9189a0/gke-admin-57f8g/default/gke-admin-57f8g-0-data.vmdk\n\n [3] VM template: /atl-qual-vc07/vm/gke-admin-57f8g-fx9f4c729448z2v8-1-tmpl\n GKE on-prem version: 1.16.0-gke.550\n Creation time: 2023-07-25 01:52:54.210705 +0000 UTC\n CPU: 4 CPU(s)\n Memory: 16384 MB\n Data disk: [vsanDatastore] 37a73d64-b823-47cd-2e0c-00620b9189a0/gke-admin-57f8g/default/gke-admin-57f8g-1-data.vmdk\n\n Please enter your numeric choice:\n ```\n2. Enter the number for the VM that you want to repair. If you don't see\n the VM in the output, contact Google Cloud Support.\n\n If you have three VMs that need to be repaired, `gkectl repair\n admin-master` outputs an error message similar to the\n following after repairing the first VM: \n\n If you are repairing admin control plane VM for HA admin cluster,\n it's possible that the API server is still down after repairing one\n of the VMs. Try continue fixing other control plane VMs listed to\n recover the quorum of control plane.\n\n In this case, re-run the command to repair the second VM.\n\nNon-HA\n\nRun the following command: \n\n```\ngkectl repair admin-master \\\n --config ADMIN_CLUSTER_CONFIG \\\n --kubeconfig ADMIN_CLUSTER_KUBECONFIG\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eADMIN_CLUSTER_CONFIG\u003c/var\u003e with the path of your admin cluster configuration file.\n- \u003cvar translate=\"no\"\u003eADMIN_CLUSTER_KUBECONFIG\u003c/var\u003e with the path of your admin cluster's `kubeconfig` file.\n\nThe admin cluster's control-plane VM is cloned into a VM template, which has\nall the information needed to re-create the VM. The `gkectl repair admin-master`\ncommand uses the VM template to create a new VM. Then it attaches a new\nboot disk and the existing data disk.\n\nIf your cluster nodes get their addresses from a DHCP server, the new VM might\nhave a different IP address from the original VM.\n\nWhat's next\n\n- If you need additional assistance, reach out to [Cloud Customer Care](/support-hub).\n\n You can also see\n [Getting support](/kubernetes-engine/distributed-cloud/vmware/docs/getting-support) for more information about support resources, including the following:\n - [Requirements](/kubernetes-engine/distributed-cloud/vmware/docs/getting-support#support_requirements) for opening a support case.\n - [Tools](/kubernetes-engine/distributed-cloud/vmware/docs/getting-support#support_tools) to help you troubleshoot, such as logs and metrics.\n - Supported [components](/kubernetes-engine/distributed-cloud/vmware/docs/getting-support#whats_supported), [versions](/kubernetes-engine/distributed-cloud/vmware/docs/getting-support#version_support_policy), and [features](/kubernetes-engine/distributed-cloud/vmware/docs/getting-support#supported_features) of Google Distributed Cloud for VMware (software only)."]]