Official vendor OpenAPI document · agent-readyCloud 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.
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.
Install Jentic One Beta
Connect the GKE Hub API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the GKE Hub API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fgkehub" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fgkehub" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with GKE Hub API.
Create and manage fleets that group clusters under a project
Register a cluster as a fleet membership and generate its connect manifest
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
Inspect membership health and connection status
Generate the YAML manifest needed to connect a non-GKE cluster
Use Cases
Patterns agents use GKE Hub 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
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
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
G
GKE Hub API
- Foundational (D-)41/100
45
Foundational Compliance56
Developer Experience & Jentic Compatibility20
AI-Readiness & Agent Experience94
Agent Usability63
Security64
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
45
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: DSignals: 4
53%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
25%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
56
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: CSignals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
25%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
20
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
82%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
0%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
63
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
62%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
64
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: BSignals: 1
64%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the GKE Hub API by hand means standing up Google OAuth 2.0 with a service account, requesting the cloud-platform scope, and polling the long-running membership and feature operations yourself. Through Jentic you install once, import the GKE Hub API from the API Directory, store the service-account credential once, and your agent calls it.
Permission scoping
GKE Hub puts the parent fleet or project in the URL path (/v1/{parent}/memberships, /v1/{parent}/features), so a rule can pin your agent to one fleet: it can register memberships and enable features there and nothing else. You choose the operations it may call, so feature changes are not included unless you add them.
Credential isolation
Your Google service-account credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'register a cluster with GKE Hub' or 'enable config management', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using GKE Hub 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.
Can I limit what my agent is allowed to do with the GKE Hub API?
Yes. Because Jentic One is self-hosted, your own rules decide which GKE Hub operations and credentials the agent may use. Since the API puts the parent fleet or project in the URL path (/v1/{parent}/memberships, /v1/{parent}/features), you can pin the agent to a single fleet so it registers memberships and lists resources there and nowhere else. You choose the exact operations it may call, so it cannot enable or change fleet features unless you explicitly allow those endpoints.
GET STARTED