Deploy an AI storefront assistant on GKE on Google Axion
Introduction
Understand mixed placement for a storefront AI assistant
Set up the source tree and cluster access
Deploy and validate the storefront on a Google N4A node pool
Review the shopping assistant implementation
Build and push the assistant image to Artifact Registry
Deploy the assistant on the Google N4A node pool
Observe and benchmark the assistant on the Google N4A node pool
Move the assistant to the Google C4A node pool and compare results
Next Steps
Deploy an AI storefront assistant on GKE on Google Axion
Introduction
Understand mixed placement for a storefront AI assistant
Set up the source tree and cluster access
Deploy and validate the storefront on a Google N4A node pool
Review the shopping assistant implementation
Build and push the assistant image to Artifact Registry
Deploy the assistant on the Google N4A node pool
Observe and benchmark the assistant on the Google N4A node pool
Move the assistant to the Google C4A node pool and compare results
Next Steps
Review frequently asked questions
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.
Use
kubectl to list nodes and confirm that both pools are present. The workflow assumes an arm64 GKE Standard cluster with separate N4A and C4A pools.The storefront runs on N4A, and
shoppingassistantservice isn’t present. This is intentional because you’ll build and deploy the assistant in later steps.Delete any existing assistant deployment, related service, and service account so the baseline reflects a storefront without the assistant.
No. You’ll build one
linux/arm64 image targeted for Axion that’ll run in either placement.Check the node assigned to the assistant pod and verify it matches the target pool after applying the appropriate Kustomize overlay. Inspect pod logs and service reachability to confirm the tier is healthy before capturing benchmarks.