Kubernetes API Connector Overview

Preview

This feature is subject to the "Pre-GA Offerings Terms" in the General Service Terms section of the Service Specific Terms. Pre-GA features are available "as is" and might have limited support. For more information, see the launch stage descriptions.

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.

Note: The Kubernetes API is distinct from the Kubernetes Engine API, which is used to deploy and manage GKE clusters. To call the Kubernetes Engine API in a workflow, use the Kubernetes Engine API connector.

Kubernetes API

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.

Note: If not specified, the project and location default to that of the workflow. If the GKE cluster is in a different project or region, you must specify it.

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.