Migrate containers to Arm using KubeArchInspect
Introduction
Install KubeArchInspect
Run KubeArchInspect
Analyze the results
Next Steps

  Log an issue

  Fork and edit

  Discuss on Discord

About this Learning Path

Skill level:  Introductory
Reading time:  15 min
Last updated:  17 Sep 2026
Skill level:
  Introductory
Reading time:
  15 min
Last updated:
  17 Sep 2026
Author:Jason Andrews, Arm
Arm IP:Neoverse
Tags: Performance and Architecture AWS Graviton Microsoft Azure Cobalt Google Axion Oracle Cloud Infrastructure (OCI) Ampere Compute Linux Kubernetes Runbook
Author:
  • Jason Andrews, Arm
Arm IP:
Neoverse
Tags:
Performance and Architecture AWS Graviton Microsoft Azure Cobalt Google Axion Oracle Cloud Infrastructure (OCI) Ampere Compute Linux Kubernetes Runbook

Who is this for?

This is an introductory topic for software developers who want to ensure containers running in a Kubernetes cluster support the Arm architecture.

What will you learn?

Upon completion of this Learning Path, you will be able to:

  • Run KubeArchInspect to generate a report on the containers running in a Kubernetes cluster.
  • Discover which images support the Arm architecture.
  • Understand common reasons for an image not supporting Arm.
  • Make configuration changes to upgrade images with Arm support.

Prerequisites

Before starting, you will need the following:

  • A running Kubernetes cluster accessible with kubectl

Summary

AI-assisted

This summary was drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
You’ll use KubeArchInspect to assess Kubernetes workloads for Arm migration. First, you’ll scan a live cluster and review a report that maps container images to the architectures advertised by their registries. Then, you’ll identify images with arm64 support, images that need newer tags, and images that can’t be checked. You’ll update selected workloads and re-run the scan to verify Arm-compatible images.

Frequently asked questions

AI-assisted

These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
How do I run the scan against my cluster?
Ensure that kubectl is configured to connect to your cluster, then run kubearchinspect images. The tool connects to the cluster and inspects the images that it finds.
What does the report show and how do I read it?
The report lists each image with its name, tag, and a status symbol. A green tick (✅) means that arm64 support is present, and a red cross (❌) means that arm64 isn’t available. A blue up symbol (🆙) means that a newer tag adds arm64, and a red cross mark (🚫) indicates an error occurred while checking the image.
What should I do when a line shows the blue up indicator?
Update your Kubernetes configuration to use the newer image tag that includes arm64 support. Re-run kubearchinspect images to confirm the status changes to a green tick.
What should I check if an image shows a red cross?
Review the source registry for alternative tags or a different image that provides arm64. If no tags or images are available, note that the current image doesn’t support Arm and plan accordingly.
What should I do if a line shows a red cross mark?
Rerun the scan and verify that the image reference is valid and can be queried at its source registry. If the issue persists, investigate access to the registry for that image.
Next