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
?
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.

Share

Tell others about this Learning Path.

Back
Return to Servers and Cloud Computing