Kubernetes

Name: Kubernetes API
Brand: Kubernetes
Availability: InStock

✓ Official Vendor SpecCloud InfrastructureContainer OrchestrationapiKey933 Endpoints

For Agents

Drive a Kubernetes cluster — create, read, update, watch, and delete workloads and configuration objects across 933 endpoints — using a bearer token bound to RBAC permissions.

Install Jentic One Beta

Connect the Kubernetes to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Kubernetes, 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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Kubernetes API.

List, create, read, update, patch, and delete Pods, Deployments, StatefulSets, DaemonSets, and Jobs across namespaces

Manage Services, Endpoints, Ingresses, and NetworkPolicies for cluster networking

Create and rotate ConfigMaps and Secrets to inject configuration into workloads

GET STARTED

Start building with Kubernetes API

Explore with Jentic

View OpenAPI Document

The Kubernetes API is the control-plane interface for any Kubernetes cluster, exposing 933 path-method combinations across core resources, apps, batch, networking, RBAC, custom resources, and admissions webhooks for the v1.10.0 surface in this spec. Clients send REST requests to the API server to create, read, update, and watch declarative objects such as Pods, Deployments, Services, ConfigMaps, and Namespaces, and the controllers reconcile actual state to match. Authentication is typically a bearer token presented as the Authorization header, and resource access is gated by RBAC roles bound to users or service accounts. The same API serves kubectl, Helm, and operators, which makes it the canonical integration target for any tool that automates a cluster.

Use Cases

Patterns agents use Kubernetes API for, with concrete tasks.

★ Application deployment automation

A delivery pipeline applies Deployment, Service, and ConfigMap manifests to a Kubernetes cluster by issuing POST or PATCH requests against the corresponding apps/v1 and core/v1 endpoints. The pipeline watches the rollout via /apis/apps/v1/namespaces/{namespace}/deployments/{name} status until ReadyReplicas equals desired. This is the standard CD pattern that underpins kubectl apply and tools like Argo CD or Flux.

Patch the Deployment 'web' in namespace 'prod' via PATCH /apis/apps/v1/namespaces/prod/deployments/web to set spec.template.spec.containers[0].image to 'web:1.4.2' and poll the status until ReadyReplicas equals desired.

Configuration and secret management

An automation system pushes new ConfigMaps and Secrets into a cluster as part of release pipelines or feature toggles. Calls to POST /api/v1/namespaces/{namespace}/configmaps and the matching secrets path create or replace the objects, and consuming Pods pick up the new values on restart or via a sidecar reloader. The pattern keeps environment configuration declarative and auditable through cluster audit logs.

Create a ConfigMap via POST /api/v1/namespaces/staging/configmaps named 'feature-flags' with data {'enable_beta':'true'} and verify it appears via GET on the same path.

Cluster observability and inventory

Operators and dashboards list and watch resources across all namespaces — Pods, Nodes, Events, PersistentVolumes — to render cluster health views and feed alerting. The API supports long-poll watches that stream change events, which removes the need for polling. Metrics-server and Prometheus rely on this surface for resource discovery.

Call GET /api/v1/pods?watch=true&labelSelector=app%3Dapi and stream events into the observability pipeline for 60 seconds.

RBAC and access control management

Platform teams provision per-team or per-service-account access to the cluster by creating Roles and RoleBindings, or ClusterRoles and ClusterRoleBindings. The API endpoints under /apis/rbac.authorization.k8s.io/v1 cover every CRUD operation needed for an internal access portal that mirrors GitOps-controlled identity.

Create a RoleBinding via POST /apis/rbac.authorization.k8s.io/v1/namespaces/team-a/rolebindings to bind the 'developer' Role to the service account 'ci-runner'.

Agent-driven cluster operations via Jentic

