Build and deploy a multi-architecture app on Amazon EKS
Introduction
Build and deploy a multi-arch application on Amazon EKS
Next Steps

  Log an issue

  Fork and edit

  Discuss on Discord

Build and deploy a multi-architecture app on Amazon EKS

Explore related resources

Find more information about the topics in this Learning Path:

Give feedback

How would you rate this Learning Path?

Review 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
?
Which platforms should I target when I build the images?
Build two variants: amd64 for x86 and arm64 for Arm-based nodes powered by Graviton. These two images form the basis for your multi-architecture manifest.
When should I create the Docker manifest, and what should it include?
Create the manifest after you build the per-architecture images. It should reference both the amd64 and arm64 images under a single tag.
How do I know if my EKS cluster has both Arm and x86 nodes before I deploy?
Confirm that the cluster includes arm64 and amd64 node groups. Use kubectl to inspect node details and verify that both architectures are present.
What result should I expect when I deploy the multi-arch image to the cluster?
Kubernetes schedules pods onto either node type, and each node pulls the correct image variant from the multi-arch tag. You should see the same application running across both architectures.
What should I check if my workload only runs on one architecture?
Verify that the cluster includes both arm64 and amd64 nodes and that your manifest lists both image variants. Also check that your deployment uses the multi-architecture image tag, not an architecture-specific one.

Share

Tell others about this Learning Path.

Back
Return to Servers and Cloud Computing