GKE Hub API

Name: GKE Hub API API
Brand: GKE Hub API
Availability: InStock

✓ Official Vendor SpecCloud InfrastructureContainer Orchestrationoauth227 EndpointsREST

For Agents

Manage fleets of Kubernetes clusters, register memberships, and enable cross-cluster features such as Config Management and Service Mesh. Built for platform teams operating multi-cluster Kubernetes.

Quickstart

Get started with GKE Hub 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:
"register a cluster with gke hub"

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

Capabilities

What an agent can do with GKE Hub API API.

Create and manage fleets that group clusters under a project

Enable and configure fleet-level features such as Config Management

Manage namespaces, scopes, and bindings across the fleet

List long-running operations and cancel them when needed

GET STARTED

Start building with GKE Hub API API

Explore with Jentic

View OpenAPI Document

Use for: Register a Kubernetes cluster as a fleet membership, Generate the connect manifest for a new on-prem cluster, Enable Config Management on my fleet, List all memberships in my fleet

Not supported: Does not provision clusters, run workloads, or manage IAM directly — use the Container API for cluster lifecycle, GKE On-Prem for on-prem clusters, and Cloud IAM for role bindings.

GKE Hub is the control plane for managing fleets of Kubernetes clusters across GKE, Anthos, and attached on-prem or multi-cloud clusters. The API manages fleets, memberships, features such as Config Management and Service Mesh, and the bindings that scope namespaces and roles across the fleet. Use it to centralise policy, observability, and configuration for many clusters under one Google Cloud project.

Use Cases

Patterns agents use GKE Hub API API for, with concrete tasks.

★ Onboard a New Cluster to a Fleet

Platform teams that operate Kubernetes across multiple regions or vendors register every cluster as a fleet membership so policy and observability can be applied uniformly. The GKE Hub API creates the membership and generates the connect manifest YAML that the cluster operator applies to register the cluster with Google Cloud. After registration, the cluster shows up in fleet dashboards.

Call POST /v1/projects/{project}/locations/{location}/memberships, then GET /v1/{name}:generateConnectManifest and supply the manifest to the cluster operator.

Roll Out Config Management Across the Fleet

GitOps-driven platforms enable Config Management as a fleet feature so every registered cluster pulls policy and configuration from the same Git repo. The features endpoints create or patch the configmanagement feature on the fleet, and individual memberships inherit the configuration. This eliminates per-cluster setup and gives a single point of audit.

Call POST /v1/projects/{project}/locations/{location}/features with featureId configmanagement and a Git source spec, then verify it propagates to all memberships.

Audit and Drift Detection for Multi-Cluster

Compliance teams need to know which clusters are part of the fleet and what features they have enabled. The list memberships and list features endpoints return that inventory in a single project per location, supporting scheduled audits and drift detection against an expected baseline. Bindings and namespaces are also enumerable for tenant scoping reviews.

Call GET /v1/projects/{project}/locations/{location}/memberships and GET /v1/{parent}/features, then compare against the expected baseline and flag deltas.

Agent-Driven Multi-Cluster Operations

An AI agent embedded in a platform engineering toolchain can register new clusters and enable fleet features through Jentic. The agent searches for the membership-create operation, loads its schema, and executes it without engineers needing to wire OAuth and connect-manifest fetching by hand.

Use Jentic to search 'register a cluster with gke hub', load the membership create schema, and execute it for a target cluster, then fetch its connect manifest.

Key Endpoints

27 endpoints — gke hub is the control plane for managing fleets of kubernetes clusters across gke, anthos, and attached on-prem or multi-cloud clusters.

METHOD

PATH

DESCRIPTION

GET

/v1/{+parent}/memberships

List fleet memberships

POST

/v1/{+parent}/memberships

Create a fleet membership

GET

/v1/{+name}:generateConnectManifest

Generate the connect manifest for a membership

GET

/v1/{+parent}/fleets

List fleets in a location

POST

/v1/{+parent}/fleets

Create a fleet

GET

/v1/{+parent}/features

List fleet-level features

POST

/v1/{+parent}/features

Create or enable a fleet-level feature

POST

/v1/{+name}:cancel

Cancel a long-running operation

GET

/v1/{+parent}/memberships

List fleet memberships

POST

/v1/{+parent}/memberships

Create a fleet membership

GET

/v1/{+name}:generateConnectManifest

Generate the connect manifest for a membership

GET

/v1/{+parent}/fleets

List fleets in a location

POST

/v1/{+parent}/fleets

Create a fleet

Why though Jentic?

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

Credential isolation

Service account credentials live encrypted in the Jentic vault. Agents receive scoped OAuth tokens for the cloud-platform scope and operate under the IAM roles bound to that account.

Intent-based discovery

Agents search by intent (e.g., 'register a cluster with gke hub' or 'enable config management') and Jentic returns the matching membership or feature operation with its schema.

Time to first call

Direct integration: 2-4 days for IAM, fleet modelling, and connect manifest plumbing. Through Jentic: under an hour for individual fleet operations.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Kubernetes Engine API

Provisions and operates the GKE clusters that Hub then registers as memberships.

Use Container API to create and resize clusters; GKE Hub to register them into a fleet.

Complementary

Backup for GKE API

Backs up workloads on clusters that are part of the fleet.

Pair with Hub to roll out backup policy alongside other fleet features.

Complementary

GKE On-Prem API

Manages on-prem Anthos clusters that are commonly registered with Hub.

Use GKE On-Prem to manage the cluster lifecycle, Hub to bring them into a fleet.

Complementary

Cloud IAM API

Configures IAM roles and service accounts used to register and operate Hub.

Use IAM to grant the gkehub roles required before Hub operations succeed.

FAQs

Specific to using GKE Hub API API through Jentic.

What authentication does the GKE Hub API use?

It uses Google OAuth 2.0 with the cloud-platform scope, typically via a service account that has gkehub.admin or similar IAM roles. Through Jentic, those credentials live encrypted in the vault and the agent receives scoped bearer tokens.

Can I register a non-GKE cluster with GKE Hub?

Yes. Create a membership for the external cluster, call generateConnectManifest, and apply the returned YAML on the cluster to install the Connect agent. The cluster then appears in the fleet alongside GKE clusters.

What are the rate limits for the GKE Hub API?

Google enforces standard per-project quotas on management calls, typically several hundred requests per minute. Cluster onboarding operations return long-running operations whose duration depends on the cluster, not the API rate.

How do I enable Config Management on my fleet through Jentic?

Search Jentic for 'enable config management on gke fleet', load the schema for POST /v1/{parent}/features with featureId configmanagement, and execute it with a Git repo source spec.

Is the GKE Hub API free?

Hub itself has no separate charge, but Anthos features such as Config Management and Service Mesh have their own per-cluster pricing. See the Anthos pricing documentation for current rates.

Does GKE Hub run my workloads?

No. Hub is the control plane for fleets, memberships, and features. Workloads still run on the underlying GKE, Anthos, or attached clusters.