An agent searches Jentic for 'scale a kubernetes deployment' and is matched to PATCH /apis/apps/v1/namespaces/{namespace}/deployments/{name}/scale. Jentic injects the bearer token from MAXsystem and returns structured JSON, letting the agent compose multi-step flows like 'find the failing Pod, describe its events, restart its parent Deployment' without holding cluster credentials.

Use the Jentic MCP tool kubernetes_scale_deployment to scale Deployment 'api' in namespace 'prod' to 6 replicas.

Key Endpoints

933 endpoints — the kubernetes api is the control-plane interface for any kubernetes cluster, exposing 933 path-method combinations across core resources, apps, batch, networking, rbac, custom resources, and admissions webhooks for the v1.

METHOD

PATH

DESCRIPTION

GET

/api/v1/namespaces

List all Namespaces

POST

/api/v1/namespaces

Create a Namespace

GET

/api/v1/namespaces/{namespace}/configmaps

List ConfigMaps in a Namespace

POST

/api/v1/namespaces/{namespace}/configmaps

Create a ConfigMap

GET

/api/v1/namespaces/{namespace}/pods

List Pods in a Namespace

POST

/api/v1/namespaces/{namespace}/bindings

Create a Binding

GET

/api/v1/componentstatuses

List component statuses

GET

/api/v1/namespaces

List all Namespaces

POST

/api/v1/namespaces

Create a Namespace

GET

/api/v1/namespaces/{namespace}/configmaps

List ConfigMaps in a Namespace

POST

/api/v1/namespaces/{namespace}/configmaps

Create a ConfigMap

GET

/api/v1/namespaces/{namespace}/pods

List Pods in a Namespace

Why Jentic?

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

Credential isolation

Kubernetes bearer tokens and kubeconfig contexts are stored encrypted in the Jentic vault (MAXsystem). Jentic injects the Authorization header at request time, so tokens never enter the agent's context window or chat history.

Intent-based discovery

Agents search Jentic by intent (e.g. 'scale a deployment', 'list pods in namespace') and Jentic returns the matching Kubernetes operation with its full input schema, abstracting the apiGroup/version path structure.

Time to first call

Direct Kubernetes integration: several days for kubeconfig handling, token rotation, and watch logic. Through Jentic: under a day — search, load schema, execute.

FAQs

Specific to using Kubernetes API through Jentic.

What authentication does the Kubernetes API use?

The Kubernetes API server typically authenticates clients with a bearer token presented in the Authorization header (the spec exposes this as the BearerToken scheme). Tokens are commonly issued to ServiceAccounts inside the cluster, while external clients use OIDC or kubeconfig-managed credentials. Jentic stores the bearer token encrypted in MAXsystem and injects it per request.

Can I scale a Deployment with the Kubernetes API?

Yes. Issue PATCH against /apis/apps/v1/namespaces/{namespace}/deployments/{name}/scale with a body that sets spec.replicas to the desired count, or PATCH the Deployment directly to update spec.replicas — both routes are supported.

What are the rate limits for the Kubernetes API?

The API server applies admission rate limits via the API Priority and Fairness feature gate, configured per cluster rather than at the SaaS level. Practical ceilings depend on the control plane's capacity — list and watch operations should use resourceVersion-based watches rather than polling.

How do I list Pods in a namespace through Jentic?

Search Jentic for 'list kubernetes pods', load GET /api/v1/namespaces/{namespace}/pods, and execute it with the namespace name. Install with pip install jentic and Jentic injects the bearer token from MAXsystem.

Does this Kubernetes spec cover Custom Resources and Operators?

The v1.10.0 spec captured here covers the built-in API groups bundled in the Kubernetes 1.10 release. Custom Resources are accessed via the /apis/{group}/{version}/namespaces/{namespace}/{plural} pattern but are not enumerated here because they are cluster-specific. Use kubectl api-resources or call /apis to discover what each cluster exposes.

Kubernetes

Connect the Kubernetes to your agent

Capabilities

Start building with Kubernetes API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs