Deploy Gardener on Google Cloud C4A (Arm-based Axion VMs)
Introduction
Get started with Gardener on Google Axion C4A (Arm Neoverse-V2)
Create a Google Axion C4A Arm virtual machine for Gardener
Install Gardener on your Arm-based SUSE VM
Verify Gardener cluster health and functionality
Benchmark Gardener cluster security with kube-bench
Next Steps
Deploy Gardener on Google Cloud C4A (Arm-based Axion VMs)
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 the
c4a-standard-4 machine type with 4 vCPUs and 16 GB of memory. It provides sufficient resources to run Gardener Local with Garden, Seed, and Shoot clusters.The clusters run locally using Kubernetes in Docker (KinD) on the Arm64-based SUSE VM. This keeps all Gardener components on the single C4A host for evaluation.
Export
KUBECONFIG to the generated kubeconfig, for example: $PWD/example/gardener-local/kind/local/kubeconfig. After exporting, kubectl commands should connect to the intended cluster without authentication errors.Proceed when Garden and Shoot report
Ready and the environment indicates healthy status for the KinD-based clusters. If readiness is pending, wait for controllers to finish reconciling.kube-bench evaluates your cluster against CIS Kubernetes benchmarks and reports findings mapped to those controls. Use the results as a baseline to track configuration changes over time on the Arm64 environment.