Kubernetes API Connector Overview

The Workflows connector defines the built-in functions that can be used to access other APIs within a workflow.

This page provides an overview of the individual connector. There is no need to import or load connector libraries in a workflow—connectors work out of the box when used in a call step.

The Kubernetes API server runs on the control plane of a Google Kubernetes Engine (GKE) cluster, allowing you to interact with objects in the cluster. This connector uses a provided cluster_id field and optional project and location fields to make a request to a cluster's control plane endpoint, even if the cluster is private. Learn more about using the Kubernetes API connector.

For more information about the control plane, see GKE cluster architecture. For more information about API methods, see Kubernetes API reference.

Functions
await_job Wait for a Kubernetes Job to complete.
create_job Run a Kubernetes Job in a GKE cluster.
delete_job Delete a Kubernetes Job.
request Send an HTTP request to a GKE cluster's control plane.

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2026-02-19 UTC.