Stay organized with collections
Save and categorize content based on your preferences.
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.
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.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[],[],null,["# Kubernetes API Connector Overview\n\nThe Workflows connector defines the built-in functions that can\nbe used to access other APIs within a workflow.\n\nThis page provides an overview of the individual connector. There is no need to\nimport or load connector libraries in a workflow---connectors work out of the box\nwhen used in a call step.\n| **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\n| Engine API connector](/workflows/docs/reference/googleapis/container/Overview).\n\nKubernetes API\n--------------\n\nThe Kubernetes API server runs on the control plane of a Google Kubernetes Engine (GKE)\ncluster, allowing you to interact with objects in the cluster. This connector\nuses a provided `cluster_id` field and optional `project` and `location` fields\nto make a request to a cluster's control plane endpoint, even if the cluster is\nprivate. Learn more about [using\nthe Kubernetes API connector](/workflows/docs/access-kubernetes-api).\n| **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.\n\nFor more information about the control plane, see\n[GKE cluster architecture](/kubernetes-engine/docs/concepts/cluster-architecture). For more information about API methods, see\n[Kubernetes API reference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#delete-job-v1-batch)."]]
