Build Flyte and gRPC ML workflows on Google Axion
Introduction
Understand Flyte and gRPC ML workflows on Google Axion
Create a Google Axion C4A Arm virtual machine
Install Flyte and gRPC tools on Axion
Build a gRPC feature engineering service
Create ML Training Workflow
Execute and validate the ML pipeline
Understand the distributed ML architecture
Next Steps
Build Flyte and gRPC ML workflows on Google Axion
Introduction
Understand Flyte and gRPC ML workflows on Google Axion
Create a Google Axion C4A Arm virtual machine
Install Flyte and gRPC tools on Axion
Build a gRPC feature engineering service
Create ML Training Workflow
Execute and validate the ML pipeline
Understand the distributed ML architecture
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 the C4A instance family and select
c4a-standard-4 (4 vCPUs, 16 GB memory).Use a SUSE Linux Enterprise Server (SLES) arm64 image to prepare the development environment.
During execution, the workflow’s feature generation step calls the gRPC service and passes the resulting features to downstream tasks. If the service is unreachable or misconfigured, the dependent step won’t complete.
The development environment uses a single-node setup on the Axion C4A VM. The gRPC feature engineering service runs as an external microservice that the Flyte workflow invokes.
Activate the
flyte-env virtual environment and run python feature_server.py from the project directory. Leave that terminal running, then open a second terminal and run python workflow.py so that the Flyte workflow can connect to the service on port 50051.