Deploy applications on Arm-based GKE using GitOps with Argo CD
Introduction
Get started with Argo CD on Google Axion C4A (Arm-based)
Create a Google Axion C4A virtual machine on Google Cloud
Prepare a GKE cluster for Argo CD deployments
Install and access Argo CD on Arm64 GKE
Deploy applications using GitOps with Argo CD
Next Steps
Deploy applications on Arm-based GKE using GitOps with Argo CD
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.
Yes. The steps use a SUSE Linux
arm64 VM and rely on zypper for package management. Use an arm64 SLES environment to match the commands shown.Confirm the current Kubernetes context points to your intended GKE cluster and namespace. In the Google Cloud console, verify the node pool uses C4A machine types to ensure you are operating on Arm64 nodes.
The
argo-cd namespace exists, core Argo CD pods report Ready, and the web UI is reachable in a browser. You should also be able to retrieve the initial admin credentials and authenticate with the Argo CD CLI.Provide a GitHub repository you control and specify the repository URL and path when configuring Argo CD for the application. Argo CD then creates and syncs the Kubernetes resources from that path, and you should see the NGINX deployment and service in the cluster and in the Argo CD UI.
Argo CD applies changes from Git automatically, removes resources that are no longer defined, and corrects drift from out-of-band edits. The application should report
Synced and Healthy, and the resource list in Argo CD should match what’s in the repository.