Kubernetes Engine API

✓ Official Vendor SpecCloud InfrastructureContainer Orchestrationoauth263 EndpointsREST

For Agents

Provision GKE clusters, resize node pools, upgrade Kubernetes versions, and rotate credentials so an agent can manage container workload infrastructure end to end.

Quickstart

Get started with Kubernetes Engine API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create a gke kubernetes cluster"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Kubernetes Engine API API.

Create zonal or regional GKE clusters with custom networking, addons, and machine types

Add, resize, autoscale, and delete node pools on existing clusters

Upgrade the cluster master and node pools to a specific Kubernetes version

Rotate cluster credentials including IP and master auth

GET STARTED

Start building with Kubernetes Engine API API

Explore with Jentic

View OpenAPI Document

Use for: I need to create a regional GKE cluster in europe-west1, List all clusters in our project, Resize the default node pool to 6 nodes, Upgrade a cluster master to Kubernetes 1.30

Not supported: Does not deploy workloads, manage Kubernetes objects, or run kubectl commands — use only to manage GKE clusters and node pool infrastructure.

Google Kubernetes Engine (GKE) API lets developers provision and manage GKE clusters, node pools, and operations on Google Cloud. It exposes the full lifecycle of a managed Kubernetes control plane: create clusters in zonal or regional mode, scale node pools, upgrade master and node versions, configure addons such as HTTP load balancing or network policy, and rotate cluster credentials. The API also surfaces server configuration metadata describing the available Kubernetes versions and machine types per location. It is the canonical way to script GKE infrastructure outside of Terraform or the Cloud Console.

Use Cases

Patterns agents use Kubernetes Engine API API for, with concrete tasks.

★ Cluster Provisioning Automation

A platform team scripts GKE cluster provisioning so application teams can self-service via a web form. The Kubernetes Engine API creates the cluster with the team's chosen region, network, and addons, returns a long-running operation, and the automation waits for completion before handing over kubectl credentials. End-to-end provisioning takes around five minutes.

Create a regional cluster 'team-payments-prod' in europe-west1 with 3 nodes per zone, network policy enabled, and Kubernetes 1.30, then wait for the operation to complete.

Scheduled Master and Node Upgrades

A weekly job calls clusters.update and nodePools.update to roll the master and worker fleet to the latest patch version of Kubernetes. The Kubernetes Engine API performs surge upgrades to keep workloads available. The job records each operation ID for audit logging.

Upgrade cluster 'prod-1' master to the latest 1.30 patch and roll its 'workers' node pool to the same version using surge=2.

Capacity Right-Sizing

Cost-optimisation tooling reviews node pool utilisation each night and calls nodePools.setSize to rebalance fleets. The Kubernetes Engine API exposes setSize, autoscaling, and locations on every node pool so the tool can shift capacity between zones without redeploying workloads. Cluster autoscaler can be enabled or tuned through the same surface.

List node pools on cluster 'analytics-prod', and for any pool with average CPU under 30% over 24 hours, call setSize to halve its node count.

Compliance Sweep for Legacy Clusters

A governance script enumerates every cluster across the project and flags any still running a deprecated Kubernetes minor version, an outdated node image, or with legacy ABAC enabled. The Kubernetes Engine API supplies cluster.get and serverConfig data to compute these checks. Results feed an internal compliance ticketing system.

List all clusters in the project, fetch each cluster's currentMasterVersion, and return any below 1.28.

AI Agent Cluster Triage

An on-call AI agent receives a high latency alert and asks Jentic for the cluster's current node count, recent operations, and master version. The Kubernetes Engine API answers all three in seconds; the agent decides whether to escalate to a human or trigger a node pool resize through the same API.

For cluster 'prod-1' in us-central1-a, retrieve the current master version, last completed operation, and node count, then summarise whether a resize is warranted.

Key Endpoints

63 endpoints — google kubernetes engine (gke) api lets developers provision and manage gke clusters, node pools, and operations on google cloud.

METHOD

PATH

DESCRIPTION

GET

/v1/projects/{projectId}/zones/{zone}/clusters

List clusters in a zone

POST

/v1/projects/{projectId}/zones/{zone}/clusters

Create a new cluster

GET

/v1/projects/{projectId}/zones/{zone}/clusters/{clusterId}

Get a specific cluster

POST

/v1/projects/{projectId}/zones/{zone}/clusters/{clusterId}/nodePools

Create a node pool

POST

/v1/projects/{projectId}/zones/{zone}/clusters/{clusterId}/addons

Update cluster addons

GET

/v1/projects/{projectId}/zones/{zone}/clusters

List clusters in a zone

POST

/v1/projects/{projectId}/zones/{zone}/clusters

Create a new cluster

GET

/v1/projects/{projectId}/zones/{zone}/clusters/{clusterId}

Get a specific cluster

POST

/v1/projects/{projectId}/zones/{zone}/clusters/{clusterId}/nodePools

Create a node pool

POST

/v1/projects/{projectId}/zones/{zone}/clusters/{clusterId}/addons

Update cluster addons

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Google service account credentials are kept encrypted in the Jentic vault. Agents call container.googleapis.com with scoped OAuth access tokens that expire within an hour, so long-lived JSON keys never reach the agent context.

Intent-based discovery

Agents search Jentic for intents like 'create gke cluster' or 'resize node pool' and Jentic returns the matching operations with their full request schemas, including networkConfig, nodeConfig, and autoscaling fields.

Time to first call

Direct integration: 2-3 days to model OAuth, regional and zonal endpoints, long-running operations, and schema validation. Through Jentic: under 1 hour for the same scope of cluster lifecycle automation.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Cloud Run API

Run containers without managing a Kubernetes cluster

Choose Cloud Run when the workload is stateless HTTP/event-driven; choose GKE when full Kubernetes primitives are required

Complementary

Container Analysis API

Scan images deployed to GKE for vulnerabilities

Pair Container Analysis with GKE to gate deployments on vulnerability findings

Alternative

Amazon EKS API

Managed Kubernetes from a different cloud provider

Choose EKS when the rest of the stack is on AWS; choose GKE for tighter integration with Cloud Logging, Cloud Monitoring, and BigQuery

Complementary

Cloud Build API

Build and push the container images that run on GKE

Use Cloud Build to produce images, then deploy them with the Kubernetes API on the GKE cluster's master

FAQs

Specific to using Kubernetes Engine API API through Jentic.

What authentication does the Kubernetes Engine API use?

The GKE API uses Google OAuth 2.0 with the cloud-platform scope. Through Jentic the service account JSON key is stored encrypted in the Jentic vault, and agents receive short-lived access tokens per request.

Can I scale a node pool with the Kubernetes Engine API without recreating the cluster?

Yes. Call setSize on the node pool resource at /v1/projects/{projectId}/zones/{zone}/clusters/{clusterId}/nodePools to change the node count, or update its autoscaling configuration to let GKE size it automatically. The cluster keeps running through the change.

What are the rate limits for the Kubernetes Engine API?

GKE applies per-project mutation quotas with stricter limits on cluster create, upgrade, and delete because each spawns a long-running operation. Read calls have higher allowances. Check the Cloud Console Quotas page for your project's exact ceilings.

How do I create a GKE cluster through Jentic?

Run pip install jentic, search Jentic for 'create gke cluster', load the schema for clusters.create on container.googleapis.com, and execute it with your cluster spec (network, nodeConfig, initialNodeCount, region or zone).

Does the Kubernetes Engine API let me deploy workloads to the cluster?

No. This API manages the cluster and node pools themselves. To deploy workloads onto a cluster you use the Kubernetes API on the cluster's master endpoint with kubectl or a client library.