이전 단계에서 가져온 BMC-IP 주소로 이동하여 가져온 사용자 이름과 비밀번호를 입력하여 로그인합니다.
상단 행의 첫 번째 버튼 위로 마우스를 가져갑니다. Power: ON이 표시됩니다. 클릭합니다. 드롭다운 메뉴가 표시되면 Momentary Press라고 표시된 첫 번째 항목을 클릭합니다. 버튼 색상이 녹색에서 주황색으로 변경되며, 이는 노드가 종료되고 있음을 의미합니다. 버튼이 노란색으로 바뀌어 머신이 꺼졌음을 나타낼 때까지 기다립니다. 몇 분 정도 걸립니다.
조정이 완료될 때까지 30분 정도 기다립니다.
블레이드 재부팅
이 섹션에서는 이전에 종료된 블레이드를 부팅하는 단계를 설명합니다.
기본 요건
Google Distributed Cloud (GDC) 에어갭 어플라이언스의 네트워크에 연결된 노트북이나 워크스테이션에서 이 런북을 실행할 수 있습니다. 또는 기기 연결에 따라 노트북이나 워크스테이션을 스위치에 연결할 수 있습니다. 루트 관리자 클러스터의 Kubeconfig에 액세스할 수 있는지 확인합니다. export KUBECONFIG=<path to kubeconfig>를 실행하여 올바른 KUBECONFIG 환경 변수를 설정합니다.
행동 계획
블레이드의 전원 버튼을 누릅니다. 블레이드의 전원이 켜지면 제어 영역이 연결될 때까지 몇 분 정도 기다립니다. kubectl는 30분 이내에 컨트롤 플레인에 연결할 수 있어야 합니다.
[[["이해하기 쉬움","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(UTC)"],[],[],null,["# Shut down one blade\n\nThis page describes how to shut down and reboot any one blade of Google Distributed Cloud (GDC) air-gapped appliance,\nfor example to move the device to maintain a blade.\n\nBefore you begin\n----------------\n\nEnsure you stop all workloads before proceeding further. Google cannot guarantee what will happen if workloads are active during a\nshutdown.\n\nIf you want to shut down all the blades, follow [Shut down the device](/distributed-cloud/hosted/docs/latest/appliance/admin/shutdown). When following these instructions, shut down *only* one blade and keep Google Distributed Cloud (GDC) air-gapped appliance running with two active blades.\n\n### Prerequisites\n\n1. You can execute this runbook on a laptop or workstation connected to Google Distributed Cloud (GDC) air-gapped appliance's network. Alternatively, you can connect a laptop or workstation to switch by following [Connect the device](/distributed-cloud/hosted/docs/latest/appliance/admin/connect-the-device).\n2. Make sure you have the access to Kubeconfig for the root-admin cluster.\n3. Set correct KUBECONFIG environment variable by running `export KUBECONFIG=\u003cpath to kubeconfig\u003e`.\n\n### Shut down the blade\n\n1. Get the node information by running `kubectl get nodes -A`. Determine \u003cvar translate=\"no\"\u003eNODE_NAME\u003cvar translate=\"no\"\u003e\u003c/var\u003e\u003c/var\u003e of blade to shut down.\n\n2. Pause BareMetalHost sync by running following command for the blade to be shut down:\n\n kubectl annotate bmhost -n gpc-system \u003cvar translate=\"no\"\u003eNODE_NAME\u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-w\"\u003e \u003c/span\u003e\u003cspan class=\"devsite-syntax-s2\"\u003e\"baremetalhost.metal3.io/paused=true\"\u003c/span\u003e\u003cspan class=\"devsite-syntax-w\"\u003e \u003c/span\u003e--overwrite\n \u003c/var\u003e\u003c/var\u003e\n\n Sample output of this command is: \n\n baremetalhost.metal3.io/**-**-bm** annotated\n\n3. Cordon the target node:\n\n kubectl cordon \u003cvar translate=\"no\"\u003eNODE_NAME\u003cvar translate=\"no\"\u003e\n \u003c/var\u003e\u003c/var\u003e\n\n Sample output is: \n\n node/**-**-bm** cordoned\n\n4. Drain the target node:\n\n kubectl drain \u003cvar translate=\"no\"\u003eNODE_NAME\u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-w\"\u003e \u003c/span\u003e--delete-emptydir-data\u003cspan class=\"devsite-syntax-w\"\u003e \u003c/span\u003e--grace-period\u003cspan class=\"devsite-syntax-w\"\u003e \u003c/span\u003e\u003cspan class=\"devsite-syntax-m\"\u003e900\u003c/span\u003e\u003cspan class=\"devsite-syntax-w\"\u003e \u003c/span\u003e--ignore-daemonsets\u003cspan class=\"devsite-syntax-w\"\u003e \u003c/span\u003e--disable-eviction\n \u003c/var\u003e\u003c/var\u003e\n\n Sample output: \n\n node/**-**-bm** already cordoned\n WARNING: ignoring DaemonSet-managed Pods: kube-system/anetd-krj2z, kube-system/etcd-defrag-xh469, kube-system/ipam-controller-manager-2f4dz, kube-system/istio-cni-node-cgqv4, kube-system/kube-proxy-5mwf2, kube-system/localpv-mn2jh, kube-system/metallb-speaker-6l7sv, mon-system/mon-node-exporter-backend-nd8mp, netapp-trident/netapp-trident-node-linux-rrlmd, obs-system/anthos-audit-logs-forwarder-tpfqv, obs-system/anthos-log-forwarder-npjh4, obs-system/kube-control-plane-metrics-proxy-wp8nh, obs-system/log-failure-detector-crbnv, obs-system/oplogs-forwarder-sqwvj, vm-system/macvtap-v9pgp, vm-system/virt-handler-86khx\n pod/grafana-0 deleted\n pod/capi-kubeadm-bootstrap-controller-manager-1.30.400-gke.136lvgtf deleted\n pod/grafana-0 deleted\n pod/grafana-proxy-server-86d8fc4758-mkc4f deleted\n .\n .\n .\n\n5. Gracefully shutdown the target node:\n\n6. Turn off \u003cvar translate=\"no\"\u003eNODE_NAME\u003cvar translate=\"no\"\u003e\u003c/var\u003e\u003c/var\u003e using iLO:\n\n - Retrieve the credentials to access the iLO:\n\n 1. Get the username:\n\n kubectl get secret bmc-credentials-\u003cvar translate=\"no\"\u003eNODE_NAME\u003c/var\u003e -n gpc-system -o jsonpath=\"{.data.username}\" | base64 --decode\n\n 2. Get the password:\n\n kubectl get secret bmc-credentials-\u003cvar translate=\"no\"\u003eNODE_NAME\u003c/var\u003e -n gpc-system -o jsonpath=\"{.data.password}\" | base64 --decode\n\n 3. Retrieve the \u003cvar translate=\"no\"\u003eBMC-IP\u003c/var\u003e address for \u003cvar translate=\"no\"\u003eNODE_NAME\u003c/var\u003e from values in `BMC-IP` column:\n\n kubectl get servers -A\n\n - Visit the \u003cvar translate=\"no\"\u003eBMC-IP\u003c/var\u003e address obtained in the previous step and sign in by entering the username and password obtained.\n\n - Hover over first button on top row. It should display `Power: ON`. Click it. A drop-down menu will appear, click first item labelled `Momentary Press`. The button colour will change from Green to Orange, meaning node is shutting down. Wait for the button to change color to yellow, indicating the machine has powered off. This will take a few minutes.\n\n7. Wait for 30 minutes for the reconciliation to complete.\n\nReboot the blade\n----------------\n\nThis section describes steps to boot up a blade which was shut down earlier.\n\n### Prerequisites\n\nYou can execute this runbook on a laptop or workstation connected to Google Distributed Cloud (GDC) air-gapped appliance's network. Alternatively, you can connect a laptop or workstation to switch by following [Connect the device](/distributed-cloud/hosted/docs/latest/appliance/admin/connect-the-device). Make sure you have the access to Kubeconfig for the root-admin cluster. And set correct KUBECONFIG environment variable by running `export KUBECONFIG=\u003cpath to kubeconfig\u003e`.\n\n### Plan of action\n\n1. Press the power button on the blade. Once the blade is powered up, wait for a few minutes for the control plane to connect. `kubectl` should be able to connect to control plane in under 30 minutes.\n\n2. Determine name of the target node by running `kubectl get nodes -A`.\n\n3. Uncordon the target node to enable scheduling:\n\n kubectl uncordon `\u003cvar translate=\"no\"\u003eNODE_NAME\u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-sb\"\u003e`\u003c/span\u003e\n \u003c/var\u003e\u003c/var\u003e\n\n4. Resume sync of BareMetalHost for the target node:\n\n kubectl annotate bmhost -n gpc-system \u003cvar translate=\"no\"\u003eNODE_NAME\u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-w\"\u003e \u003c/span\u003e\u003cspan class=\"devsite-syntax-s2\"\u003e\"baremetalhost.metal3.io/paused=false\"\u003c/span\u003e\u003cspan class=\"devsite-syntax-w\"\u003e \u003c/span\u003e--overwrite\n \u003c/var\u003e\u003c/var\u003e\n\n5. Wait for 30 minutes for the reconciliation to complete."]]
