Cloud, hosting & identity · wired today
Drive Kubernetes API with governed agents
Infrastructure state changes under you; agents need to read it live. The Kubernetes API connector is one of 205 executable connectors and gives agents 5 read-only tools, with the credential held in the vault and every call receipted.
What agents can run against Kubernetes API
| Tool | What it does |
|---|---|
version | Get the Kubernetes version the apiserver reports, including build and platform |
list_namespaces | List the namespaces in the cluster with their phase and creation time |
list_pods | List the pods in one namespace with their phase, node, IP and start time |
list_nodes | List the cluster nodes with their kubelet version, OS image, capacity and schedulability |
list_deployments | List the deployments in one namespace with desired, ready and available replica counts |
Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.
What the Kubernetes API connector needs
You provide API server, token from your Kubernetes API account; Quox sends it as a bearer token. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Where to get it: Kubernetes API's own API documentation ↗ covers creating and scoping the credential.
How proven is this?
LIVE-PROVEN: every tool on this page was executed with real credentials against a real running Kubernetes API instance (provisioned for the proof, then destroyed), and every call answered successfully. The strongest proof class a connector can carry before it runs inside your own deployment.
Kubernetes API integration FAQ
What can Quox agents do with Kubernetes API?
Agents can run 5 read-only tools against Kubernetes API: version, list namespaces, list pods, list nodes, list deployments. Every call is receipted in the evidence trail.
What does the Kubernetes API integration need?
You provide API server, token from your Kubernetes API account; Quox sends it as a bearer token. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Do agents see my Kubernetes API credentials?
No. Credentials live encrypted in the Quox vault and are resolved server-side at call time. Agents invoke tools; they never receive the underlying secret.
How proven is the Kubernetes API connector?
LIVE-PROVEN: every tool on this page was executed with real credentials against a real running Kubernetes API instance (provisioned for the proof, then destroyed), and every call answered successfully. The strongest proof class a connector can carry before it runs inside your own deployment.