Troubleshooting Arm workloads

Autopilot Standard

---

This page shows you how to resolve issues with Arm workloads deployed on your Google Kubernetes Engine (GKE) Autopilot or Standard clusters.

If you need additional assistance, reach out to Cloud Customer Care.

Pods on Arm nodes crashing

The following issue occurs when you deploy a Pod on an Arm node, but the container image isn't built for Arm architecture.

To identify the issue, do the following:

1. Get the status of your Pods:

   kubectl get pods
   

2. Get the logs for a crashing Pod:

   kubectl logs POD_NAME
   

   Replace POD_NAME with the name of the crashing Pod.

   The error message in your Pod logs is similar to the following:

   exec ./hello-app: exec format error
   

To resolve this issue, ensure that your container image supports Arm architecture. As a best practice, build multiple architecture images.

Pod doesn't trigger scale-up

Applies to: Autopilot

The following issue occurs in Autopilot clusters when you attempt to deploy Arm workloads on unsupported GKE versions or unsupported Google Cloud regions.

To identify the issue, get your cluster event log:

kubectl get events -w

The output is similar to the following:

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

To resolve this issue, ensure that your Autopilot cluster is running GKE version 1.24.1-gke.1400 or later, and that the Google Cloud region supports Arm nodes.

Pods stuck in Pending state

Applies to: Autopilot

The following issue occurs when you attempt to deploy Autopilot Pods on Arm architecture but your Google Cloud project is out of quota.

To identify the issue, get the event log for your cluster:

kubectl get events -w

The output is similar to the following:

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.

This event might not appear in your log as soon as you deploy your Pods.

To resolve this issue, try to request a quota increase.

What's next

If you need additional assistance, reach out to Cloud Customer Care.