Study guide

9.3 Kubeflow on GKE, AutoML & Tabular Workflows as Training Choices

Google Cloud Professional Machine Learning Engineer PMLE

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Overview & the Agent Platform Map

1.1 PMLE Exam Facts, Policies & the June 2026 Blueprint 1.2 From Vertex AI to Gemini Enterprise Agent Platform: The Product Name Map

2 Chapter 2: Low-Code ML with BigQuery ML

2.1 Choosing, Training & Predicting with BigQuery ML Models 2.2 Feature Engineering & Feature Selection in BigQuery ML 2.3 Fine-Tuning & Evaluating Gemini Models from BigQuery

3 Chapter 3: AutoML & Google Cloud AI APIs

3.1 Training Models with Agent Platform AutoML 3.2 Building with Document AI, Vision, Translation & Other AI APIs

4 Chapter 4: Foundation Models in Model Garden

4.1 Evaluating & Selecting Models in Model Garden 4.2 Building & Tuning Solutions with Gemini, Imagen, Veo & MaaS 4.3 Optimizing Gemini Applications for Cost, Latency & Availability

5 Chapter 5: Exploring, Preprocessing & Protecting Data

5.1 Organizing & Exploring Tabular, Text & Image Data 5.2 Choosing a Preprocessing Tool: BigQuery, Dataflow, Spark or Python 5.3 Creating & Consolidating Features in Agent Platform Feature Store 5.4 Protecting PII & Sensitive Data in ML Workflows

6 Chapter 6: Notebooks, Prototyping & Experiment Tracking

6.1 Workbench vs. Colab Enterprise: Secure, Collaborative Notebooks 6.2 Prototyping with PyTorch, scikit-learn, JAX & Model Garden in Notebooks 6.3 Experiment Environments, Tracking & Lineage with Experiments and ML Metadata

7 Chapter 7: Evaluating Predictive & Generative AI Solutions

7.1 Evaluation Metrics for Predictive Models 7.2 Evaluating Gen AI: Computation Metrics, Rubrics & LLM-as-a-Judge

8 Chapter 8: Choosing the Modeling Approach

8.1 Choosing the Model Type: ARIMA, Trees, DNNs & LLMs 8.2 Choosing the Product & Deployment Strategy 8.3 Modeling Techniques for Interpretability Requirements

9 Chapter 9: Training Data & Training SDKs

9.1 Organizing & Ingesting Training Data from Cloud Storage & BigQuery 9.2 Custom Training on Agent Platform: Containers, Jobs & Worker Pools 9.3 Kubeflow on GKE, AutoML & Tabular Workflows as Training Choices

10 Chapter 10: Troubleshooting, Hyperparameter Tuning & Fine-Tuning

10.1 Troubleshooting ML Training Failures 10.2 Hyperparameter Tuning on Agent Platform 10.3 Fine-Tuning Foundation Models & When to Tune

11 Chapter 11: Training Hardware & Distributed Training

11.1 Choosing CPUs, GPUs & TPUs for Training 11.2 Distributed Training: Data & Model Parallelism

12 Chapter 12: Deploying Models for Inference

12.1 Batch vs. Online Inference on Agent Platform 12.2 Serving Beyond Agent Platform Endpoints: Model Garden, Cloud Run & GKE 12.3 Prebuilt & Custom Serving Containers

13 Chapter 13: Model Versions, Rollouts & Inference Logic

13.1 Organizing & Versioning Models in Model Registry 13.2 Rollout Strategies: A/B Tests, Canaries & Traffic Splits 13.3 Inference Preprocessing & Postprocessing

14 Chapter 14: Scaling Online Serving

14.1 Serving Features Online with Feature Store 14.2 Public, Dedicated & Private Endpoints 14.3 Serving Hardware & Autoscaling for Throughput 14.4 Tuning Models for Production Training & Serving

15 Chapter 15: End-to-End ML Pipelines

15.1 Validating Data & Models in Pipelines 15.2 Agent Platform Pipelines with KFP: Components, Templates & Caching 15.3 Ensuring Consistent Preprocessing Between Training & Serving

16 Chapter 16: Orchestration with Managed Airflow & Ray

16.1 Orchestrating ML Workflows with Managed Service for Apache Airflow 16.2 Ray on Agent Platform for Distributed ML Workloads

17 Chapter 17: Automating Retraining & CI/CD/CT

17.1 Choosing a Retraining Policy 17.2 CI/CD/CT for ML with Cloud Build

18 Chapter 18: Securing AI Systems, Responsible AI & Explainability

18.1 Protecting AI Systems from Data & Model Exfiltration 18.2 Defending Gen AI Apps: Safety Filters, Model Armor & Regex Guardrails 18.3 Responsible AI: Detecting & Monitoring Bias 18.4 Model Explainability on Agent Platform

19 Chapter 19: Monitoring AI Solutions

19.1 Configuring Model Monitoring on Agent Platform 19.2 Training-Serving Skew, Data Drift, Concept Drift & Attribution Drift 19.3 Monitoring, Testing & Evaluating Gen AI Solutions in Production

9.3 Kubeflow on GKE, AutoML & Tabular Workflows as Training Choices

Key Takeaways Explain This Topic AI

Kubeflow Trainer provides Kubernetes-native distributed training and fine-tuning on GKE across frameworks such as PyTorch, JAX, DeepSpeed, and XGBoost.

Kubeflow on GKE fits teams that already operate Kubernetes and need portability, while Agent Platform custom training removes cluster operations.

Tabular Workflows are managed Agent Platform Pipelines that expose each AutoML step, including data splitting, feature engineering, architecture search, training, ensembling, and distillation.

Tabular Workflow for End-to-End AutoML is generally available and supports multi-terabyte datasets with up to 1,000 columns.

