이 페이지에서는 Google Kubernetes Engine(GKE) Autopilot 또는 표준 클러스터에 배포된 ARM 워크로드의 문제를 해결하는 방법을 보여줍니다.
ARM 노드의 포드가 비정상 종료됨
다음 문제는 ARM 노드에 포드를 배포할 때 컨테이너 이미지가 ARM 아키텍처용으로 빌드되지 않은 경우에 발생합니다.
문제를 식별하려면 다음을 수행합니다.
포드 상태를 가져옵니다.
kubectlgetpods
비정상 종료되는 포드의 로그를 가져옵니다.
kubectllogsPOD_NAME
POD_NAME을 비정상 종료 포드의 이름으로 바꿉니다.
포드 로그의 오류 메시지는 다음과 비슷합니다.
exec ./hello-app: exec format error
이 문제를 해결하려면 컨테이너 이미지에서 Arm 아키텍처가 지원되는지 확인합니다. 멀티 아키텍처 이미지를 빌드하는 것이 좋습니다.
포드가 수직 확장을 트리거하지 않음
적용 대상: Autopilot
지원되지 않는 GKE 버전 또는 지원되지 않는Google Cloud 리전에 ARM 워크로드를 배포하려고 하면 Autopilot 클러스터에서 다음 문제가 발생합니다.
문제를 식별하려면 클러스터 이벤트 로그를 가져옵니다.
kubectlgetevents-w
출력은 다음과 비슷합니다.
117s Normal NotTriggerScaleUp pod/hello-app2-78fc858558-pg4hz pod didn't trigger scale-up (it wouldn't fit if a new node is added): 2 node(s) didn't match Pod's node affinity/selector
이 문제를 해결하려면 Autopilot 클러스터가 GKE 버전 1.24.1-gke.1400 이상을 실행하고Google Cloud 리전에서 ARM 노드를 지원하는지 확인합니다.
포드가 대기중 상태로 멈춰 있음
적용 대상: Autopilot
다음 문제는 ARM 아키텍처에 Autopilot 포드를 배포하려고 하지만 Google Cloud 프로젝트의 할당량이 초과된 경우 발생합니다.
문제를 식별하려면 클러스터의 이벤트 로그를 가져옵니다.
kubectlgetevents-w
출력은 다음과 비슷합니다.
29m Warning FailedScaleUp pod/hello-app-7b86c88cb8-8vt2k Node scale up in zones asia-southeast1-b associated with this pod failed: GCE quota exceeded. Pod is at risk of not being scheduled.
[[["이해하기 쉬움","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,["# Troubleshooting Arm workloads\n\n[Autopilot](/kubernetes-engine/docs/concepts/autopilot-overview) [Standard](/kubernetes-engine/docs/concepts/choose-cluster-mode)\n\n*** ** * ** ***\n\nThis page shows you how to resolve issues with Arm workloads deployed on your\nGoogle Kubernetes Engine (GKE) Autopilot or Standard clusters.\n\nPods on Arm nodes crashing\n--------------------------\n\nThe following issue occurs when you deploy a Pod on an Arm node, but the\ncontainer image isn't built for Arm architecture.\n\nTo identify the issue, do the following:\n\n1. Get the status of your Pods:\n\n kubectl get pods\n\n2. Get the logs for a crashing Pod:\n\n kubectl logs \u003cvar translate=\"no\"\u003ePOD_NAME\u003c/var\u003e\n\n Replace \u003cvar translate=\"no\"\u003ePOD_NAME\u003c/var\u003e with the name of the crashing Pod.\n\n The error message in your Pod logs is similar to the following: \n\n exec ./hello-app: exec format error\n\nTo resolve this issue, ensure that your container image supports Arm\narchitecture. As a best practice,\n[build multiple architecture images](/kubernetes-engine/docs/how-to/build-multi-arch-for-arm).\n\nPod doesn't trigger scale-up\n----------------------------\n\n**Applies to:** Autopilot\n\nThe following issue occurs in Autopilot clusters when you attempt to\ndeploy Arm workloads on unsupported GKE versions or unsupported\nGoogle Cloud regions.\n\nTo identify the issue, get your cluster event log: \n\n kubectl get events -w\n\nThe output is similar to the following: \n\n 117s Normal NotTriggerScaleUp pod/hello-app2-78fc858558-pg4hz pod didn't trigger scale-up (it wouldn't fit if a new node is added): 2 node(s) didn't match Pod's node affinity/selector\n\nTo resolve this issue, ensure that your Autopilot cluster is running\nGKE version 1.24.1-gke.1400 or later, and that the\nGoogle Cloud region supports Arm nodes.\n\nPods stuck in Pending state\n---------------------------\n\n**Applies to:** Autopilot\n\nThe following issue occurs when you attempt to deploy Autopilot Pods on\nArm architecture but your Google Cloud project is out of quota.\n\nTo identify the issue, get the event log for your cluster: \n\n kubectl get events -w\n\nThe output is similar to the following: \n\n 29m Warning FailedScaleUp pod/hello-app-7b86c88cb8-8vt2k Node scale up in zones asia-southeast1-b associated with this pod failed: GCE quota exceeded. Pod is at risk of not being scheduled.\n\nThis event might not appear in your log as soon as you deploy your Pods.\n\nTo help resolve this issue,\n[request a quota adjustment](/docs/quotas/help/request_increase).\n\nWhat's next\n-----------\n\n- If you can't find a solution to your problem in the documentation, see\n [Get support](/kubernetes-engine/docs/getting-support) for further help,\n including advice on the following topics:\n\n - Opening a support case by contacting [Cloud Customer Care](/support-hub).\n - Getting support from the community by [asking questions on StackOverflow](http://stackoverflow.com/questions/tagged/google-kubernetes-engine) and using the `google-kubernetes-engine` tag to search for similar issues. You can also join the [`#kubernetes-engine` Slack channel](https://googlecloud-community.slack.com/messages/C0B9GKTKJ/) for more community support.\n - Opening bugs or feature requests by using the [public issue tracker](/support/docs/issue-trackers)."]]
