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

  Log an issue

  Fork and edit

  Discuss on Discord

About this Learning Path

Skill level:  Introductory
Reading time:  40 min
Last updated:  31 Jul 2026
Skill level:
  Introductory
Reading time:
  40 min
Last updated:
  31 Jul 2026
Author:Pareena Verma, Arm
Arm IP:Neoverse
Tags: Containers and Virtualization Google Cloud Linux Argo CD Kubernetes kubectl GKE Git NGINX
Author:
  • Pareena Verma, Arm
Arm IP:
Neoverse
Tags:
Containers and Virtualization Google Cloud Linux Argo CD Kubernetes kubectl GKE Git NGINX

Who is this for?

This is an introductory topic for developers and platform engineers who want hands-on experience implementing GitOps using Argo CD on Arm64-based Google Kubernetes Engine (GKE) clusters running on Google Axion (C4A) processors.

What will you learn?

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

  • Provision an Arm-based SUSE Linux Enterprise Server (SLES) virtual machine on Google Cloud (C4A with Axion processors)
  • Create and connect to a Google Kubernetes Engine (GKE) cluster running on Arm64 (Axion) nodes
  • Install and validate Argo CD on an Arm-based GKE cluster
  • Understand Argo CD core components and GitOps architecture
  • Deploy a production-ready application using pure GitOps workflows
  • Enable automated sync, pruning, and self-healing with Argo CD
  • Verify application health and access to deployed services on GKE

Prerequisites

Before starting, you will need the following:

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 deploy applications on Arm-based Google Kubernetes Engine using GitOps with Argo CD on Google Cloud C4A instances built on Arm Neoverse V2 cores. Starting from a SUSE Linux arm64 VM, you’ll provision an arm64 GKE environment and install Argo CD using official upstream manifests. You’ll configure browser and CLI access, retrieve admin credentials, and define a Git-backed workflow that continuously reconciles Kubernetes resources. Then, you’ll deploy a production-ready NGINX application from a GitHub repository with automated sync, pruning, and self-healing enabled. By the end, you’ll validate application health and confirm service access on the arm64 GKE cluster.

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
?
Do I need a specific Linux distribution on the VM used to manage the cluster?
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.
How do I know `kubectl` is targeting the `arm64` GKE cluster before installing Argo CD?
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.
What indicates that Argo CD installed and is accessible correctly?
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.
Which repository setup does Argo CD use for the NGINX GitOps deployment?
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.
What should I expect after enabling automated sync, pruning, and self-healing in Argo CD?
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.
Next