Tabular Workflow for Forecasting and Feature Transform Engine are in public preview.

Last updated: September 2026

The exam guide's training bullet names four SDK families: Agent Platform custom training, Kubeflow on GKE, Agent Platform AutoML, and Tabular Workflows . Questions test whether you can pick the one that matches the team's skills, control needs, and appetite for running infrastructure.

Kubeflow on Google Kubernetes Engine (GKE)

Kubeflow is an open-source ML toolkit for Kubernetes. On GKE, its training component, Kubeflow Trainer , runs distributed training and fine-tuning as Kubernetes resources. The newer TrainJob API replaces the earlier Training Operator's framework-specific jobs such as PyTorchJob and TFJob . It supports frameworks including PyTorch, JAX, DeepSpeed, Hugging Face, and XGBoost , sets up distributed communication (for example, the environment torchrun needs), and can gang-schedule multi-node jobs.

When Kubeflow on GKE is the right answer

The organization already runs GKE with platform engineers, shared GPU node pools, and Kubernetes-native tooling and policies.

Portability matters: the same training definitions must run on-premises, on other clouds, and on Google Cloud.

The team needs fine-grained Kubernetes control : custom schedulers, sidecars, node affinity, or packing inference and training on shared accelerator pools.

Existing investment in Kubeflow Pipelines and Trainer manifests is large.

When it's the wrong answer

The scenario stresses minimal operational overhead or a team without Kubernetes skills. Agent Platform serverless training provisions and releases compute for you.

Nothing requires portability or Kubernetes-specific control.

  • Aspect Agent Platform custom training Kubeflow on GKE
  • Cluster management None. Serverless jobs You manage the GKE cluster, node pools, upgrades, and add-ons
  • Portability Google Cloud-specific job API Kubernetes-portable manifests

Integration Native Experiments, Model Registry, Pipelines, and metadata Integrate yourself, or run KFP pipelines on Agent Platform Pipelines

Scheduling control Worker pools, Spot, flex-start, reservations Full Kubernetes scheduling, queueing, and sharing

  • Best for Most teams that want managed training Platform teams standardized on Kubernetes
  • AutoML as a Training SDK

AutoML (Chapter 3) trains image and tabular models through training pipelines created from the console, the API, or the Python SDK (for example, AutoMLTabularTrainingJob ). Organizing AutoML training well means:

Using managed datasets with versioned data.

Choosing the split strategy (random, manual column, or chronological).

Setting the optimization objective and budget in node hours.

Registering the resulting model in Model Registry and comparing its evaluation with custom models trained on the same dataset.

AutoML gives no control over individual steps . That's the gap Tabular Workflows fill.

Tabular Workflows

Tabular Workflows are fully managed, scalable pipelines for end-to-end ML on tabular data. Each workflow is a managed instance of Agent Platform Pipelines (which runs Kubeflow pipelines serverlessly), defined through the Google Cloud Pipeline Components (GCPC) SDK .

  • Workflow Type Availability
  • End-to-End AutoML Classification and regression Generally available
  • Forecasting Forecasting Public preview
  • Feature Transform Engine Feature engineering Public preview
  • What Tabular Workflow for End-to-End AutoML adds over AutoML

You control every step instead of the whole pipeline at once:

  • Data splitting
  • Feature engineering
  • Architecture search , which you can limit or skip for stability and speed
  • Model training , with hardware you select for training and search
  • Model ensembling , including changing ensemble size
  • Model distillation , to shrink the model and lower serving latency

It supports multi-terabyte datasets with up to 1,000 columns . Every component appears in the pipeline graph with transformed tables, evaluated architectures, logs, and parameters. That transparency plain AutoML doesn't provide.

Versioning: each workflow version ships with the GCPC SDK. Pinning the SDK version pins the workflow version, so upgrades don't silently change training behavior. template_path, parameter_values = tabular_utils.get_automl_tabular_pipeline_and_parameters(

  • ...,
  • optimization_objective="minimize-log-loss",
  • data_source_bigquery_table_path="bq://proj.ds.training",
  • target_column="churned",
  • ...)
  • job = pipeline_jobs.PipelineJob(template_path=template_path,
  • parameter_values=parameter_values, ...)
  • job.run()
  • Running KFP Pipelines Without Running Kubeflow

Teams often mix these up. Kubeflow Pipelines (KFP) is the SDK and pipeline format. Kubeflow on GKE is a self-managed deployment of Kubeflow components on your own cluster. Agent Platform Pipelines runs KFP-format pipelines serverlessly . A team can write pipelines with the KFP SDK, run them on Agent Platform Pipelines, and never operate a Kubeflow cluster. Choose self-managed Kubeflow only when a specific Kubernetes or portability requirement calls for it.

Choosing Among All Training SDKs

  • Scenario Best choice
  • SQL team, data in BigQuery, standard model BigQuery ML
  • Little ML expertise, image or tabular objective, want best accuracy with no code AutoML

AutoML accuracy, but the team must limit architecture search, choose hardware, distill for latency, and inspect each step Tabular Workflow for End-to-End AutoML

  • Custom architecture or loss, any framework, managed infrastructure Agent Platform custom training
  • Platform team on GKE, portability required, Kubernetes-native scheduling Kubeflow Trainer on GKE
  • Distributed Python across preprocessing and training Ray on Agent Platform
  • Worked Scenario

A retailer's AutoML churn model performs well, but the serving team needs latency under 20 ms and the data science lead wants to see and control feature engineering. The dataset is 3 TB with 600 columns. Plain AutoML can't expose steps or distill the model. The best fit is Tabular Workflow for End-to-End AutoML , with architecture search narrowed and distillation enabled, run as a pipeline with the GCPC SDK version pinned.